Product Feature
Verify Bug Fixes Before You Close the Issue
Bug fix verification is the check that a resolved issue is actually fixed on the live page before anyone closes it. In OverlayQA, Verify fix rechecks the page the issue was captured on and saves the verdict with before and after screenshots.
How Verify Fix works
Open a resolved issue and press Verify fix. OverlayQA captures the page again and runs the check that fits the issue: accessibility issues rerun the axe-core rule that flagged them, design token issues remeasure the CSS property that was captured, and bugs and mismatches compare the original screenshot with a fresh one using AI. The result reads Fix verified, Passed (with caveat), Fix failed, Inconclusive, or Couldn't verify, and it stays on the issue with both screenshots.
The verdict is advice. After a pass you choose Mark as verified or Reopen, and after a failure you choose Reopen as regressed or Retry. To retest a release, select resolved issues on the Issues page and choose Verify fixes: OverlayQA groups them by page and the Chrome extension checks each page in turn, including staging and pages behind a login.
Why verify fixes before closing issues
- Resolved is not fixed: a resolved status says a developer shipped a change. It does not say the page now looks right.
- Retesting takes a reviewer: someone opens each page, finds the element, and compares it with the screenshot in the original report.
- No proof of the fix: when a client asks whether something was fixed, a closed ticket is not evidence. A saved verdict with before and after screenshots is.
Frequently asked questions about Verify Fix
- What is bug fix verification?
- Bug fix verification is the check that a resolved issue is actually fixed on the live page before anyone closes it. In OverlayQA, Verify fix rechecks the page the issue was captured on and saves the verdict with before and after screenshots.
- How does Verify Fix decide whether a fix worked?
- It runs the check that fits the issue. Accessibility issues rerun their axe-core rule, design token issues remeasure the captured CSS property, and other issues compare the original screenshot with a new one using AI. The result reads Fix verified, Passed (with caveat), Fix failed, Inconclusive, or Couldn't verify.
- Does Verify Fix close or reopen issues on its own?
- No. The verdict is advice, and the call stays with your team. After a pass you choose Mark as verified or Reopen. After a failure you choose Reopen as regressed or Retry. Inconclusive and Couldn't verify never count as a pass.
- Which issues can be verified?
- Issues marked Resolved, Verified, or Closed that still have their original screenshot. General and Improvement issues hold questions and suggestions with nothing on the page to recheck, so change the type to Bug or Mismatch to verify one.
- Can it check staging, localhost, or pages behind a login?
- Yes, with the Chrome extension, which checks the page you have open with your signed-in session. From the dashboard, issues on public pages are checked from OverlayQA's servers, and issues on local or private pages open in the extension instead.
- Can I verify many fixes at once?
- Yes. Select resolved issues on the Issues page and choose Verify fixes. OverlayQA groups them by page, and the extension checks each page in turn.
- Can an AI coding agent verify a fix?
- Yes. The OverlayQA MCP server includes a verify_issue tool that checks a resolved issue on its public page and returns the saved verdict and explanation, so an agent can confirm its own fix.
- Is Verify Fix on every plan?
- Yes. Every plan includes a monthly allowance of verifications for each project.