# TestWatch > TestWatch is an AI end-to-end testing service: describe a user flow in plain English, and it writes a readable Playwright test, runs it on a schedule or from CI, tells you why a failure happened, and proposes a fix you approve. Passing runs make no AI calls. - Pricing: you pay for the tests you create; runs are included and never billed per run. No AI credits: writing and fixing tests is part of the plan price; paid plans have a daily safety limit against runaway AI use (about 20 test generations a day on Starter, 60 on Team, shared with automatic fixes). Free: 5 tests, 500 runs a month, 2 apps and one daily schedule. Unlimited teammates, no card. Start on Free; upgrade to Starter or Team in the app (for businesses). Schedules run hourly on Starter and as often as every 15 minutes on Team. Enterprise starts at $799 a month: custom limits, schedules as often as every 5 minutes, invoicing and a signed order form. - Fixes to your main tests change only locators and waits, never assertions, and apply only after you approve. On a pull-request preview (Starter or higher), a fix may also update the text a check expects when the PR renamed it; it runs on that PR only after someone accepts it, and is applied to the main test automatically once it passes there twice (with a notice and Undo). - Clear failure reasons: CAPTCHA or bot wall, app down, bad credentials, missing 2FA. It doesn't bypass CAPTCHAs. - Devices: one test per screen size (mobile, tablet, desktop), run on every device you pick: Pixel, iPhone, Galaxy, iPad, Chrome and Safari (Safari = WebKit, emulated). Real browser engines with emulated screens, not real hardware. No Firefox. Devices take no test slots; each device run counts as a run. - Logins: test accounts with passwords and authenticator-app (TOTP) 2FA. Each test signs in as the account you pick for it, or not at all; each environment uses that account's shared login, its own login, or skips the account (those tests are skipped there, not failed). Built-in test email inboxes on every plan handle verify links, magic links, password resets and emailed codes. SMS codes and signing in through Google, GitHub or SSO in the app under test aren't supported. - Runs start on a schedule (presets or cron) or by hand on every plan. From CI on Starter or higher: the GitHub Action testwatch-dev/action, the CLI @testwatch/cli, the REST API, signed deploy hooks, preview-URL runs and an MCP server for AI coding agents (Claude Code, Cursor, Codex, Copilot, claude.ai, ChatGPT; OAuth sign-in or API key) that run tests, read failures and generate new tests (the agent must confirm each generation). JUnit download on every plan. - Alerts: failure emails to the owner on every plan; Slack, email and signed webhook channels on Starter or higher; a weekly summary email. - Eval on our own fixture apps (87 trials, October 2026): 94% good outcomes, 1% false green, 0% brittle, 5% generation failed, 0% stopped on a false blocker (rounded). Method and every case: https://testwatch.dev/eval - Tests are standard Playwright code you can read and copy. On every plan, export the whole suite as a runnable Playwright project (npx playwright test). - EU-based; servers in Vienna, Austria; files in Cloudflare R2; AI requests not pinned to the EU. For plan limits and answers to common questions, see https://testwatch.dev/llms-full.txt. Every docs page is also plain Markdown: add .md to its URL, e.g. https://testwatch.dev/docs/api.md and https://testwatch.dev/docs/cli.md (the overview is https://testwatch.dev/docs/index.md). ## Pages - [How it works](https://testwatch.dev/how-it-works) - [Features](https://testwatch.dev/features) - [Pricing](https://testwatch.dev/pricing) - [Test cost calculator](https://testwatch.dev/tools/test-cost-calculator) - [Security](https://testwatch.dev/security) ## Guides - [Self-healing Playwright tests](https://testwatch.dev/self-healing-playwright-tests) - [AI Playwright test generator](https://testwatch.dev/playwright-test-generator) ## Docs - [Overview and quickstart](https://testwatch.dev/docs) - [GitHub Action](https://testwatch.dev/docs/github-action) - [CLI](https://testwatch.dev/docs/cli) - [REST API](https://testwatch.dev/docs/api) - [AI coding agents (MCP)](https://testwatch.dev/docs/ai-agents) - [Deploy hooks and webhooks](https://testwatch.dev/docs/deploy-hooks-and-webhooks) - [Preview URLs and protected staging](https://testwatch.dev/docs/preview-urls-and-protection) - [Test fixtures: inboxes and test data](https://testwatch.dev/docs/fixtures) - [Export your suite](https://testwatch.dev/docs/export) - [Data export and switching](https://testwatch.dev/docs/data-export) ## Use cases - [Logins with 2FA](https://testwatch.dev/use-cases/test-login-2fa-totp) - [Checkout flows](https://testwatch.dev/use-cases/test-checkout-flow) - [Testing without a QA team](https://testwatch.dev/use-cases/e2e-testing-without-qa-team) - [Email verification](https://testwatch.dev/use-cases/test-email-verification) - [Preview deploys](https://testwatch.dev/use-cases/test-preview-deploys) - [Clean test data](https://testwatch.dev/use-cases/clean-test-data) - [Export your suite](https://testwatch.dev/use-cases/export-playwright-suite) ## Compare - [TestWatch vs tester.army](https://testwatch.dev/compare/tester-army) - [TestWatch vs Claude Code + Playwright MCP](https://testwatch.dev/compare/diy-claude-code-playwright-mcp) - [QA Wolf alternatives](https://testwatch.dev/compare/qa-wolf-alternative) - [Momentic alternatives](https://testwatch.dev/compare/momentic-alternative) - [Octomind alternatives](https://testwatch.dev/compare/octomind-alternative) - [TestWatch vs Playwright Test Agents](https://testwatch.dev/compare/playwright-test-agents) - [Best AI end-to-end testing tools](https://testwatch.dev/compare/best-ai-e2e-testing-tools) ## Blog - [Playwright anti-patterns: 5 flaky code shapes we reject](https://testwatch.dev/blog/playwright-anti-patterns) - [Why Playwright tests pass locally but fail in CI](https://testwatch.dev/blog/playwright-pass-locally-fail-in-ci) - [How to evaluate AI testing tools: count the false greens](https://testwatch.dev/blog/how-to-evaluate-ai-testing-tools) ## Company - [About](https://testwatch.dev/about) - [Blog](https://testwatch.dev/blog) - [Changelog](https://testwatch.dev/changelog) - [How we measure](https://testwatch.dev/eval)