# Validate.QA

> Validate.QA is an autonomous QA agent for web applications. Paste a URL and it maps the app, walks every page, clicks every button, watches every API call, captures console and network errors, runs security checks, and generates a native Playwright test suite covering UI, API, security, console, and network. Tests are standard `@playwright/test` .spec.ts files committed to your own repo (no vendor lock-in), self-heal when selectors drift, and run in your existing CI. Drive it over MCP from Cursor, Claude Code, or Codex, from a single URL via autonomous discovery, or by narrating a browser flow with the Chrome extension.

## What Validate.QA Does

Validate.QA turns a single URL into a complete, self-maintaining Playwright suite:

- **Autonomous Site Discovery**: Paste a URL and a headless agent maps every page, form, flow, and API endpoint, then plans and generates test coverage automatically - no manual recording required.
- **UI + API + Security + Console + Network Coverage**: One run produces UI flow tests, Playwright API test chains from observed calls, basic security checks, and console/network error assertions.
- **AI Test Generation**: Generates complete Playwright test files with verified selectors picked by a 9-tier strategy (test-id, ARIA role, label, placeholder, text, id, name, class, CSS path) - not brittle CSS paths. Assertions are proven against the live DOM before they are written.
- **Native .spec.ts Export — No Lock-In**: Output is standard `@playwright/test` code committed to your GitHub repo. You own it and run it with `npx playwright test`.
- **Self-Healing Tests**: When your UI changes, AI re-discovers selectors and rewrites broken steps via a 5-phase batch healer. No more flaky test maintenance.
- **Regression Suites & Scheduling**: Generate full regression suites with `playwright.config.ts`, auth setup, and `regression.suite.ts`. Schedule runs and auto-heal failures in CI.
- **CI/CD Integration**: GitHub Actions workflow generation, trigger API with bearer tokens, and webhook notifications plug into the pipeline you already have.
- **MCP-Native**: A full Model Context Protocol server lets Cursor, Claude Code, and Codex drive generation, healing, and runs directly from your AI editor.
- **Voice-Guided Recording**: Optionally install the Chrome extension, press Record, and narrate what you're testing in plain English. Whisper transcribes your voice and the agent maps it to browser actions.
- **QA Copilot**: Chat-based AI assistant that understands your test suite and helps debug, extend, and improve coverage.

## How It Works

1. Paste your app's URL (plus a one-line brief). A headless agent explores the app - every page, form, flow, and API call.
2. It plans coverage and generates native Playwright tests, picking stable selectors and proving assertions against the live DOM.
3. Review the generated .spec.ts - each is verified by a real run before it's promoted; edit or keep them, they live in your repo.
4. Run on demand, schedule recurring runs, or trigger from CI; results land in the dashboard.
5. When the app changes, tests self-heal; genuine regressions are flagged as bugs instead of hidden.

You can also drive everything over MCP from Claude Code, Cursor, or Codex, or record a specific flow with the Chrome extension and narrate intent - both funnel into the same pipeline.

## Technical Details

- **Test Output**: Standard Playwright test files (TypeScript) - no vendor lock-in
- **AI Models**: Supports multiple providers (xAI Grok, OpenAI, Anthropic Claude, MiniMax, NVIDIA, DeepSeek)
- **Execution Modes**: Playwright direct, MCP Agent (self-healing), Playwright Native (generated code)
- **Integrations**: GitHub (auto-commit tests to repo), CI/CD pipelines, Chrome extension
- **Architecture**: Multi-tenant platform with per-org isolated databases

## Plans & Pricing

- **Standard**: Launch special with a 30-day free trial, no credit card. Includes the full platform on one shared-workspace project: 30 tests, 20 dashboard test runs/day, 1 survey/day, 2 Discovery runs/day (or 30 tests, whichever comes first), 1 suite run/day, and 5 self-heals/day.
- **Standard Plus** ($99.99/month): higher shared-workspace usage with 200 tests, 100 dashboard test runs/day, 5 suite runs/day, 3 surveys/day, 10 Discovery runs/day (or 200 tests, whichever comes first), 20 self-heals/day, and 2 concurrent discoveries.
- **Pay as you go**: prepaid usage credits with no monthly subscription. Manual test runs are $0.15, suite runs are $0.50, Discovery runs are $2.00, and self-heals are $0.75.
- **Enterprise**: dedicated runner, custom domain, SSO, audit log, custom AI models, annual contract.

## How Validate.QA tests (one URL, five kinds of coverage)

A single exploration pass becomes UI tests, API tests, console/network checks, and a security audit. How each works:

