Solutions: QA leads
For QA leads: fewer broken tests after UI changes
When most of the week goes to fixing tests broken by a renamed button, the suite stops being trusted. The platform heals locator and layout changes and records each one for review.
Trigger: Suite maintenance eats the sprint. What helps: Fewer broken tests after UI changes.
How the platform fits
Heal what is cosmetic, fail what is behaviour
Locator and layout changes are healed without a human. Text and order changes wait for review. A changed outcome fails the test.
Review heals in one list
npx aitp heal --review lists healed steps since the last run for approval.
Triage before you open the trace
Each failed test gets a triage card with a proposed classification: app bug, test issue or environment.
Capabilities
Heals locator and layout changes
When a step no longer resolves because an element moved, was renamed or restyled, the platform re-resolves it, marks the test as healed and records the change for review.
Read moreTriages failures
A failed test gets a triage card with the failing step, the page state, the diff from the last passing run and a classification: app bug, test issue, environment.
Read moreTests in plain English
A test is a list of steps in plain English in a YAML file; the platform resolves each step against the live page at run time.
Read moreQuestions
What does self-healing change in a test?
It re-resolves a step whose element moved, was renamed or restyled, marks the test as healed and records the change for review.
Can I stop healed runs from passing CI?
Yes. With ci.failOnHealedPending: true, healed steps pending review return exit code 2 and the CI step fails.
Request early access
Early access: prices are the planned list prices. Billing starts when the platform enters beta; early-access use is not charged. We reply within 24 hours on business days.