ATF Test Generator not finding specific scoped application

Thomas Berge
Tera Expert

Interesting problem. Love the ATF Test Generator application, but have come across an issue with a specific scoped application. When I am in the ATF Test Generator page/form and select advanced and then specific scope, it does not find the application I am looking for. It just returns "no results found". It DOES find other scoped applications on the same instance, so I am sure it's something in the application configuration for the scoped app, NOT the ATF Test Generator. 

I initially found an issue where the application access settings for the scoped app did not permit create operations for all application scopes. Assumed that this would be the cause since you would naturally then not be able to create records as part of automated tests and roll them back.  But changing this did not give a result. Have also added the app admin role to the Cloud User, though it had not specified that this would be required.

Does anyone know what logic the ATF Test Generator uses to exclude applications when filling in this form? Btw - the same behavior applies when selecting a specific table. 


If I generate tests for the whole instance - this particular scope is skipped.

If it IS a cross-scope issue - maybe it would have been better to let you select the app and then present a "Nice Error"??

1 ACCEPTED SOLUTION

Thomas Berge
Tera Expert

Mystery solved - I think.... Looks like something hasn't been fully or properly text indexed and I had failed to try the obvious, which was to search based on table name instead of display name/label - When I searched x_... it found the scope and generated the tests. I think that it was a combination of the 2 disparate issues as it had also failed to generate tests for this application based on a "full instance" test generation, so I think the application access settings also played a part.

View solution in original post

1 REPLY 1

Thomas Berge
Tera Expert

Mystery solved - I think.... Looks like something hasn't been fully or properly text indexed and I had failed to try the obvious, which was to search based on table name instead of display name/label - When I searched x_... it found the scope and generated the tests. I think that it was a combination of the 2 disparate issues as it had also failed to generate tests for this application based on a "full instance" test generation, so I think the application access settings also played a part.