Is it possible to add a feature that lets sub-element inherit the selector of the parent element inside the repository?
Suppose I have a Citrix app that I need to automate using images. Since it is Citrix, I essentially have a single ‘Window’ despite navigating to different windows/links/menus/etc.
I would like to make a repository of image selectors with the following structure:
1 Screen window for the main portal of an app
→ A bunch of images to click on
→ An unofficial ‘sub window’ here
→ -> Additional links.
2 Screen for a subportal with new forms, links, fields etc
→ Elements that can be click as above.
→ Link to an even deeper WIndow (but from Citrix point of view the same window)
→ -> More Clickables and images
Hopefully that is clear. At each level I am in some sense navigating to a new window, but with the same selector in Citrix (main window). So each window/subwindow/form box that I highlight as an element is really the exact same selector.
However, in the developer’s mind there is some distinction. So many of the sub elements in the repository are really just there to help a developer understand the hierarchy of the application rather than ‘official new windows’. Yet each element MUST contain a selector which means I end up having numerous identical selectors in this approach. This is fine until the selector changes and I have to go through and update each and every element based on the selector.