Prompt

How do I review and approve intentional UI changes in visual tests?

Technology / Testing & QA1 observationLast seen Oct 27, 2026

Latest observation

Oct 27, 2026OpenAI APIWeb search: off

To review and approve intentional UI changes in visual tests, use a workflow that makes it easy to compare the new screenshots against the baseline and then update the baseline only when the change is expected.

Typical workflow

  1. Run the visual test suite

    • Your test tool captures new screenshots and compares them to the stored baseline images.
  2. Inspect the diffs

    • Review side-by-side comparisons or overlay diffs.
    • Check whether the change is expected, such as:
      • a design update
      • a text/content change
      • a responsive layout adjustment
      • a browser rendering difference
  3. Approve the change if intentional

    • If the visual difference is valid, mark it as approved in your visual testing tool.
    • This usually updates the baseline image or stores the new screenshot as the approved version.
  4. Reject or fix if unintentional

    • If the difference is a regression, fix the code and rerun the tests.

Common ways to approve

  • Via UI dashboard: most visual testing services let you open failed tests and click “Approve” or “Accept.”
  • Via CLI or test runner: some tools let you accept new baselines from the command line.
  • Via branch/PR workflow: approve changes in the visual review tool, then merge the PR once all checks pass.

Best practices

  • Only approve changes after confirming they’re expected.
  • Review diffs at the right screen sizes and browsers.
  • Keep approvals tied to a pull request so the reason for the change is documented.
  • Prefer reviewing with real examples rather than blindly updating all baselines.

Example with common tools

  • Percy: review builds in the Percy dashboard and click Approve.
  • Chromatic: inspect changes and click Accept changes.
  • Applitools: mark differences as accepted in the test results view.

If you tell me which visual testing tool you’re using, I can give the exact approval steps for it.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.