Mark an issue fixed and let TestOptim verify the fix
Set an issue to Fixed or Closed and TestOptim checks your live app first, usually by re-running the test that found the bug. Learn what Verifying means, what happens on pass or fail, and when it is skipped.
In this article
To verify a fix in TestOptim, deploy it, open the issue and set its Status to Fixed. TestOptim then opens your live app and checks whether the problem is really gone.
Before you start
- Your role must be able to update issues: Developer, QA Engineer, QA Lead, Admin or Owner.
- The project must not be busy. TestOptim runs one job per project at a time (see what to do when another job is already in progress).
- Deploy your fix first. The check runs against the live URL of your project.
Mark an issue fixed
Open your project and click Issues.
Click the issue to open the detail panel. You can also use the full issue page.
In the Status menu, choose Fixed.
You can choose Closed the same way. Both start a check.
Close the panel. The row now shows a Verifying badge.

Note
While the check runs, the Status menu shows Verifying… and you can't choose Fixed or Closed again. In the toolbar, the same state is filed under More > Pending verification.
What happens next
How TestOptim checks the fix depends on where the issue came from.
- The issue came from a test run. TestOptim re-runs the test case that found the bug, on the live app. The run appears on the Test runs page as a Reverify run. It uses one test execution, doesn't file new issues and doesn't send test run notifications.
- The issue has no test case, for example one filed from Slack. TestOptim opens the issue's page on the live app, signs in with the project's default credential profile if it has one, and the AI judges from what the page shows now. It doesn't replay the steps to reproduce. The same page check is used when the test case was excluded, or when you have no test executions left.
A re-run usually takes a few minutes and a page check a minute or two. Then:
- The fix works. The issue gets the status you asked for (Fixed or Closed).
- The bug is still there. The issue goes back to In progress.
- The check can't reach a verdict, for example because your app is down, the page returns an error, the test can't finish, or someone stops the run. The issue gets the status you asked for without verification. Its Activity tab says the verification did not run.
The Activity tab of the issue records the result. After a re-run, it links to the verification run, so you can watch its recording.
The list and the detail panel do not refresh by themselves. Reload the page, or open another page and come back, to see the result.

Note
When a check fails, TestOptim also records its reasoning in a "[QA Failed]" note. The issue page does not show notes today. After a re-run, open the verification run from the Activity tab to see what the agent saw.
Warning
Do not rely on Fixed meaning "verified" while a project is busy. If a test run, exploration or another check is already running when you set the status, TestOptim cannot start the check. It applies Fixed (or Closed) straight away, with no verification. The status then shows Fixed immediately, so Fixed alone does not prove the fix was verified. Wait for the running job to finish if you want the verification.

Re-test a failing test
Issues that came from a test run have a Re-test this fix button under Status. It reruns only the test case that found the bug, which is a single test, not your whole suite.
- Open the issue.
- Click Re-test this fix.
- A toast says Re-testing this fix and Running 1 test. Watch the result on the Test runs page.


Things to know:
- The button is not shown for issues filed by hand, for example from Slack. They have no test case behind them.
- If another job is running you see Could not start the re-test: "A test run is already in progress for this project. Please wait for it to finish before starting another."
- Re-testing runs the test like any other run. It is not the same as the check that starts when you set Fixed. If the bug is still there, the run files a new issue and the original stays as it was. You then have two issues for one bug. Set the old one to Rejected with a note, or keep it and close the new one.
- Re-testing uses one test execution from your monthly allowance and is refused if you have none left.
- You need permission to run tests to use it. Developers and Viewers can read test runs but cannot start them.

Why did my issue go back to In progress?
The check still found the bug: the re-run test failed, or the page check judged that the problem is still there. Open the verification run from the issue's Activity tab, or try the issue's steps yourself. Fix the bug, deploy, then set Fixed again.
Why is my issue Fixed when the check didn't run?
If the check can't reach a verdict, for example because your app was unreachable, TestOptim applies the status you asked for without verification. The Activity tab shows "verification did not run". Make sure the live app is up, set the issue to In progress, then set Fixed again to start a new check.
Tips
- For many issues, use a bulk status change. The first 10 selected issues are verified together in one check, so this takes a while. The rest are set to the new status directly, without verification. See Update, export and clean up issues in bulk.
- If the Jira integration is connected with Run tests automatically on Jira status change turned on, moving a ticket to Done in Jira can also start a check. See Connect Jira.
Related
Keep reading
- IssuesReview issues found by TestOptimSee where TestOptim issues come from, what severity and status mean, and how to filter, search and open an issue to read the steps to reproduce.
- IssuesUpdate, export and de-duplicate issues in bulkSelect several TestOptim issues to assign them, change status, export CSV or delete them, and clean up the same bug filed more than once.
- Test runs & resultsRead test run results and watch recordingsRead a finished TestOptim run: which test cases passed or failed, the issues it filed, the video recording with a chapter per test, and the trace.
- Getting startedQuick start: find your first bugsGo from a new account to a list of real bugs in five steps. Create a project, explore your app, generate test cases, run a few tests and review the issues.