The achilles heel of test automation is dealing with applications that either change repeatedly or are not well designed for test automation in the first place. Rapise has a completely new approach to locating objects on a web page that based on our research and development will yield significantly better results in creating tests that work without alteration, even when the application being tested changes, or when the application uses dynamic IDs and attributes.
When used in self-healing mode, Rapise generates a “full-path locator” for each recorded element. The full-path locator includes information about all the attributes of an element and attributes of its ancestors in the DOM tree.
When you run a previously recorded test and the element is found with a traditional XPath locator then this new full-path locator is not used (there is nothing to repair).
But if the standard XPath generated for an element during recording or manually created by a tester is not valid then the new full-path locator is used instead to find the most suitable element on the page (using the fruits of our big data analysis and machine learning algorithms).
When the full-path locator is used you get the following healing notification in the report:
The healing notification indicates that an element was found with some confidence, it is a number from zero to 100%. In the notification details you can find the difference between recorded and matched elements. You can also see the images of the recorded and found elements. This information is a clue to either accept the found element or manually fix the test.
When you come across such a situation, you can then do one of three things:
The main benefits of the new self-healing tests are: