Hello,
TS Element Explorer is a useful feature to follow the page object pattern, however, it seems to be be oriented towards web pages in the web app. What if I have to write tests for a web app which has, e.g., navigation menu which is constant through the app pages?
Taken that I have the main page, the about page, the contacts page, etc. and on each of them a nav bar with items: MainPageLink, AboutPageLink, ContactsPageLink, etc. I can't see how to avoid mapping all the link for each page, instead once specifying an object for that menu with its links, and calling its instance on each of the pages under testing
1 Answer, 1 is accepted
0
Hello Dmitry,
Thank you for your interest in Test Studio.
Test Studio uses an intelligent element identification scheme to auto-generate find expressions and they are divided into pages in the element explorer as you have already noticed. Even if elements might use the same find expression but still belong to different pages they will be recognized as different elements.
Please let me know if there is anything else I could be helpful with.
Regards,
Elena Tsvetkova
Telerik
Thank you for your interest in Test Studio.
Test Studio uses an intelligent element identification scheme to auto-generate find expressions and they are divided into pages in the element explorer as you have already noticed. Even if elements might use the same find expression but still belong to different pages they will be recognized as different elements.
Please let me know if there is anything else I could be helpful with.
Regards,
Elena Tsvetkova
Telerik