visual-qa

You can automate visual smoke tests for UI regressions by running a conductor workflow on the main branch that captures PASS/FAIL results into a checkpoint file for traceability. Build the extension or app first, then execute the visual-qa workflow.

A visual QA checkpoint verifies UI changes by running lightweight smoke checks on the extension and backend, then logging failures to a JSON file for quick rollback. It provides an auditable PASS/FAIL record of visual integrity.

No external dependencies are required to run visual UI smoke checks beyond the conductor environment itself. The workflow operates self-contained within the environment and writes its traceable results directly to a local checkpoint file.

Visual smoke test results for post-merge UI verification are logged to the .checkpoints/visual-qa.json file. This JSON record provides full audit traceability and captures plus/minus PASS or FAIL outcomes for quick review.

Yes, you can use this lightweight visual QA workflow for backend changes because it explicitly verifies both the extension and backend. It captures UI-facing regressions caused by backend modifications and writes the results to a checkpoint file.

The limitation of lightweight visual smoke tests for UI regressions is that they are designed for quick post-merge verification rather than deep functional testing. They provide a rapid PASS/FAIL traceability record but do not replace comprehensive test suites.