The request asks what to use for testing changes; no specific product is named, so the strongest fits are the tools whose pages or actions directly cover validating and verifying code or UI changes. Playwright 7 runs end-to-end browser tests, pytest 4 runs Python unit tests, Streamlit's checking-changes action 12 validates changes before commit, Shiplight 6 verifies UI changes via MCP, and UI Verify 9 does visual regression testing for coding agents.
- 1
Playwrightplaywright.devwebsite read, tools not yet checked
Full-featured test runner for end-to-end testing across Chromium, Firefox and WebKit, with auto-waiting assertions, tracing and parallelism.
official:SDK · playwright+230 community tools built for it
- 2
pytestpytest.orgverified and signed
Python testing framework for writing small, readable tests that scale to complex functional testing of applications and libraries.
+22 community tools built for it
for agents: unittest · test
- 3
Shiplight AI Docsshiplight.aiverified and signed
The verify action checks UI changes in the browser using Shiplight MCP tools.
official:MCP server · Shiplightpackage · Shiplight+1 community tools built for it
for agents: verify · create-tests · triage
- 4
UI Verifyuiverify.aiverified and signed
Visual regression testing for Playwright, Storybook and Vitest, where an AI judge separates intended UI changes from real regressions.
for agents: setup-visual-testing · evaluate-run · factory
Sources
- 4pytest documentationdocs.pytest.org · read 2026-10-29
- 6Shiplight AI Docs — Autonomous QA Testing with MCP & YAML | %sdocs.shiplight.ai · read 2026-10-29
- 7Fast and reliable end-to-end testing for modern web apps | Playwrightplaywright.dev · read 2026-10-29
- 9UI Verify · Visual testing for coding agentsuiverify.ai · read 2026-10-29
- 12checking-changes: declares "checking-changes" (the record we read and signed)unfragile.ai · read 2026-10-24
For agents: the 10 actions behind this answer
scoutqa-test · scoutqa-test verified and signed
This skill should be used when the user asks to "test this website", "run exploratory testing", "check for accessibility issues", "verify the login flow works", "find bugs on this page", or requests automated QA testing. Triggers on web application testing scenarios including smoke tests, accessibil
checking-changes · checking-changes verified and signed
Validates all code changes before committing by running format, lint, type, and unit test checks. Use after making backend (Python) or frontend (TypeScript) changes, before committing or finishing a work session.
verify_behavior · fetchsandbox-mcp found in code, not yet checked
Prove a known fix survives a bug — the 'prove' half of reproduce→prove.
unittest · pytest verified and signed
PostTestHelpersTestClocks · Stripe API verified and signed
Create a test clock
verify · verify verified and signed
Verify UI changes in the browser using Shiplight MCP tools.
· Playwright website read, tools not yet checked
Web automation and testing for apps, scripts, and AI agents
· DebuggAI website read, tools not yet checked
DebuggAI tests your website or web app like a real user and catches bugs before your users do. AI-powered, no code, no setup. Move fast without breaking things.
setup-visual-testing · setup-visual-testing verified and signed
Set up UI Verify visual regression testing in a repo end to end — detect or scaffold the capture path (Storybook stories, a Playwright suite, or Vitest browser-mode component tests), install the uiverify CLI and wire it into CI, and author the first stories the economical, deterministic way from the
ansible/ansible-content-actions · ansible-content-actions verified and signed
A set of GitHub actions for testing Ansible collections.
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.