Maintain tests

Keep tests working as the application changes: self-healing, component upkeep and version history.

Self-healing

Self-healingSuggested fixes for broken locators, reviewed before they change a test

Self-healing rulesLet safe fixes apply without a review, with guardrails and dry runs

How healing ranks candidatesHealing profiles, thresholds and weights

Self-healing audit trailWho or what changed which locator, why, and on what evidence

Keep tests healthy

Component maintenance queueWhich components need fixing, publishing or upgrading, with a recommendation each

Version historyEvery saved version of a test, and reverting

Version provenanceWho made each version, why, and from which run