When the app changes on purpose
Accept a new look in one click, or edit the check, so the test follows your app.
A bug, or a change?
Tests live as long as your app does, and your app keeps changing.Updating a test is part of everyday development, not a sign that something went wrong.
When a check fails, look at the two pictures in the Confidence Report.Either the app has a bug, and you report it, or the app changed on purpose, and the test should follow.
Look
Expected beside actual
A bug?
Create a bug report
On purpose?
Accept the new look
Save
The test expects it from now on
Accept a new look
- 1
Select the failed check in the report
- 2
Click Accept actual as expected
The new look becomes what the check expects.It is marked as pending until you save, and Ctrl+Z takes it back.
- 3
Click Save
The test file is updated.The next run expects the new look.
The team renamed "Save" to "Save draft".Three checks fail on the button, in three tests.Accept the new look in each report and save: the tests are up to date in a minute, without opening GUI Test Studio.
Accept many at once
After a redesign, many checks fail for the same reason.Accept them all from the report in one go: a sheet lists every failed check with its two pictures, so you can untick any that is a real bug before accepting the rest.
Change what a text check expects
For a text check, edit the expected words, the precision or the shape right in the report.A preview, outlined, says whether the check would pass with the change, before you save.
Change the check in GUI Test Studio
For anything more, click Open in GUI Test Studio in the report: the test opens with that check already selected, ready to edit.
Different looks for different environments
If both looks are right, for instance the light and the dark theme, keep both: see Several looks for one check.
Ask for the change in a prompt
You can also describe the change to your AI assistant, in Claude, ChatGPT with Codex or VS Code, or to a local AI model we provide or you bring: rename a step, change the text a check expects, give it a longer timeout, decide what happens if it fails, remove or ignore a step, add a wait, change the test's name or description.The assistant changes that part of the test in place, without recording anything again, and asks you to confirm before it writes, because the change overwrites the test file.
The Change a test example of the Create Test From Prompt window, in GUI Test Runner-Recorder, writes such a request for you: name the test and the change, and send it to your assistant.
See Create a test from a prompt: the same connector creates, edits and runs tests.
Still stuck?Tell us what you were trying to do, and we answer within one working day.Ask our team