Published Updated
Guides for QA, testing and dev teams
Every TestChimp guide in one place: testing techniques with Playwright examples, explainers on QA in an agentic SDLC, product how-tos, and side-by-side comparisons with other tools. New to TestChimp? Start with the quick intro or start a 14-day free trial, no credit card required.
QA guides
Testing techniques for real flows: auth, payments, OTP, email, UI patterns and more, with Playwright examples.
E2E foundations and common gotchas
- All testing guides
Authoritative scenario testing guides, payments, auth, AI, integrations, and industry patterns with probe-first E2E and TestChimp QA workflow.
- Common E2E testing mistakes and fixes
Selector drift, world-state pollution, flaky waits, and UI-only asserts, symptom-first fixes for Playwright E2E maintenance.
- E2E testing foundations
Seed routes, probe Assert, fixtures, and requirement traceability, the Arrange/Act/Assert building blocks behind reliable Playwright suites.
- Acceptance test examples: login, checkout and search
Acceptance test examples in Given/When/Then and checklist form for login, password reset, checkout and search.
- Alpha vs beta testing: differences, examples and when to use each
Alpha vs beta testing: who tests, where and when.
- API contract testing: how it works, tools and a starter setup
API contract testing checks that a provider and its consumers agree on requests and responses.
- API testing tools: 8 options compared
Compare API testing tools by where tests live, language and CI support: Postman, Bruno, Insomnia, Hoppscotch, REST Assured, Karate.
- Avoid test data collisions in parallel CI
Fix Playwright parallel workers colliding on shared coupons, emails, and carts, runId seed routes, worker-scoped fixtures.
- Canary testing: what it is, how it works and when to use it
Canary testing sends a small share of real traffic to a new version and watches metrics before a full rollout.
- Catch backend bugs that UI-only assertions miss
Why success toasts lie in E2E: use probe Assert on API and database state, and keep UI checks optional so backend bugs don't slip through.
- Fix E2E tests that break each other
Stop E2E tests from polluting shared data, per-run seed routes, runId-scoped fixtures, and probe Assert so parallel CI stays green.
- Fix E2E tests that break when selectors change
Playwright locators break after refactors when tied to CSS classes.
- Fix E2E tests that depend on run order
Fix order-dependent Playwright suites: independent Arrange per spec.
- Fix E2E tests that pass locally but fail on staging
Fix Playwright specs that pass locally but fail on preview or staging, BASE_URL, feature flags.
- Fix flaky waits and timeouts in Playwright
Playwright wait for should use locator auto-wait or expect.poll, not waitForTimeout.
- Fix hardcoded test data that flakes in CI
Replace fixed emails, coupons, and dates in Playwright specs, dynamic seed routes, runId fixtures.
- Fix shared login state polluting Playwright tests
Fix shared Playwright auth state with per-spec auth seeds, role-scoped sessions and runId isolation.
- Flaky tests: causes, detection and fixes
What a flaky test is, why E2E tests flake, how to detect flakes with Playwright retries and repeat-each, and a fix order that works.
- Manage E2E test data with seed routes and backend asserts
E2E test data management with per-run seed routes, probe endpoints, and scenario-annotation traceability, the expired-coupon pattern for any domain.
- Reach TMMi level 5 with data-driven QA
What TMMi Level 5 (Optimization) requires: defect prevention, quality control and test process optimization, and how TestChimp enables data-driven QA.
- Seed feature flags for stable E2E tests
Fix flaky Playwright specs when LaunchDarkly or env flags differ, posture fixtures, seed routes that force flag state, and probe Assert on gated APIs.
- Smoke test in software testing: what it is, examples and CI setup
A smoke test is a short check that a build works at all before deeper testing.
- Stop E2E tests leaking test data (teardown)
Fix E2E suites that pollute staging with orphan orders and users, prefer runId isolation over afterAll cleanup, and probe counts to catch leaks.
- Stop logging in for every Playwright test
Flaky tests often come from typing credentials in every Playwright spec.
- Test coverage metrics: which to track and which to ignore
Test coverage metrics explained: line, branch, function, mutation and scenario coverage.
- When mocking in E2E tests hides integration bugs
Fix Playwright suites that mock every API, use real routes and probes; reserve AIMock for LLM boundaries only so wiring and auth bugs surface in CI.
- When snapshot testing is too brittle for E2E
Replace full-page Playwright snapshots with probe Assert, stable structural checks, and targeted visual regression.
- When to use AI steps (ai.act, ai.verify) in Playwright
Use TestChimp ai.act and ai.verify sparingly for genuine product variance, never replace probe Assert or stable data-testid on forms and checkout.
- Why E2E tests are flaky and how to fix them
Fix startup E2E flake at the root: world-state fixtures, probe Assert, parallel-safe seeds and hybrid ai.act on brittle UI, not reruns or sleeps.
Auth and identity
- All auth and identity testing guides
Testing guides for Firebase, OAuth, MFA, CAPTCHA, RBAC and session flows: enterprise-grade auth E2E patterns for Playwright.
- CAPTCHA Testing: How to Test CAPTCHA-Enabled Flows
How to test CAPTCHA in Playwright with reCAPTCHA test keys, hCaptcha test mode, Turnstile and env bypass.
- How to test 2FA and MFA flows
How to test 2FA and MFA in Playwright: TOTP seeds via otplib, backup codes, SMS stubs, recovery flows, clock-aware fixtures and API probe enforcement.
- How to test Auth0 and Okta SSO in E2E
Enterprise SSO E2E, Auth0/Okta test tenants, programmatic tokens, SAML routing, org claims, and session refresh without brittle IdP UI clicks in CI.
- How to test Clerk authentication in Playwright
Clerk E2E, programmatic sign-in, org switching, session tokens, and per-run users without brittle hosted UI clicks in every spec.
- How to test Firebase authentication flows
Test Firebase Auth in E2E with the Auth emulator, custom tokens, email verification, phone OTP and per-run users, without shared staging accounts.
- How to test Google, GitHub, and social OAuth
Social OAuth E2E, popup vs redirect, denied consent, account linking, and sandbox apps with session probes instead of brittle provider UI clicks.
- How to test magic links and passwordless login
Passwordless E2E, Mailtrap inboxes, link expiry, bot prefetch, single-use tokens, with disposable emails and probe-based session Assert.
- How to test passkeys and WebAuthn in Playwright
Passkey E2E, virtual authenticators, registration vs login, and fallback paths when WebAuthn is unavailable in CI.
- How to test role-based access control matrices
RBAC E2E, role × resource × action matrices, 403 vs hidden UI, inherited roles, with fixture users, API probes, and combinatorial scenario coverage.
- How to test session expiry and refresh tokens
Session lifecycle E2E, idle timeout, refresh rotation, concurrent sessions, absolute expiry, with Playwright clock and token probes.
Payments, billing and business flows
- All business flow testing guides
Testing guides by business flow: payment, subscription, inventory, licensing and admin flows, from checkout to seat limits, with Playwright.
- How to test admin dashboards and role permissions
Admin RBAC E2E, impersonation scope, horizontal privilege escalation negatives, audit trails, with role fixture users and probe Assert on admin APIs.
- How to test Apple Pay, Google Pay, and PayPal flows
E2E patterns for wallet payments: sandbox tokens, PayPal popups.
- How to test BNPL checkout (Klarna, Affirm, Afterpay)
BNPL E2E, redirect flows, approval/denial, webhook settlement, and probe Assert when payment is not immediate card capture.
- How to test free trial to paid conversion
Trial conversion E2E, expiry without card, mid-trial upgrade, feature lock, grace periods, with billing seeds, Stripe test clocks.
- How to test inventory updates and stock reservations
Parallel-safe inventory E2E for oversell races, reservation timeouts and backorders, using seeded SKUs, probe Assert and clock fixtures.
- How to test multi-vendor marketplace checkout
Marketplace E2E, multi-vendor carts, split payouts, vendor shipping rules, commission probes, with per-vendor seeds and ledger Assert.
- How to test Plaid Link and open banking flows in Playwright
Plaid sandbox E2E in Playwright: Link flow, OAuth institutions, public_token exchange and linked-account probes without flaky credential UI.
- How to test plan limits and feature flags
Entitlement E2E, gated UI vs API 403, metered limits, grandfathered features, with plan seeds, usage counters.
- How to test product configurators and custom builds
Configurator E2E, invalid combinations, async price recalc, saved builds, BOM validation, with option fixtures and price probes on each toggle.
- How to test referral and invite programs
Referral E2E, invite links, attribution cookies, double-redemption, and probe Assert on reward ledger, not vanity UI counters.
- How to test returns, refunds, and partial credits
Refund flow testing, partial credits, store credit, return windows, restocking fees, with Stripe test refunds, webhook probes, and seeded order dates.
- How to test seat limits, invites, and team growth
Seat licensing E2E, at-limit invites, seat reclaim on deactivate, overage billing, with org fixtures and seat-count probes on every role change.
- How to test shipping rates and fulfillment status
Shipping E2E, zone tables, free-shipping thresholds, carrier API timeouts, split shipments.
- How to test subscription billing, trials, and renewals
Test SaaS billing: trials, proration, dunning and plan changes with Stripe test clocks, webhook probes and entitlement assertions.
- How to test tax, VAT, and country-specific pricing
Regional pricing and tax E2E, VAT/GST, B2B exempt accounts, currency rounding, Stripe Tax, with geo fixtures and probe line items.
- How to test usage-based billing meters
Usage metering E2E, rollover credits, burst limits, billing period boundaries, with clock fixtures, meter probes.
- Stripe test cards and Stripe payment testing in Playwright
Stripe test card numbers for success, declines and 3D Secure, plus reliable Playwright tests for Checkout and webhooks.
- Test credit card numbers for Stripe, PayPal, Adyen, Braintree
Test credit card numbers for each payment provider's sandbox: Visa, Mastercard, Amex, declines and 3D Secure, plus how to use them in automated tests.
Email, OTP, webhooks and other integrations
- All integration testing guides
Testing guides for integrations: Stripe webhooks, email, SMS, maps, PDFs and Supabase, with third-party integration E2E patterns for Playwright.
- How to test Algolia and Elasticsearch search in Playwright
Algolia and Elasticsearch E2E in Playwright: index sync waits, dual-write lag, facet probes and per-run seeds.
- How to test CSV import and export
How to test CSV import and export in Playwright: malformed rows, header mismatch and export encoding, with seed files and parsed assertions.
- How to test embedded widgets and iFrames
How to test iframes and embedded widgets in Playwright: frameLocator, cross-origin embeds and SDK load races for Stripe-like and partner widgets.
- How to test file upload flows (CSV, images, docs)
How to test file uploads in Playwright: setInputFiles, size limits, MIME rejection and virus-scan pending states, with fixture files and probes.
- How to test map interactions and geolocation
How to test maps and geolocation in Playwright: geolocation mocks, Places autocomplete and marker clicks.
- How to test Next.js App Router and Server Actions in E2E
Next.js E2E, App Router navigation, Server Actions, route handlers, and probe Assert for mutations RSC UI cannot prove alone.
- How to test PDF generation and downloads
How to test PDF generation and downloads in Playwright: waitForEvent download, pdf-parse text assertions and dynamic dates, plus file validation.
- How to test SMS and OTP verification flows
OTP testing for SMS verification: Twilio test credentials, virtual numbers, resend cooldown, and an API inbox or stub provider.
- How to test Stripe webhooks in CI
Stripe webhook E2E, signature verification, idempotency, missed events, out-of-order delivery, with Stripe CLI and probe Assert.
- How to test Supabase apps with Playwright
Supabase E2E, Auth, RLS, and Realtime with service-role seeds, per-run users, and probe Assert for Lovable and Next.js stacks.
- How to test transactional email flows
Email E2E with Mailtrap or similar, verification, OTP, password reset, with disposable inboxes and parallel-safe workers.
- How to test web push notification preferences
How to test web push notification preferences: permission prompts, unsubscribe and payload deep links, using service worker stubs.
- How to test webhooks and async event processing
How to test webhooks and async events: idempotency, out-of-order delivery and poison messages, with polling probes and dead-letter queue patterns.
UI patterns
- All UI pattern testing guides
Testing guides for UI patterns: forms, search, i18n, websockets, grids, GDPR and non-functional checks, with cross-cutting Playwright patterns.
- How to catch non-functional bugs in E2E tests
Beyond functional asserts, ExploreChimp on SmartTest paths for latency, confusing errors, accessibility gaps.
- How to test calendar booking and scheduling
How to test calendar booking and scheduling: slot availability, timezones and double-booking prevention, with slot seeds and booking probes.
- How to test data grids, sorting, and bulk actions
How to test data grids, sorting and bulk actions in Playwright: virtual scroll, sort and filter combos and bulk select, with row-id probes.
- How to test dates, timezones, and scheduling
How to test dates, timezones and scheduling: Playwright clock, DST boundaries and UTC vs local display, with frozen-time fixtures.
- How to test drag-and-drop and sortable lists
How to test drag-and-drop and sortable lists in Playwright: dragTo, library-specific handlers and touch, with probe-based order assertions.
- How to test form validation and error states
Form validation E2E, client vs server rules, async errors, accessibility, with field-level scenarios and probe Assert.
- How to test GDPR export, delete, and consent flows
Privacy E2E, data export completeness, delete cascade, consent version, with audit probes and regulatory fixtures.
- How to test infinite scroll and pagination
How to test infinite scroll and pagination: duplicate fetch prevention, end-of-list and scroll containers, with network wait patterns.
- How to test localization and i18n flows
How to test localization and i18n: locale switching, RTL and currency formats, with locale fixtures and ExploreChimp for layout breaks.
- How to test mobile web and responsive checkout
Mobile web E2E, viewports, touch targets, responsive breakpoints, Apple Pay and Google Pay.
- How to test rich text and WYSIWYG editors
How to test rich text and WYSIWYG editors in Playwright: contenteditable, toolbar actions and paste sanitization, with stored-HTML probes.
- How to test search, filters, and faceted navigation
How to test search, filters and faceted navigation: URL state, zero results and filter combos, with a seeded catalog and result-count probes.
- How to test video and audio player controls
How to test video and audio players in Playwright: play and pause, seek, captions and autoplay policies, with stub media assets.
- How to test WebSockets and live UI updates
How to test WebSockets and live UI updates: event ordering, reconnects and stale UI, with message fixtures and probe fallback.
Testing AI features
- All AI feature testing guides
Chatbots, agents, RAG, LLM output validation, streaming, and canvas, evals plus E2E with AIMock, ai.act/ai.verify, and probe Assert.
- How to test AI agent workflows and tool calling
Agent workflow E2E, tool failure, retries, idempotent side effects, human approval, with stub APIs and probe Assert.
- How to test canvas, charts, and visual widgets
Canvas and chart E2E, coordinate-free ai.act, WebGL stability, drill-down, with probes for data state over pixel clicks.
- How to test chatbots and conversational UIs
Test chatbots and conversational UI with hybrid Playwright, AIMock golden responses, offline evals, and probe Assert.
- How to test RAG and knowledge-base search
RAG E2E, fixture corpora, citation checks, empty retrieval, access control, with evals for recall and probes for retrieval IDs.
- How to test streaming AI responses
How to test streaming AI responses in Playwright: partial render, abort and mid-stream errors, with completion waits and final-state assertions.
- LLM Testing: How to Validate LLM Output in E2E
LLM testing for structured JSON, semantic checks, and golden sets, with evals for regression and AIMock for deterministic E2E.
Industry guides
- All industry testing guides
Industry-specific QA guides for ecommerce, fintech, AI apps, SaaS onboarding and flaky E2E reliability, with Playwright and TestChimp patterns.
- How startups test fintech web apps
Fintech E2E for startups: transfers, daily limits, idempotency keys, ledger probes and compliance-aware scenarios.
- How to test AI-powered web applications
Test AI web apps with AIMock, hybrid ai.act and ai.verify, offline prompt evals and probe Assert on tool side effects, not exact LLM string matching.
- How to test audit logs and compliance trails
How to test audit logs and compliance trails: immutable records, who-did-what attribution and retention, with probes on log entries.
- How to test cart and promo code scenarios
Parallel-safe cart and coupon E2E: stacking rules, run-scoped promos, race conditions and probe asserts on discounts, not shared staging codes.
- How to test CMS content publishing workflows
How to test CMS publishing workflows: draft, preview, scheduled publish and rollback, with content-state probes in Playwright.
- How to test e-signature and document workflows
How to test e-signature workflows: sign order, envelope expiry and witness flows, with the DocuSign sandbox and PDF assertions.
- How to test ecommerce checkout flows without flaky tests
Reliable ecommerce checkout E2E: run-scoped coupons, payment probes, parallel CI and TrueCoverage by payment method and country.
- How to test EdTech course enrollment and progress
How to test EdTech course enrollment and progress: prerequisites, waitlists and progress tracking, with enrollment seeds and progress probes.
- How to test healthcare patient portals
How to test healthcare patient portals: role separation, appointment policies and PHI-safe test data, with HIPAA-aware fixtures.
- How to test HR and applicant tracking flows
HR/ATS E2E, multi-stage pipelines, knock-out questions, PII handling, with stage fixtures and compliance-aware probes.
- How to test insurance quote and bind flows
How to test insurance quote and bind flows: multi-step wizards, rating tables and bind vs quote-only, with rate fixture seeds.
- How to test multi-tenant SaaS isolation (IDOR, RLS)
Multi-tenant SaaS E2E: IDOR URL probes, cross-tenant API negative tests, Postgres RLS and org-scoped seeds, so empty UI states don't hide data leaks.
- How to test real estate search and listing flows
How to test real estate search and listings: map and list sync, saved searches and filters, with geo listing seeds.
- How to test SaaS onboarding flows
SaaS onboarding E2E with screen-state checkpoints, activation funnel probes, step seeds and ExploreChimp UX checks, not monolithic signup scripts.
- How to test travel booking flows (hotels, flights)
Travel booking E2E: inventory holds, timezone checkout, fare rules and cancellation probes.
Performance and load testing
- All performance testing guides
Guides to load testing, volume testing, k6 vs JMeter vs Locust, load patterns, latency and HTTP error metrics.
- Find slow, janky UX before users churn
Catch performance and UX regressions that functional tests miss.
- k6 vs JMeter vs Locust: which load testing tool
Compare Grafana k6, Apache JMeter, and Locust for load and volume testing, language, CI fit, arrival-rate models.
- Load testing patterns: ramp, spike, soak and stress
Choose the right load pattern: ramping VUs, spike, soak, stress, open vs closed models and constant arrival rate, so k6 results match real demand.
- Performance regression testing across releases
Catch performance degrades by comparing p95, fail rate, and 4xx/5xx on matching k6 runs.
- Performance test metrics that matter
What to record in a load or volume test, p95 latency, HTTP 4xx vs 5xx, fail rate, and VUs over time, and how each metric changes a ship decision.
- Performance testing for agentic teams with k6 journeys
Scenario-linked k6 journeys and comparable runs across releases.
- What is load testing and how to run it
Load testing checks whether N concurrent users can finish a real journey within latency and error SLOs, using ramping VUs and think time.
- What is volume testing
Volume testing checks whether a journey holds up when a tenant has a large dataset: indexes, N+1 queries and pagination, without more users.
Test management and QA practice
- E2E tests as a map of your app's user journeys
Treat your end-to-end suite as a map of app pathways, not a pile of scripts.
- Exit-safe test management: keep tests and plans in Git
Own your test plans and tests in your repo so leaving a vendor costs nothing.
- Manual testing with requirement traceability
Keep manual test sessions linked to scenarios and stories.
- One test codebase for web and mobile apps
How to share test plans and Playwright-style tests across web, iOS and Android.
- Prioritize test cases by real user behaviour
Rank test cases by how often users actually take each path.
- Requirement traceability without spreadsheets
Link requirements to tests in code instead of maintaining a matrix by hand.
- Test planning as code explained
Version-controlled, agent-readable test plans and why they matter.
- Test plans in code vs Jira with an MCP
Why plans in Git still win even when Jira exposes an MCP server.
- Trace UX bugs to business impact
Find which bugs slow down checkout and other key flows.
- Turn a manual test session into an automated test
Capture a manual session once, then convert it to a Playwright test.
- Why your E2E tests are unreliable
The root causes behind flaky end-to-end suites and what fixes them.
Dev guides
How QA fits an agentic SDLC: AI-written tests, CI, and the evidence you need to ship with confidence.
Agentic SDLC and AI-written tests
- QA in the age of AI
Modern QA is shifting from manual script maintenance to AI-driven test creation, orchestration, and coverage intelligence.
- A practical E2E testing framework for startups
E2E testing for startups: a practical framework with Arrange/Act/Assert, seed routes, probe Assert, markdown plans.
- Agents weakening test assertions: how to catch it
Coding agents sometimes loosen assertions or special-case tests to get green.
- Backend asserts vs UI assertions in E2E tests
Methodology for E2E assertions, when probe endpoints beat UI checks, the expired-coupon pattern, and how to combine both without false greens.
- Better requirements make better agent output
Check requirements for gaps and ambiguity before agents build or test them.
- Boiling the QA lake: full coverage is now affordable
With agents writing tests, broad coverage stops being a luxury. What changes for QA.
- Build vs buy QA tooling in the LLM era
LLMs let you build anything, not everything. How to decide what QA tooling to build and what to buy.
- Check that AI-written Playwright tests can actually fail
A quick way to catch tests that pass no matter what the app does.
- Claude writes your tests: deciding which ones matter
When an agent writes the tests, someone still has to decide which ones count.
- How AI test generation works
How AI test generation works with Playwright SmartTests, markdown plans, agents, and TestChimp per-PR workflows.
- How to do QA without a dedicated QA team
How startups automate QA without hiring, developer-led workflows, /testchimp on every PR, markdown plans, and agent maintenance instead of a QA org.
- How to trust AI-written tests
A green test written by the AI that wrote the code proves little.
- Lessons for building AI agents (from Memento)
Agents see snapshots, not a continuous stream, so write instructions the way the hero of Memento needs them.
- Playwright MCP: what it is, setup, and where it fits
Playwright MCP lets an AI agent drive a real browser through accessibility snapshots.
- QA for coding agents: Claude Code, Cursor and Devin
Claude Code, Cursor and Devin can write and run tests.
- Spec-driven testing: test against your spec
Spec-driven testing ties every test to a written spec scenario.
- Trace agent outcomes back to workflow policies
Close the loop between what agents did and the policy that told them to.
- Verified tests: trust but verify agent-written coverage
Mark the agent-written tests a human has reviewed.
- What is AI in QA testing
AI in QA, from test generation and hybrid runtime steps to orchestration, TrueCoverage, and agent-driven maintenance.
- Who checks the tests your AI agent wrote?
A review loop for agent-written tests, from first run to verified.
- Why agent skills are a SaaS distribution channel
Why shipping an agent skill gets your product used inside coding agents.
- Why Claude beats most UI testing tools
Test automation spans system infra, test infra and the test layer, which web-based authoring tools cannot reach.
- Why fixtures matter when agents write your tests
Playwright fixtures are what keep agent-written tests reliable.
- Why traditional QA breaks in fast-moving teams
Spreadsheets, record-replay, slow TMS, and decoupled automation fail when startups ship daily, modern QA needs Git-native plans and orchestration.
Testing apps built with AI coding tools
- Testing apps built with AI coding tools
QA for apps built with Lovable, Cursor, Claude Code, Replit, Copilot, Windsurf, Codex, and other agent or vibe-coding tools.
- A QA workflow for agent-built apps
Per-PR QA loop for agent-built apps, requirements, TrueCoverage, test runs, SmartTests, init, test, explore, evolve.
- Claude Code with Playwright: three ways to set it up
How to use Claude Code with Playwright: add the Playwright MCP server, generate the planner, generator and healer agents.
- How to test apps built with Bolt
Per-PR E2E QA for apps built with Bolt.new: seed routes, probes and Playwright SmartTests that go beyond preview demos.
- How to test apps built with Claude Code
Claude Code testing with the TestChimp skill: per-PR test, explore, and evolve on apps you build in Claude Code.
- How to test apps built with Cursor
Cursor testing with the TestChimp skill and per-PR /testchimp test for apps you build in Cursor, beyond one-off agent tests.
- How to test apps built with GitHub Copilot
From Copilot one-off tests to orchestrated per-PR QA with TestChimp SmartTests, traceability, and TrueCoverage.
- How to test apps built with Lovable
Lovable testing for apps you ship from Lovable: per-PR Playwright SmartTests, requirement traceability.
- How to test apps built with OpenAI Codex
Per-PR QA for Codex-assisted codebases, SmartTests, traceability, and TrueCoverage beyond generated test snippets.
- How to test apps built with Replit
Test Replit-built apps with preview URL testing, SmartTests in Git and per-PR /testchimp test, so changes are checked before they ship.
- How to test apps built with Windsurf
Test Windsurf-built apps with per-PR /testchimp test: orchestrated E2E QA that goes beyond Cascade happy paths and keeps tests in your repo.
- How to test vibe-coded apps
Why vibe-coded and prompt-shipped apps need E2E QA with probes, per-PR /testchimp test, and TrueCoverage, not demo-only happy paths.
CI, devops and release confidence
- E2E testing in CI
CI guides for Playwright and SmartTests: GitHub Actions, parallel runs, sharding, traces and reporter wiring for reliable per-PR E2E.
- Evolve tests from real user behaviour
Use real-user sessions to decide which tests to add next.
- GitHub pull request checks: run tests and require them to merge
How to run tests as GitHub pull request checks, require them with branch protection, and fix checks stuck on 'Waiting for status to be reported'.
- Playwright Trace Viewer: record, open and read a trace
How to record a Playwright trace, open trace.zip locally or at trace.playwright.dev, and read the Actions.
- Release governance: ship when the evidence says so
Gate releases on test, coverage and security evidence instead of gut feel.
- Run Playwright in GitHub Actions with parallel shards
Playwright GitHub Actions and GitHub Actions Playwright CI: sharding, parallel workers, traces, and the Playwright report, without flaky shared data.
- Shift-left testing with Git branch-aware runs
Test each branch against its own environment before merge.
- Smoke vs regression testing (and smart smoke in CI)
How smoke and regression testing differ, and how to fit smoke runs in a CI time budget.
- Use observability data to prioritize API test coverage
Point API tests at the endpoints real traffic depends on.
TestChimp guides
Product how-tos: set up TestChimp, plan tests, run them on every PR, and read the coverage.
Getting started
- Run QA with TestChimp and Claude: all workflows
Run autonomous QA with TestChimp and Claude: markdown plans in Git, MCP APIs, Playwright SmartTests, ExploreChimp.
- How do I get humans to review tests my coding agent wrote?
Have a person confirm what an agent-written test checks with Verified Tests.
- How to ship AI-written code you don't fully understand
You can't read every line Claude Code writes.
- Hybrid Playwright plus agentic QA: the TestChimp approach
Why TestChimp favors Playwright SmartTests with optional ai.act steps, in-repo plans and TrueCoverage over pure scripts or fully agentic tests.
- Set up teams and projects in TestChimp
Learn how to set up organizations, projects, Git repo mapping, environments.
- TestChimp overview for engineering teams
TestChimp runs QA as a closed loop for AI-assisted teams: plans and tests live in git.
- TestChimp quick start: connect Git and test your first PR
Set up TestChimp in minutes: connect your repo, map plans and SmartTests folders, install the TestChimp skill, run /testchimp init.
- Update the TestChimp skill and CLI
Use /testchimp skill upgrade to pull the latest TestChimp skill playbooks/policies and align @testchimp/cli so agent workflows stay current.
- What is TestChimp and how it fits your QA workflow
TestChimp orchestrates QA for startups: markdown test plans in Git, Playwright SmartTests, TrueCoverage from real user behaviour.
Test planning and requirements
- Test plan template in Markdown (test planning as code)
A copyable Markdown test plan template, and how to keep plans, tests and coverage in sync in Git.
- Check requirement quality before tests are written
Govern requirement quality with DeFOSPAM checks, score clarity, completeness, testability, and more.
- Generate test plans and requirements in Git with an agent
Use /testchimp author plans to write user stories and scenarios under plans/ with identity-backed entities.
- Implement a story or scenario with a coding agent
Use /testchimp implement with a story or scenario id to plan and ship product code under implement.policy.md.
- Import test cases from TestRail, Jira and other tools
Bring user stories and scenarios from external tools into TestChimp markdown plans, then sync to Git for agents, traceability, and SmartTest linking.
- Link requirements to Playwright tests for traceability
Link markdown scenarios to Playwright SmartTests with scenario annotations.
- Migrate TestRail test cases to Markdown in Git
Import TestRail test cases into TestChimp as scenarios, sync them to git as Markdown and link Playwright tests.
- Plan and track manual and automated test runs
Run structured test runs from TestChimp plans, track manual and automated execution against scenarios, environments.
- Run requirement quality checks (DeFOSPAM)
Analyze story, scenario, or plans-path quality with /testchimp analyze requirement quality, explicit scope required.
- Sync test plans to your Git repo
Sync TestChimp markdown user stories and scenarios to your mapped plans/ folder in Git, enabling PR reviews, agent access.
- Write test scenarios in Markdown and link them to tests
Write test scenarios as markdown with steps and metadata, organize them in folders.
- Write user stories as Markdown with acceptance criteria
Create user stories with YAML frontmatter, priorities, labels, and acceptance criteria in TestChimp.
SmartTests and QA workflows
- SmartTests: Playwright tests with AI steps
SmartTests are Playwright scripts with optional ai.act and ai.verify steps, scenario traceability and markScreenState checkpoints for ExploreChimp.
- Bootstrap QA infrastructure in your repo (/testchimp init)
Run /testchimp init once to wire MCP, SmartTests layout, Playwright CI, seed and teardown endpoints, fixtures, mocking, TrueCoverage and environments.
- Connect agents to your test environment safely
Use /testchimp connect to test environment with a required connect-to-test-env policy, procure BASE_URL for create-tests, regression, ExploreChimp.
- Deduplicate and prune your test suite
Run /testchimp cleanup to find duplicate or semantically similar SmartTests, mark distinct pairs and remove true duplicates.
- Fix a failing test run with an agent
Use /testchimp fix test execution with an execution or batch invocation id to diagnose and fix failures, explicit identity required.
- Fix a reported issue with a coding agent
Use /testchimp fix issue with an issue id to fetch the issue and implement a fix, not blocked on connect-to-test-env.
- Generate tests for requirements with an agent
Use /testchimp create tests to author SmartTests for requirements or API operations, prioritizing uncovered high-volume and high-error operations.
- Import existing tests into SmartTests
Import an existing E2E suite into SmartTests: Playwright as-is or best-effort from Cypress and Selenium, then wire the reporter.
- Install the @testchimp/playwright reporter and runtime plugin
Install @testchimp/playwright so CI runs report executions, tag TrueCoverage events with test identity.
- Keep SmartTests and QA assets in your repo
Keep Playwright SmartTests beside application code in Git, transparent PRs, standard tooling, no proprietary runner lock-in.
- Link Playwright tests to test scenarios
Connect Playwright SmartTests to markdown scenarios using scenario annotations, unlocking coverage insights without manual traceability spreadsheets.
- Maintain your functional test suite (/testchimp upkeep)
Use /testchimp upkeep to maintain your suite: close TrueCoverage and requirement gaps, run ExploreChimp and cleanup, and refresh instrumentation.
- Mark screen states in Playwright tests
Call markScreenState after stable UI boundaries in SmartTests to power Atlas, ExploreChimp bug tagging, and UX analytics aligned to real journeys.
- Mark tests as verified after human review
Inspect a covering SmartTest, mark that it verifies a linked scenario, assign a sticky verifier and get notified when a run needs re-verification.
- Review agent-written tests before you trust them
How to review tests written by AI coding agents: a practical checklist (can it fail, scoped assertions, no skips, linked scenario) and Verified Tests.
- Run QA on every pull request (/testchimp test)
Use /testchimp test after development to scope SmartTest authoring, scenario linking.
- Run SmartTests in CI with plain Playwright
Execute SmartTests in GitHub Actions or any CI using the normal Playwright runner plus @testchimp/playwright for reporting and TrueCoverage test.
- Run tests across multiple environments
Run SmartTests and explorations against QA, staging, or custom environments and releases, scoping insights, TrueCoverage.
- Run tests against each Git branch (shift-left QA)
Run SmartTests against Git branch deployments before merge, aligning PR previews, exploratory runs, and coverage with the code under review.
- Set up SmartTests in your CI/CD pipeline
Integrate SmartTests into CI/CD with Playwright, @testchimp/playwright reporting, branch previews, and TestChimp insights.
- Sync SmartTests and plans with GitHub
Connect GitHub to sync SmartTests and markdown plans bi-directionally, PR-based reviews, branch-aware CI, and agent access to the same repo truth.
- Test iOS and Android apps with Mobilewright SmartTests
Run native mobile SmartTests on iOS and Android via Mobilewright, same plans, traceability, ExploreChimp story.
- Write SmartTests in Playwright
Author SmartTests as Playwright specs with installTestChimp fixtures, scenario annotations, optional ai.act steps and markScreenState checkpoints.
- Write version-controlled QA workflow policies
Use /testchimp create policy with a workflow-id to author *.policy.md, frontmatter, scoping, subflows, and project quirks for agents.
Exploratory and UX testing
- AI exploratory testing for UX bugs (ExploreChimp)
Run ExploreChimp explorations guided by SmartTests and recipes, journeys, screen-state analysis, explorer credits.
- Automate form validation testing
Specialized ExploreChimp recipe focused on form validation, error messages, and edge inputs along SmartTest journeys across your app.
- Discover app screen states to bootstrap tests
ExploreChimp discovers key screen-states when no SmartTests exist, building a starter suite for targeted Bug Source Analytics explorations later.
- Find where bugs come from (bug source analytics)
Primary ExploreChimp recipe when SmartTests exist, analyzes DOM, screenshots, network, console.
- Guide exploratory runs with custom instructions
Steer ExploreChimp with custom instructions, focus areas, credentials hints, areas to avoid, and product context for sharper UX bug detection.
- Run an exploratory testing session
Launch explorations from TestChimp or /testchimp explore, pick SmartTest folders, recipes, environments, journey counts, and custom instructions.
- Run exploratory tests on PR preview environments
Run ExploreChimp against branch deployments tied to open PRs, catch UX regressions on preview URLs before merge alongside branch SmartTests.
- Run exploratory UX testing from your agent (/testchimp explore)
Run /testchimp explore to launch ExploreChimp, test-guided agents that inspect DOM, screenshots, network.
- Test light and dark themes for visual consistency
ExploreChimp Theme Tester runs SmartTest journeys across themes, finding visual inconsistencies, contrast issues, and theme-specific UX bugs.
- Test localization and i18n UX automatically
ExploreChimp Localization Tester validates locales along SmartTest paths, catching truncated strings, template leaks, ambiguous copy.
- Trace UX bugs back to screens, scenarios and stories
ExploreChimp tags UX bugs at screen-states along SmartTest journeys, linking findings to Atlas, scenarios.
- Why exploratory testing finds bugs scripts miss
Automated SmartTests verify function; ExploreChimp finds UX, visual, performance.
Coverage and QA intelligence
- Measure test coverage against real user behaviour (TrueCoverage)
TrueCoverage aligns production RUM events with SmartTest runs on web, iOS, and Android, prioritize QA by demand, duration, drop-off, and depth.
- QA metrics and insights in one place (QA Intelligence)
TestChimp QA Intel connects plans, SmartTests, executions, explorations, and TrueCoverage.
- Test API coverage against your OpenAPI spec
TestChimp maps OpenAPI operations to SmartTest traffic for endpoint and schema-field coverage, gap triage, and create issue, test or ignore workflows.
- Add real-user event tracking for coverage
Use /testchimp instrument (or setup truecoverage) to wire RUM emits and plans/events, optional scope; also a subflow of run-qa and upkeep.
- Behaviour coverage views in QA Intelligence
Access TrueCoverage inside QA Intel, event funnels, drop-off and dwell signals, and test coverage gaps aligned to SmartTest execution scope.
- Check schema field and response coverage per API operation
Drill into a TestChimp API operation: schema trees, response-code coverage, covering tests, and field-level create issue, create test or ignore gap.
- Close test coverage gaps from requirements and real usage
Use /testchimp fix coverage gaps to close testing gaps from requirements and TrueCoverage, optional scope; often a subflow of upkeep.
- Explore your QA knowledge graph (InfiniTrace)
InfiniTrace is TestChimp's link explorer for stories, scenarios, tests, executions, events, and explorations.
- Find untested user journeys in the coverage dashboard
Use the TrueCoverage dashboard for overview metrics, event detail, funnels, sample sessions, and metadata drill-down to prioritize SmartTests.
- How behaviour-based test coverage works
Understand TrueCoverage event models, session metrics, funnels, metadata slicing, and base vs coverage scopes for behaviour-aligned QA prioritization.
- Instrument web, iOS and Android apps for behaviour coverage
Self-service guide to @testchimp/rum-js, iOS/Android RUM SDKs, event emits, Playwright test identity, and TESTCHIMP_PROJECT_TYPE configuration.
- Map tests and requirements by meaning (Semantic Canvas)
Semantic Canvas is TestChimp's embedding-space map in QA Brain, plot stories, scenarios, SmartTests, issues, and events by meaning.
- QA dashboard: test metrics and trends
TestChimp homepage dashboard, high-level trends for test planning coverage, SmartTest executions, explorations, and bugs across your execution scope.
- Scenario coverage insights for test plans
Insights tab on test plans, functional coverage from linked SmartTests, execution history, and exploratory findings for selected plan folders.
- See API operation coverage at a glance
Use the TestChimp APIs list to see coverage by service, search operations, view covering tests, and act on uncovered endpoints in one place.
- See screens, states and bugs on an app sitemap
Atlas maps app screens and states from SmartTest markScreenState checkpoints, visualize bugs, regressions, and UX issues in product structure.
- Set up OpenAPI contract coverage
Configure OpenAPI root paths in TestChimp, enable Playwright API payload capture, and tune URL filters and payload storage for Operations coverage.
- Test execution and plan coverage insights
Insights tab on SmartTests, execution history, linked scenario coverage, failure trends, and exploration bug summaries per folder or file.
- Triage UX and exploration bugs
Central bugs view for ExploreChimp, extension reports, and UX findings, filtered by screen-state, severity, environment.
- Use observability data to prioritize API tests
Connect runtime observability to API contract governance to prioritize high-volume.
Releases, smoke runs and performance
- Performance testing with k6 for agent-driven teams
Agent-authored k6 journeys answer concurrency and data-volume questions before production, so apps that work for one user do not fail under load.
- Pick the best smoke tests for each PR within a time budget
Smart Smoke selects a high-ROI subset of Playwright SmartTests for each PR, related + tagged + budget-packed.
- Release management: decide when you are ready to ship
TestChimp release management ties test runs, manual session evidence, CI batches, release checks and approvals to one version for auditable sign-off.
- Author, run and maintain k6 tests with agents
Scaffold k6, author journey tests after a PR, run release-scoped performance tests and keep composites honest with the /testchimp perf workflows.
- Compare performance test runs across releases
Review k6 thresholds, p95, fail rate and timeseries in Executions, then overlay a prior run or release to spot latency and fail-rate regressions.
- Configure Smart Smoke in Playwright
Enable Smart Smoke with TESTCHIMP_SMART_SMOKE_ENABLED, set budget and tags via env or use.testchimpSmartSmoke.
- Create a release and drive release QA posture
Cut a release with /testchimp create release: lock policy, create the catalog release, run nested QA, perf and security actions.
- Detect leaked secrets before release
Run Gitleaks secrets scanning from TestChimp Release Checks, scan release changes or full git history, baseline commit, redacted report.
- Gate releases programmatically on test results
Use the TestChimp MCP release-details API to gate CI and agent workflows on in-scope test results, open issues, and release scans for a version label.
- Generate k6 load test journeys from scenarios
Use /testchimp create-perf-tests to author k6 journeys and composites linked to real scenarios, after a PR or under a release performance run.
- How budget-aware smoke test selection works
Smart Smoke maps PR impact to related SmartTests, weights them by priority, stability, recency and runtime.
- Import existing performance tests into k6
Import an existing Locust, k6, JMeter, Gatling, or Artillery suite into the mapped SmartTests k6 folder, with journeys, scenario links, and tagging.
- Link CI test runs to a release
Attach CI and local Playwright automation batches to TestChimp test runs on a release, with scenario coverage and progress alongside manual testing.
- Maintain k6 journeys and composite tests
Use /testchimp upkeep-perf to prioritize slow, high-volume, or high-error APIs and keep k6 journeys, datasets, baselines, and composites aligned.
- Organize k6 performance tests in your repo
k6 performance tests live under tests/k6 as journeys, composites, profiles and datasets.
- Record manual test results on a release
Add manual test results to release test runs via Chrome extension capture or quick web records, with notes.
- Record release approvals and fire a deploy webhook
Record who approved a release, using each person's job role, and fire a configurable deploy webhook when every required role and person has approved.
- Release analytics for ship decisions
TestChimp release intelligence: overview metrics, requirement coverage, release delta analytics.
- Run DAST security scans before release
Run OWASP ZAP DAST from TestChimp Release Checks: passive or active scans via SmartTests, environment targeting and a ZAP report on the release.
- Run QA and security checks on a release
Run UX checks and security scanners (DAST, SAST, secrets, dependency) from the TestChimp release page, with findings and bugs scoped to the release.
- Run related k6 tests after PRs and releases
Use /testchimp run-perf-tests to run related k6 journeys for a branch or release git range, with optional create-perf-tests when coverage is thin.
- Run release security and QA gates from your agent
Use /testchimp run release check with a release-check config id for DAST, SAST, secrets, deps, and related scans, explicit config required.
- Run SAST code security scans before release
Run Semgrep SAST from TestChimp Release Checks: release-scoped or full-repo rule packs, severity filters, a baseline commit and a Semgrep report.
- Run smart smoke tests from your agent
Use /testchimp run smart smoke to write related-tests.json, enable Smart Smoke, select a related and budget subset, and help fix failures.
- Run UX checks on a release
Run ExploreChimp UX Checks from Release Checks for exploratory findings on SmartTest pathways in the release delta.
- Scan dependencies for CVEs before release (Trivy)
Run Trivy dependency scanning from TestChimp Release Checks: release or full tree, security profiles, ignore-unfixed, baseline diff and a CVE report.
- Set up k6 performance testing (/testchimp init-perf)
Run /testchimp init-perf once to scaffold the mapped tests/k6 tree, Playwright testIgnore, @testchimp/k6 reporter, and performance testing policies.
Agents, automations and apps
- A QA counterpart for every team member (Bonobi)
Bonobi gives every developer, QA engineer, QA lead and PM a background QA bot.
- Bring product and QA context into meetings (Meeting Bots)
TestChimp Meeting Bots join Google Meet, Zoom, Teams and Webex with product and QA context to capture knowledge, answer in-call and assign work.
- Capture team knowledge from coding-agent chats (AgentWatch)
TestChimp AgentWatch watches Cursor, Claude Code, Codex and 20+ coding agents to capture product decisions and keep stories and scenarios current.
- Event-driven QA automations with cloud agents
Automations run TestChimp workflows via cloud agents when issues, plans, test batches or releases change, with ChimpHands, GitHub Issues or webhooks.
- Run a QA cloud agent in your CI (ChimpHands)
ChimpHands is TestChimp's native QA cloud agent.
- Test in the browser with the TestChimp Chrome extension
TestChimp Chrome extension captures manual test sessions in the browser, document steps, evidence, and traceability.
- TestChimp Studio desktop IDE for software delivery
TestChimp Studio is a desktop app for software delivery: requirements, agentic QA, release governance, coverage and executions on macOS.
- Track bugs and QA issues where testing happens
TestChimp issue management: typed issues with activity, links and attachments, plus list and kanban triage.
- Browse coding-agent sessions
Browse coding-agent conversations in TestChimp Studio: filter and search sessions, inspect extraction history and stats.
- Capture manual test sessions in Chrome
Capture manual test sessions in the browser, document steps, evidence, and traceability to scenarios without leaving the app under test.
- Common QA automation recipes
Ready-to-use TestChimp automation recipes for auto-fixing issues, implementing ready stories, repairing failed CI batches, running QA on releases.
- Configure custom meeting bots and policies
Define custom TestChimp Meeting Bots with a job role and policy markdown under plans/knowledge/policies/meetbots, for QA, FDE, pre-sales.
- Connect calendars for meeting bots
Connect Google Calendar or Outlook so TestChimp Meeting Bots can list upcoming meetings and enable team @mentions with participant context.
- Create a QA automation
Step-by-step guide to create a TestChimp automation, configure trigger, workflow action, aggregation, and human gates in the Automations wizard.
- Create issues from code or CI
Create or update TestChimp issues via the MCP HTTP API or TestChimp CLI from CI, custom scanners, and external signal systems.
- Download TestChimp Studio
Download TestChimp Studio for macOS, Windows and Linux from certified GitHub Releases, or install cross-platform with npx @testchimp/studio.
- Enable and configure AgentWatch
Enable AgentWatch in TestChimp Studio, sync cadence, agents to watch, allowed story/scenario actions, baseline gate.
- How bugs and issues get created
How TestChimp issues are created, by ExploreChimp, release UX and security scans, manual Create Issue.
- How QA automations and triggers work
Learn how TestChimp automations work: triggers, AND conditions, task templates, aggregation, human approval gates, rate limits and execution tracking.
- Install and use Bonobi
Install Bonobi from the Grok template, connect it over OAuth, set the webhook and onboard it by role.
- Install TestChimp Studio
Install TestChimp Studio via certified DMG/EXE from GitHub Releases, or via npx for developers and dogfood beta.
- Issue details, activity and linked artifacts
Full-page TestChimp issue view: types, autosaved metadata, activity comments and replies, links to stories and scenarios.
- Manage issues in a list or kanban board
Triage TestChimp issues in list or kanban views, title search, Add Filter for severity, assignee, release, due date, and more.
- Meeting bots pricing and billing
Meeting Bots billing is $1 per hour of meeting join time plus ChimpHands credits for LLM invokes, transcription is per meeting, not per bot.
- Meeting transcripts, PII redaction and follow-ups
Browse Meeting Bot transcripts in TestChimp, capture tribal knowledge, redact PII, summarize, and hand meetings to ChimpHands for post-call workflows.
- QA cloud agent best practices
Use ChimpHands to author requirements with full code context, automate housekeeping workflows, and choose platform chat or local skill-backed agents.
- Record Playwright tests from Chrome
Capture manual sessions in the Chrome extension, then use Copy test generate prompt so your agent authors Playwright SmartTests in Git.
- Set up cloud agents for automations
Install the TestChimp skill and MCP CLI, wire TESTCHIMP_API_KEY from secrets, and configure Cursor, Claude Code, Codex.
- TestChimp Studio release notes
How certified in-app auto-update and npm/npx updates work for TestChimp Studio on macOS, Windows and Linux, and how to stay current.
- Use cloud agents in automations
Configure ChimpHands, GitHub Issue, or Webhook invocation so TestChimp automations hand catalog workflows to cloud agents with a shared rate limit.
- Why use a native QA cloud agent
Why ChimpHands: isolated QA agent cost and auditability, preserved dev-agent subscriptions, async QA from platform insights and cost-optimized models.
Integrations, API and admin
- Integrate with TestChimp from code (API and MCP)
Integrate with TestChimp over HTTP using project API keys, guides and interactive API reference for /api/mcp endpoints.
- API keys and API basics
Authentication, base URL and protobuf JSON conventions for the TestChimp /api/mcp programmatic APIs, with the request format every endpoint shares.
- Behaviour coverage API
Query TrueCoverage and RUM analytics programmatically through the TestChimp /api/mcp endpoints, using a project API key.
- Connect Amazon CloudWatch
Connect AWS Application Signals or API Gateway CloudWatch metrics to TestChimp with least-privilege read credentials.
- Connect Bitbucket Cloud for tests and plans
Connect Bitbucket Cloud repositories to TestChimp, sync markdown plans and SmartTests with an access token and repository webhook.
- Connect Datadog
Connect a Datadog APM service to TestChimp with API and application keys for route discovery and request-volume summaries.
- Connect GitHub for tests and plans
Connect TestChimp to GitHub, OAuth, repo mapping, PR branch sync, and CI workflows for Playwright SmartTests and markdown plans in your startup repo.
- Connect GitLab for tests and plans
Connect GitLab repositories to TestChimp, sync markdown plans and SmartTests, support MR workflows, and Playwright CI with @testchimp/playwright.
- Connect Google Cloud Monitoring
Configure OpenTelemetry span-derived route metrics in Google Managed Service for Prometheus and connect them to TestChimp API governance.
- Connect Honeycomb
Connect a Honeycomb dataset to TestChimp with a Configuration API key for route discovery, request counts, and latency percentiles.
- Connect observability tools to QA
Connect Google Cloud Monitoring, CloudWatch, Datadog, or Honeycomb to TestChimp for read-only API route discovery and persisted runtime metrics.
- Connect your code repository
Connect GitHub, GitLab, or Bitbucket Cloud, sync SmartTests and markdown plans, enable PR workflows, preview envs, and agent access in one repo spine.
- Ephemeral environment API
Provision and manage Bunnyshell ephemeral environments and branch endpoint config through the TestChimp /api/mcp programmatic API.
- Issue management API
List, create and update TestChimp issues programmatically through the /api/mcp endpoint, using a project API key.
- Manage environments and releases
Define QA, staging, and production environments plus releases, scope SmartTest executions, explorations, TrueCoverage.
- Manage projects and Git mapping
Create and configure TestChimp projects, Git repo connections, plans/tests folder mapping, environments.
- Manage team members, roles and access
Invite teammates to TestChimp, assign roles, and manage organization access, so engineering, QA, and agents share the control plane securely.
- Migrate to MCP API v2
Breaking MCP tool consolidation in TestChimp Programmatic API 2.0.0, old tool names, new tools, and parameter mapping.
- Proof Points API Guide
Fetch project QA proof points (releases, scenario coverage, scenario count) with a restricted API key for Dealpuffin and similar integrations.
- Release management API
Integrate release catalog, test runs, batch linking, gate details, and security scan reporting via TestChimp /api/mcp APIs.
- Screen state atlas API
List and upsert screen states via the TestChimp /api/mcp API to keep the Atlas behind Fetch Atlas and ExploreChimp workflows up to date.
- Test execution history API
Query SmartTest execution history and failing reports programmatically via the TestChimp /api/mcp endpoint, using a project API key.
- Test planning API
Author and query user stories, scenarios and requirement coverage programmatically via the TestChimp /api/mcp endpoint.
- Test PR preview environments with Bunnyshell
Integrate Bunnyshell with TestChimp for ephemeral preview environments, run branch SmartTests and ExploreChimp on PR deployments automatically.
- TestChimp API reference
Full reference for the TestChimp REST and MCP API.
- Web, mobile and multi-platform projects
Choose the right TestChimp project type, Web (Playwright), Mobile (Mobilewright iOS/Android), or Multi-Platform (shared scaffold for web and native).
QA services
- QA services for startup engineering teams
Professional services paths, QA coverage intelligence setup, infra bootstrap, execution pods, TrueCoverage rollout.
- Coverage intelligence setup service
Engage TestChimp to wire plans, SmartTests traceability, QA Intel dashboards, and TrueCoverage views.
- Dedicated test execution and exploration capacity
QA Execution Pod provides dedicated capacity to run SmartTests, explorations, and regression cycles, surge coverage for releases and migrations.
- QA infrastructure setup service
TestChimp helps bootstrap CI, fixtures, seeds, mocks, Playwright layout, and agent skill wiring, enterprise-grade harness for startup repos quickly.
- Real-user coverage setup service
Expert rollout of RUM SDKs, event taxonomy, Playwright test identity, and TrueCoverage dashboards, prioritize SmartTests by real user behaviour.
- Shift-left QA upgrade for pull request gates
Upgrade legacy QA to PR-scoped SmartTests, preview environments, ExploreChimp on branches, and TestChimp intelligence, catch issues before merge.
Product updates
- AgentWatch launch: capture team knowledge from agent chats
Turn decisions buried in coding-agent chats into shared, searchable team knowledge.
- API contract governance launch: cover what your spec promises
Measure which OpenAPI operations, fields and responses your tests actually exercise.
- Bonobi launch: a QA counterpart for every team member
QA bots for PMs, designers and engineers, coordinated in one place.
- ChimpHands launch: a QA cloud agent in your CI
Run TestChimp's QA agent on your own CI runners.
- InfiniTrace launch: a walkable QA knowledge graph
Follow links from requirements to tests, runs, bugs and screens.
- Meeting Bots launch: product context in every call
Bots that join calls with your product, QA and release context.
- Native mobile testing launch (iOS and Android)
TestChimp now plans and runs tests for native mobile apps.
- No-code view for Playwright tests
Edit Playwright tests in a simplified view without losing the code.
- QA on autopilot with workflow automations
Trigger cloud-agent QA workflows from repo and release events.
- Screen-state markers in Playwright tests
Tag screen states in tests to map coverage across your app.
- Semantic Canvas launch: see QA knowledge by meaning
Explore tests, scenarios and bugs clustered by meaning.
- SmartTests now support the full Playwright ecosystem
Use any Playwright feature, fixture or reporter with SmartTests.
- Special-purpose testing agents for specific bug classes
SmartTest-guided agents that each target one class of bugs, alongside ExploreChimp.
- Test runs launch: turn testing into release confidence
Plan, track and report manual and automated runs per release.
- TestChimp and Bunnyshell partnership for PR environments
Test every pull request on its own preview environment.
- TestChimp changelog
Every release, newest first.
- TestChimp Studio launch: a desktop IDE for delivery
A desktop app that brings plans, tests and agents together.
- TestChimp weekly changelog: week ending 23 October 2026
Claude Code plugin with hosted MCP, ExploreChimp on your machine, safer runner credentials, and Git sync that handles large pushes and rate limits.
Comparisons and tools
How TestChimp compares to other tools and approaches, plus our free Playwright and HAR tools.
Free Playwright and HAR tools
- Add AI steps to Playwright tests (ai-wright)
Open-source library for ai.act and ai.verify steps inside standard Playwright scripts.
- AI steps in Playwright scripts with ai-wright
Mix ai.act and ai.verify steps into ordinary Playwright tests where selectors are brittle.
- Analyze a HAR file and find what broke (HAR Playground)
Free browser tool that finds failing, slow and insecure requests in a HAR file, redacts secrets and exports Playwright mocks. No signup.
- Find duplicate and overlapping Playwright tests (semantic-graph)
Open-source CLI that maps your Playwright suite by meaning so you can spot duplicate tests and coverage gaps.
- Find duplicate tests in a Playwright suite
Detect overlapping tests with a semantic graph before your suite bloats.
Approach comparisons
- All TestChimp comparisons
Compare TestChimp to issue trackers, record-replay, pure agentic tests, manual exploration, and traditional traceability.
- Exploratory testing agents vs manual exploratory testing
Exploratory testing with agents vs manual testing at scale.
- ExploreChimp vs other AI web explorers
Unconstrained crawlers miss product context; ExploreChimp follows SmartTest GPS with markScreenState, recipes.
- Fully agentic tests vs Playwright plus AI steps: speed and cost
Agentic testing that invokes AI on every step is slow and expensive.
- Plain Playwright scripts vs SmartTests
Pure Playwright breaks on UI drift; SmartTests add ai.act self-repair, scenario traceability, ExploreChimp GPS.
- Record and replay testing tools vs test planning plus Playwright
Record-replay generates brittle flows in silos; TestChimp captures via extension but hardens Playwright in Git with plans, TrueCoverage.
- Requirements traceability matrix (RTM) template and alternative
What an RTM is, a copyable template, and how to keep traceability live in code instead of a spreadsheet.
- Test plans in Jira vs test planning as code
Why Jira-only test plans fail agentic QA, TestChimp markdown in Git, kanban UX, scenario traceability, and SmartTest links beat ticket silos.
TestChimp vs other tools
- TestChimp vs Selenium, Cypress and AI testing tools
Vendor comparison hub, TestChimp vs Selenium, Cypress, Playwright-only, Testim, Mabl.
- mabl Pricing: Credits, Quotes and How TestChimp Compares
mabl pricing is quote and credit based, from 500 credits a month.
- TestChimp vs ACCELQ
ACCELQ is enterprise codeless automation across channels.
- TestChimp vs BrowserStack
BrowserStack is a cloud execution grid. TestChimp authors and orchestrates QA, and its SmartTests run on BrowserStack or any Playwright CI target.
- TestChimp vs Bugasura
Bugasura focuses on bug tracking and lightweight QA workflows.
- TestChimp vs Claude
Claude writes great code, including Playwright files.
- TestChimp vs ContextQA
ContextQA is an AI-focused QA platform. TestChimp is Playwright-native, with planning, traceability and TrueCoverage, not a proprietary test format.
- TestChimp vs Cypress
Cypress has strong DX for JS teams. TestChimp builds on Playwright for multi-tab and multi-origin tests, with planning.
- TestChimp vs Functionize
Functionize uses ML for test creation and maintenance in the cloud.
- TestChimp vs Gitoza
TestChimp vs Gitoza: both keep test cases in git.
- TestChimp vs Katalon
Katalon is a broad platform across web, mobile, API and desktop.
- TestChimp vs Klarent
Comparing Klarent alternatives? See TestChimp vs Klarent for PR testing.
- TestChimp vs LambdaTest
LambdaTest provides cloud browsers and HyperExecute.
- TestChimp vs Leapwork
Leapwork is no-code automation with RPA-style building blocks.
- TestChimp vs Momentic AI
Momentic AI offers natural-language SaaS tests with AI execution.
- TestChimp vs Playwright
Playwright codegen records clicks. TestChimp adds planning, traceability, ExploreChimp.
- TestChimp vs PractiTest
PractiTest is a traditional TMS for manual and automated tests.
- TestChimp vs QA Wolf
QA Wolf is a managed service that ships tests for you.
- TestChimp vs Qase
Qase is a modern TMS with API integrations.
- TestChimp vs Reflect
Reflect is visual regression and no-code testing.
- TestChimp vs Sauce Labs
Sauce Labs is a cloud testing platform focused on execution.
- TestChimp vs Selenium
Compare TestChimp with Selenium WebDriver for startup QA, Playwright SmartTests, AI steps, planning, and TrueCoverage vs classic Selenium suites.
- TestChimp vs SpurTest (2026)
SpurTest is English-first SaaS automation.
- TestChimp vs Testim (2026)
Testim is SaaS record-replay with ML stabilization.
- TestChimp vs Testomat.io
TestChimp vs Testomat.io: Testomat.io is hosted test management with Playwright sync.
- TestChimp vs TestRail
TestRail is traditional test management.
- TestChimp vs testRigor
testRigor uses English-first proprietary tests executed in their cloud.
- TestChimp vs Testsigma Pricing and Features
Compare Testsigma pricing and features with TestChimp: Playwright in Git, planning and a 14-day free trial, no credit card.
- TestChimp vs Tricentis Tosca
Tosca is enterprise model-based test automation.
- TestChimp vs XRay
XRay is Jira-native test management. TestChimp keeps plans and SmartTests in Git with traceability, a better fit for engineering-led startups.
- TestChimp vs Zephyr
Zephyr provides Jira-integrated test management.
Alternatives
- All QA tool alternatives
Best alternatives to Selenium, Cypress, TestRail, Testim, mabl and other QA tools for modern startup teams, with side-by-side comparisons.
- ACCELQ alternatives
Why fast-moving teams switch from ACCELQ to TestChimp: Playwright SmartTests in your repo, per-PR QA and TrueCoverage from real user behaviour.
- Autosana alternatives
Weighing Autosana alternatives? Compare TestChimp vs Autosana for PR testing with coding agents: vendor-written flows vs your own agents.
- BrowserStack Alternatives (2026): Playwright in Git
BrowserStack alternatives for dev-led teams: keep Playwright tests in Git, run QA on every PR, and see coverage against real production usage.
- Bugasura alternatives
Why fast-moving teams switch from Bugasura to TestChimp: Playwright SmartTests in your repo, per-PR QA and TrueCoverage from real user behaviour.
- Claude alternatives
Why fast-moving teams switch from Claude to TestChimp: Playwright SmartTests in your repo, per-PR QA and TrueCoverage from real user behaviour.
- ContextQA alternatives
Why fast-moving teams switch from ContextQA to TestChimp: Playwright SmartTests in your repo, per-PR QA and TrueCoverage from real user behaviour.
- Cypress vs Playwright
Cypress and Playwright compared on architecture, browsers, languages, parallelism and multi-tab support.
- Functionize Alternatives for Modern QA Teams
Functionize alternatives for teams that want Playwright in Git, per-PR QA, and TrueCoverage instead of a standalone Functionize suite.
- Git-native Azure DevOps Test Plans alternative
TestChimp is a git-native Azure DevOps Test Plans alternative: Markdown plans and Playwright tests in your repo.
- Git-native Qase alternative
TestChimp is a git-native Qase alternative for engineering teams: Markdown plans and Playwright tests in your repo.
- Git-native TestRail alternative
A TestRail and Qase alternative for teams using AI coding agents: Markdown scenarios in your repo, agents maintain the tests, and humans approve.
- Git-native Xray alternative
TestChimp is a git-native Xray alternative: Markdown plans and Playwright tests in your repo and two-way git sync instead of Jira-issue tests.
- Human Testers vs Ongoing QA for Vibe-Coded Apps
Human testers are great for first impressions and launch walkthroughs.
- Katalon Alternatives for Modern QA Teams
Katalon alternatives for teams that want Playwright in Git, per-PR QA, and TrueCoverage instead of a standalone Katalon suite.
- LambdaTest alternatives
Why fast-moving teams switch from LambdaTest to TestChimp: Playwright SmartTests in your repo, per-PR QA and TrueCoverage from real user behaviour.
- Leapwork alternatives
Why fast-moving teams switch from Leapwork to TestChimp: Playwright SmartTests in your repo, per-PR QA and TrueCoverage from real user behaviour.
- mabl Alternatives (2026): Playwright in Your Repo
mabl alternatives for dev-led teams: keep Playwright tests and plans in Git, run QA on every PR, and see coverage against real production usage.
- Meticulous alternatives
Looking for a Meticulous.ai alternative?
- Momentic Alternatives (2026): Keep Playwright Tests in Git
Momentic alternatives for dev-led teams: keep Playwright tests and plans in Git, run QA on every PR, and see coverage against real production usage.
- Playwright alternatives compared
Cypress, Selenium, WebdriverIO, Puppeteer and TestCafe compared, and when to keep Playwright instead.
- PractiTest alternatives
Why fast-moving teams switch from PractiTest to TestChimp: Playwright SmartTests in your repo, per-PR QA and TrueCoverage from real user behaviour.
- QA Wolf Alternatives for Modern QA Teams
QA Wolf alternatives for teams that want Playwright in Git, per-PR QA, and TrueCoverage instead of a standalone QA Wolf suite.
- Qase Alternative (2026): Git-Native Test Management
Qase alternative for dev-led teams: keep test plans and Playwright tests in Git, run QA on every PR, and see coverage against real production usage.
- Reflect alternatives
Why fast-moving teams switch from Reflect to TestChimp: Playwright SmartTests in your repo, per-PR QA and TrueCoverage from real user behaviour.
- Sauce Labs Alternatives (2026): Playwright in Git
Sauce Labs alternatives for dev-led teams: keep Playwright tests and plans in Git, run QA on every PR, and see coverage against real production usage.
- Selenium Alternatives (2026): Playwright, Cypress and More
Selenium alternatives for dev-led teams: compare Playwright and Cypress, keep tests in Git, run QA on every PR, and see coverage against real usage.
- SpurTest Alternatives for Modern QA Teams
Spurtest alternatives for teams that want Playwright in Git, per-PR QA, and TrueCoverage instead of a standalone SpurTest suite.
- TesterArmy alternatives
Searching for a TesterArmy alternative? Compare TestChimp vs TesterArmy for PR testing: low-cost vision agents vs coverage.
- Testim Alternatives (2026): Playwright Tests in Your Repo
Testim alternatives for dev-led teams: keep Playwright tests and plans in Git, run QA on every PR, and see coverage against real production usage.
- TestRail Alternatives (2026): Git-Native Options
TestRail alternative for dev-led teams: keep test plans and Playwright tests in Git, run QA on every PR, and see coverage against real usage.
- testRigor Alternatives for Modern QA Teams
testRigor alternatives for teams that want Playwright in Git, per-PR QA, and TrueCoverage instead of a standalone testRigor suite.
- Testsigma Alternatives (2026): Playwright in Git
Testsigma alternatives for dev-led teams: keep Playwright tests and plans in Git, run QA on every PR, and see coverage against real production usage.
- Tiden alternatives
Looking for a Tiden alternative? TestChimp keeps product definition current from meetings and agent sessions and keeps humans in charge of release.
- Tricentis Tosca Alternatives (2026): Git-Native Options
Tricentis Tosca alternatives for dev-led teams: keep Playwright tests and plans in Git, run QA on every PR.
- Vibe-coded app audit vs ongoing QA: which do you need?
An audit is a great check before launch.
- VibeQA Alternative: Keep Your App Working
Looking for a VibeQA alternative? VibeQA scans a live page for security and quality issues; TestChimp checks signup.
- Xray Alternatives (2026): Git-Native Test Management
Xray alternatives for dev-led teams: keep test plans and Playwright tests in Git, run QA on every PR, and see coverage against real production usage.
- Zephyr Alternatives (2026): Tests and Plans in Git
Looking for a Zephyr alternative? Compare Zephyr's Jira-based test management with a Git-native approach: Markdown plans.
Choosing an AI testing tool
- QA solutions for fast-moving teams
TestChimp solution pages for AI testing, autonomous QA, Selenium replacement and QA automation platforms.
- AI test generation tool
Generate and maintain Playwright SmartTests with AI agents, deterministic by default, hybrid ai.act steps, no vendor lock-in.
- AI testing tool for startups
TestChimp is an AI-native testing tool, SmartTests, agent workflows, planning, and TrueCoverage for fast-moving teams.
- Autonomous QA platform
Agent-orchestrated autonomous QA with /testchimp init, test, explore, and evolve, Playwright SmartTests, planning, and TrueCoverage.
- Modern QA automation platform
Planning, SmartTests, exploration, test runs, and TrueCoverage in one modern QA automation platform for startups.
- Selenium replacement tool
Replace Selenium WebDriver suites with Playwright SmartTests, AI-assisted maintenance, and TestChimp QA orchestration.