November 4, 2026 · 3 min read
When your UI changes: how Qavtrix spots a changed flow
A renamed button breaks a test even though the feature still works. Qavtrix finds the element that replaced it and offers a one-click update.
Most end-to-end failures are not bugs. Someone renamed "Add to cart" to "Buy now", moved a field, or swapped a link for a button, and the test is still looking for the old element.
Telling these apart from real bugs is where teams lose time: open the trace, compare screenshots, find the new selector, edit the test, run it again.
Reading the page at the moment of failure
When a step fails, Playwright records an accessibility snapshot of the page: its buttons, links, fields and headings. Qavtrix gives that snapshot to its failure analyst together with the test and the error. If the element the test needs was replaced, the analysis names what took its place, for example the "Add to cart" button becoming a "Buy now" button.
A fix you approve
The run page shows "Your flow changed" with the old and new locator side by side. One click saves the updated test as a new version, and you can run it again straight away. The proposed locator is checked before it is offered: it must be a plain Playwright locator that appears in your test, so nothing else in the script changes.