- [UI testing](https://dev.validate.qa/how-we-test/ui-testing) - 9-tier selector strategy (test-id > role > label > placeholder > text > id > name > class > CSS) and assertions proven against the live DOM before they're written.
- [API testing](https://dev.validate.qa/how-we-test/api-testing) - observes the API calls your UI makes, then builds Playwright request chains (login → create → read → delete) with assertions on status and payload. No OpenAPI spec required.
- [Console & network testing](https://dev.validate.qa/how-we-test/console-network-testing) - instrumented context captures console errors and full HAR, so a page that looks fine but logs an error or fails a background request is caught.
- [Security testing](https://dev.validate.qa/how-we-test/security-testing) - a 7-phase security audit derived from the captured HAR: headers, cookie/auth handling, exposed data, transport, and common misconfigurations.
- [How we test (overview)](https://dev.validate.qa/how-we-test)

## Documentation

Public docs for using Validate.QA:

- [Getting started](https://dev.validate.qa/docs/getting-started) - create a project, generate tests from a URL, review and run them.
- [How it works](https://dev.validate.qa/docs/how-it-works) - the explore → plan → generate → verify → heal pipeline and test lifecycle.
- [The tests you get](https://dev.validate.qa/docs/playwright-tests) - native @playwright/test .spec.ts you own; no DSL, no lock-in, runs with npx playwright test.
- [Self-healing tests](https://dev.validate.qa/docs/self-healing) - how broken tests are repaired and real app bugs are flagged instead of hidden.
- [Running tests in CI/CD](https://dev.validate.qa/docs/ci-cd) - trigger tokens, JUnit XML export, GitHub Actions, and scheduled runs.
- [MCP server](https://dev.validate.qa/docs/mcp-server) - manage tests from Claude, Grok, Grok Bot, Codex, Claude Code, and Cursor over Model Context Protocol (OAuth connectors or stdio).
- [Connect Claude, Grok, and Codex](https://dev.validate.qa/blog/connect-claude-grok-codex-to-validate-qa) - add Validate.QA as a remote MCP connector; no PAT.
- [Docs home](https://dev.validate.qa/docs)

## Answers (common questions, answered directly)

Every common question — AI test generation from a URL, autonomous discovery, self-healing Playwright suites, API/security checks, CI/CD, pricing, comparisons — is answered directly on the FAQ hub. The page is prerendered (full HTML without JavaScript) and carries FAQPage structured data:

- [FAQ - all questions, answered directly](https://dev.validate.qa/faq)

## Comparisons (Validate.QA vs alternatives)

Honest, side-by-side comparisons of how Validate.QA differs from the tools teams evaluate for automated testing. Validate.QA's core differentiator across all of them: paste a URL, get a native Playwright suite (UI, API, security, console, network) that you own and that self-heals.

- [All comparisons](https://dev.validate.qa/compare)
- [Validate.QA vs Playwright Codegen](https://dev.validate.qa/compare/playwright-codegen) - autonomous generation vs recording
- [Validate.QA vs Selenium](https://dev.validate.qa/compare/selenium) - AI generation vs hand-coded WebDriver
- [Validate.QA vs Cypress](https://dev.validate.qa/compare/cypress) - generated Playwright vs hand-written Cypress
- [Validate.QA vs mabl](https://dev.validate.qa/compare/mabl) - exportable Playwright vs proprietary low-code
- [Validate.QA vs Katalon](https://dev.validate.qa/compare/katalon) - autonomous Playwright vs record-and-script
- [Validate.QA vs Virtuoso](https://dev.validate.qa/compare/virtuoso) - autonomous discovery vs natural-language authoring
- [Validate.QA vs testRigor](https://dev.validate.qa/compare/testrigor) - Playwright output vs plain-English commands
- [Validate.QA vs Testim](https://dev.validate.qa/compare/testim) - autonomous Playwright vs AI record-and-playback
- [Validate.QA vs Applitools](https://dev.validate.qa/compare/applitools) - functional generation vs visual AI (complementary)
- [Validate.QA vs BrowserStack](https://dev.validate.qa/compare/browserstack) - test generation vs cloud execution grid
- [Validate.QA vs QA Wolf](https://dev.validate.qa/compare/qa-wolf) - self-serve AI platform vs managed service
- [Validate.QA vs Octomind](https://dev.validate.qa/compare/octomind) - both generate Playwright; breadth from one URL
- [Validate.QA vs Checksum.ai](https://dev.validate.qa/compare/checksum) - autonomous from your app vs from production traffic
- [Validate.QA vs Momentic](https://dev.validate.qa/compare/momentic) - autonomous discovery vs low-code authoring
- [Validate.QA vs TestSprite](https://dev.validate.qa/compare/testsprite) - live-app URL discovery vs PRD/codebase MCP planning
- [Validate.QA vs Functionize](https://dev.validate.qa/compare/functionize) - owned Playwright + URL discovery vs enterprise NLP cloud

## Links

- [Home](https://dev.validate.qa/)
- [What is Validate.QA](https://dev.validate.qa/what-is-validate-qa)
- [Accuracy benchmark & methodology](https://dev.validate.qa/benchmark)
- [Best AI QA Agents (2026)](https://dev.validate.qa/best-ai-qa-agents)
- [See it run: URL to Playwright suite](https://dev.validate.qa/example-run)
- [How It Works](https://dev.validate.qa/how-it-works)
- [Documentation](https://dev.validate.qa/docs)
- [Pricing](https://dev.validate.qa/pricing)
- [How We Test](https://dev.validate.qa/how-we-test)
- [Compare](https://dev.validate.qa/compare)
- [AI Playwright Test Generator](https://dev.validate.qa/ai-playwright-test-generator)
- [App Feature Discovery for QA](https://dev.validate.qa/app-feature-discovery)
- [Sign Up](https://dev.validate.qa/signup)
- [Security](https://dev.validate.qa/security)
- [Privacy Policy](https://dev.validate.qa/privacy)
- [Terms of Service](https://dev.validate.qa/terms)
- [Chrome Extension](https://chromewebstore.google.com/detail/validateqa)
- [X / Twitter](https://x.com/Validate_QA)