Hi Sriram,
Yes there are, personally I’m not a fan,
- Firstly you should write good locators, based on the standards the app it written to, e.g. use the field label to locate the field, or use the accessibility text to locate the field, these are things that should not be changing.
- if you test cases are well written and the a step fails there must be a reason, so rather than auto-fixing it and getting a false positive, you should asses the failure for:
- is this change a defect?
- does the test need updating as a result of a change request?
So a quick search for “robot framework self healing” produced links like:
- Smart Healing Object Repository in Robot framework
- GitHub - Tesena-smart-testing/selfhealing-robot-framework: Self-healing Selenium Tests in Robot Framework using Healenium
- Healenium Compatibility with Robot Framework
Hopefully those links will help,
Dave.