Many of our users have tried automated testing in the past and gave up due to the ongoing maintenance effort. Autonomous maintenance will significantly relief that pain when using 21. Every change made to a test will trigger an impact analysis and will apply the changes made to other tests presenting the same pattern. 


Starting today every change(s) saved will trigger a search for similar patterns (source screen, action and destination screen) and list the tests that present similar patterns. You can then choose the tests you want to apply the changes by selecting/de-selecting the tests.

Choosing "confirm and activate changes" will apply all changes as bulk actions. If you chose to keep the changes tentative, do not check this. Tentative changes will appear in the test but will not get executed until confirmed by the user. To confirm tentative changes go to each test and confirm the change manually .

Some of the changes currently detected:

  • Addition of screens (e.g addition of tutorials)

  • Updates to the elements (Element has been changed from one type to another e.g a button was changed to an image)

  • Removal of steps from the user flow

Note that the system is already adaptive to changes given the multi-locator approach that 21 applies to test execution.

Future versions of autonomous maintenance will offer full autonomous detection of changes to the app.

Did this answer your question?