The current match types available to Element attributes in the application modeller include that of wildcards and reg ex’s, primarily designed for usage on Text, Value or other string-based attributes. I am looking to get that capability extended to X Paths/HTML Paths and Element ID’s/Web Class. At this moment in time, the use of wildcards only covers a low number of Path levels such as final element identifiers (Button) or sub final DIV’s; does not allow for full Reg Ex’s or Wildcards to be used on every layer of the HTML code and Reg Ex’s are very hit and miss when it comes to applying them to HTML Paths.
The usage of wildcards and Reg Expressions does cause an Invocation error when utilising the Chrome Plug in, so any improvement on the true error thrown, for issue resolution purposes would also be a bonus.
Reason for Request –
A scenario whereby the need to have dynamic Path finding for buttons within our application has arisen, due to multiple layered buttons of the same type being available. The use of inferior interaction methods such as UIA, AA or simplified Browser attributes produces a slow and cumbersome interaction time, reducing our process benefit and having the capability of Reg Ex and Wildcard at all levels of HTML Paths will significantly improve the performance of our automation.
... View more