I was excited to see that TestProject allows adding Custom Attribute’s and also allows you to customize what how element locators are prioritized when using the recorder (and I suppose by the AI/ML self healing) for the application being tested.
I have not found much updated documentation regarding this new feature (am sure something is in the works there?). Part of the reason this was so exciting is because in some ways resembles how TestCafé Studio has approached this same issue - the documentation they provided to explain how to leverage this feature was very helpful.
In the mean time, as I create tests and learn how to tweak TP, I am trying to glean and information that helps in getting the recorder to identify and prioritize element locators that work well with our application (a single-page application with dynamic knockout.js components).
A few questions:
Custom Attributes - what is permissible? I have added some custom attributes, and see they get prioritized, but there seems to be some validation as to what is allowed here.
Combined Attributes / Attributes Properties - Since we use knockout.js, there are many data-bind attributes and properties that could be great locators for us. Is there any way to make use of these here? I added the data-bind attribute, but have not found any ways to use them here.
Element Types - TP also allows for the definition of Element Types (under Addons). Can these be leveraged in any way when setting up Application Strategies?
Strategy per Application URL: Is there any way to copy a strategy from one application to another? We have several environments Dev/Staging/QA/Prod, all having different URL’s for access - if the strategies implemented impact how self-healing works, it is important that we keep the settings for these environments in sync in some manner.