testsprite-cli

TestSprite's central claim is that the bottleneck moved. Writing code got fast; proving it still works did not. The vendor's own framing — three weeks to hand-write a 60-test suite at the published two-to-four-hours-per-end-to-end-test benchmark — is the honest version of that argument, and it is why a tool that generates a suite in ten minutes from a URL is worth a look even if you already have Playwright in the repo. The design choice that matters most is that tests run against the deployed app, not mocks. A parallel fleet of agents explores the live product, clicking through flows the way a user would, and tests are generated from what the agents actually find rather than inferred intent from source code. That is a meaningfully different failure mode from script-based frameworks: a pass means a person could plausibly do the thing. The cost is that you need a reachable staging or production app and internet access, because TestSprite runs the browsers on its own machines — the vendor is explicit that air-gapped testing is out. The failure bundle is the second real differentiator. One self-consistent payload per failure — failing step and neighbours, screenshots, DOM snapshots, test source, root-cause hypothesis, suggested fix — is the difference between an agent that can act on a red test and one that needs a human to triage the morning. Combined with Auto-Heal (repairs when the UI drifts, no selector rewrites) and retained passing tests, coverage compounds instead of decaying, which is the actual complaint behind most abandoned E2E suites. The 3.0 release (April 24, 2026) is where backend stopped being an afterthought. A rebuilt engine supports multi-dependency integration chains, Dynamic Variables for cross-test resource reuse, Auto Cleanup that wipes test-created resources after each run, Auto-Auth and Smart Rerun for stable nightly regression. The Data Flow view traces API invocations under different input scenarios. File fixtures (CSV, JSON, PDF, images) are uploaded once at project level and wired into both frontend and backend tests. The editable Feature Map, auto-extracted from a PRD upload, acts as ground truth for generation downstream — and the vendor makes a good point that a failing test also re-surfaces a dropped requirement mid-task, which no context window does on its own. Where it fits: AI-native teams and small startups without a QA hire, plus any developer in Claude Code, Codex or Cursor who wants merges gated before they land. The CLI (open source, npm) and MCP server mean the agent that wrote the code can also read the failure and fix it in the same session. Where it does not: teams who need behaviour-driven scripts with full control over selectors and assertions should stay on Playwright or Cypress — this is an autonomous verifier, a different category. Credit budgeting is the practical constraint. Free gives 150 credits per month and one test list; Starter gives 400 credits and 5 test lists for $19/mo after the