llms.txt
Compare with other sites' llms.txt files →# TestChimp Documentation
> TestChimp runs the entire QA process for software teams: it orchestrates a closed feedback loop that makes agents address product risks and coverage gaps, while people own intent.
## Start here
- TestChimp is a QA platform for human-agent hybrid teams. Plans are markdown stories and scenarios; tests are standard Playwright SmartTests (optional ai.act/ai.verify steps); both live in your own Git repo (GitHub, GitLab, or Bitbucket Cloud) with two-way sync.
- Governance signals show what is actually covered: requirement coverage, Verified Tests (a person confirmed the test covers the scenario), API contract coverage, semantic coverage and TrueCoverage (production user events vs test runs).
- Only Verified Tests status lives solely in TestChimp; everything else is in your repo or in the full data download.
- Full text of the key pages below: https://testchimp.io/llms-full.txt
- Signup: https://prod.testchimp.io/signup
## Key pages
- [What is TestChimp? An overview for engineering teams](https://testchimp.io/docs/what-is-testchimp): Answer-first overview: the QA loop, Meet-Bots and AgentWatch, governance signals, data ownership, imports, pricing and platforms.
- [How to trust AI-written tests](https://testchimp.io/guides/trust-ai-written-tests): Why green agent-written tests prove little, mutation testing vs human review, a verification checklist, and how Verified Tests and coverage signals work.
- [Verified Tests](https://testchimp.io/docs/smart-tests/verified-tests): A project member inspects a SmartTest and confirms it covers a linked scenario. A sticky assignee is notified when a CI or local run still needs verification or re-verification.
- [Best TestRail alternative](https://testchimp.io/guides/alternatives/testrail-alternative): Why teams move from TestRail to TestChimp: plans and Playwright SmartTests in Git, per-PR QA, TrueCoverage.
- [A git-native TestRail alternative](https://testchimp.io/guides/alternatives/git-native-testrail-alternative): Answer-first Qase or TestRail alternative for engineering teams using AI coding agents: Markdown scenarios in the repo, agents write and maintain tests, humans approve.
- [A git-native Qase alternative](https://testchimp.io/guides/alternatives/git-native-qase-alternative): Qase alternative for engineering teams: Markdown plans and Playwright in git, Verified Tests, honest migration (no direct Qase importer).
- [A git-native Azure DevOps Test Plans alternative](https://testchimp.io/guides/alternatives/git-native-azure-devops-test-plans-alternative): Git-native alternative to Azure DevOps Test Plans: plans as Markdown in git vs Azure Boards work items, Verified Tests, honest migration notes.
- [A git-native Xray alternative](https://testchimp.io/guides/alternatives/git-native-xray-alternative): Git-native alternative to Xray for Jira: Markdown plans and Playwright in git vs Jira-issue tests, Verified Tests, BDD fairness notes.
- [Human review of agent-written tests](https://testchimp.io/docs/smart-tests/human-review-of-agent-written-tests): Practical checklist for reviewing AI coding agent tests, then how Verified Tests records who checked each scenario link.
- [How do I get humans to review tests my coding agent wrote?](https://testchimp.io/guides/review-tests-coding-agent-wrote): Verified Tests: a person confirms what a test checks, the badge goes stale when an agent edits it, and tests link to in-repo Markdown scenarios.
- [Test planning as code](https://testchimp.io/docs/test-planning/intro): What test planning as code is, how startups using AI coding agents replace TestRail with Markdown plans in git, and FAQ.
- [Migrate TestRail test cases to Markdown in git](https://testchimp.io/guides/migrate-from-testrail-to-git): Step by step: import TestRail cases as scenarios (optionally Jira stories first), sync the Markdown to your repo as a pull request, and link Playwright tests.
- [TestChimp vs TestRail](https://testchimp.io/guides/compare/testchimp-vs-testrail): Side-by-side comparison, when TestRail is still the better fit, and the migration path.
- [TestChimp vs Qase](https://testchimp.io/guides/compare/testchimp-vs-qase): Side-by-side comparison with Qase, when Qase is the better fit, and the migration path.
- [TestChimp vs Gitoza](https://testchimp.io/guides/compare/testchimp-vs-gitoza): Both keep test cases in your repo: Gitoza is a local desktop tracker (YAML on a gitoza branch); TestChimp adds the QA loop, agents, coverage signals and Verified Tests.
- [TestChimp vs Testomat.io](https://testchimp.io/guides/compare/testchimp-vs-testomat-io): Hosted test management hub vs repo-owned plans and tests with an agent-run QA loop; sourced feature table, when each fits, and exit stories.
- [Meticulous alternatives: TestChimp vs Meticulous](https://testchimp.io/guides/alternatives/meticulous-alternatives): Visual replay diffs vs agent-run tests with coverage you can trust; human verification of agent-written tests vs agent-approved visual diffs.
- [Autosana alternatives: TestChimp vs Autosana](https://testchimp.io/guides/alternatives/autosana-alternatives): Vendor-written flows vs your own coding agents, with scenario coverage, TrueCoverage and human verification of agent-patched tests.
- [TesterArmy alternative: TestChimp vs TesterArmy](https://testchimp.io/guides/alternatives/testerarmy-alternatives): Low-cost vision agents vs coverage, test review and release readiness for teams whose coding agents write the tests.
- [Tiden alternative for dev teams using coding agents](https://testchimp.io/guides/alternatives/tiden-alternative): Looking for a Tiden alternative? TestChimp keeps your product definition current from meetings and agent sessions, measures QA posture across several coverage signals, and keeps humans in charge of release decisions.
- [VibeQA alternative: keep your app working after every change](https://testchimp.io/guides/alternatives/vibeqa-alternative): Looking for a VibeQA alternative? VibeQA scans a live page for security and quality problems. TestChimp checks that signup, login and checkout still work after every change. The two work side by side.
- [Vibe-coded app audit vs ongoing QA: which do you need?](https://testchimp.io/guides/alternatives/app-audit-vs-ongoing-qa): An audit is a great check before launch. Ongoing QA keeps your app working after launch, while your coding agent keeps changing it. You probably need both.
- [Hiring human testers for your vibe-coded app vs keeping QA running](https://testchimp.io/guides/alternatives/human-testers-vs-ongoing-qa): Human testers are great for first impressions and launch-day walkthroughs. Between those passes, TestChimp keeps checking your app as your coding agent changes it.
- [TestChimp vs Klarent](https://testchimp.io/guides/compare/testchimp-vs-klarent): Vendor-managed enterprise suite vs your own coding agents with coverage, human verification and published pricing.
- [Requirement traceability](https://testchimp.io/docs/test-planning/requirement-traceability): Link markdown scenarios to Playwright SmartTests with scenario annotations; coverage by folder, environment and release.
- [Import from TestRail, Jira, Linear, and Azure DevOps](https://testchimp.io/docs/test-planning/import-from-external-sources): Import user stories (Jira, Linear, Azure DevOps) and test cases (TestRail, and Azure DevOps Test Cases linked with Tested By) into markdown plans; imports can be reverted; free-trial limits apply.
- [Export and sync plans to Git](https://testchimp.io/docs/test-planning/export-to-git): Tests and plans live in your GitHub, GitLab, or Bitbucket Cloud repo with two-way sync; only Verified Tests status lives solely in TestChimp.
## Getting started
- [Project types: Web, Mobile, and Multi-Platform](https://testchimp.io/docs/admin/project-types): TestChimp projects are typed as Web, Mobile, or Multi-Platform so init scaffolds, SmartTests, and platform analytics match how you ship.
- [Admin: Manage TestChimp Projects and Git Mapping](https://testchimp.io/docs/admin/projects): Project admin controls which repositories, folder mappings, and integrations feed SmartTests, markdown plans, and QA intelligence for each product in your org.
- [Admin: Environments and Releases in TestChimp](https://testchimp.io/docs/admin/releases): Releases and environments let teams tag every execution and exploration with the deployment context insights and TrueCoverage filters require.
- [Admin: Team Members, Roles, and Access Control](https://testchimp.io/docs/admin/team): Team admin governs who can connect Git, edit plans, run explorations, and view TrueCoverage - keeping startup QA collaboration secure as the org grows.
- [Changelog](https://testchimp.io/docs/changelog): What each TestChimp platform release shipped - new capabilities, improvements, and bug fixes, newest first.
- [Onboarding Teams and Projects in TestChimp](https://testchimp.io/docs/introduction/organization): Configure your TestChimp organization and projects with Git folder mapping, environments, releases, and team roles so plans, SmartTests, and insights stay aligned.
- [What Is TestChimp? QA Workflow Layer for AI Agents](https://testchimp.io/docs/introduction/quick-intro): TestChimp is a QA workflow layer that connects test plans, Playwright SmartTests, CI, and TrueCoverage so AI agents and teams ship the right tests and keep them aligned with product reality.
- [TestChimp Quick Start: Git, Skill, and First PR Test](https://testchimp.io/docs/introduction/quick-start): Get TestChimp running by connecting Git, installing the TestChimp skill on Claude or Cursor, running /testchimp init once, /testchimp test when a PR is ready, and /testchimp create release when you ship.
- [TestChimp QA Solutions for Startup Engineering Teams](https://testchimp.io/docs/qa-solutions/intro): TestChimp QA Solutions help startups stand up agent-ready QA - coverage intelligence, repo bootstrap, dedicated execution capacity, TrueCoverage, and shift-left pipeline upgrades.
- [QA Coverage Intelligence Setup Service](https://testchimp.io/docs/qa-solutions/qa-coverage-intelligence-setup): Coverage intelligence setup aligns markdown plans, scenario annotations, CI reporting, and TrueCoverage instrumentation so QA Intel surfaces real gaps - not vanity metrics.
- [QA Execution Pod: Dedicated Test and Exploration Capacity](https://testchimp.io/docs/qa-solutions/qa-execution-pod): Execution Pod augments your team with dedicated TestChimp operators running SmartTests, ExploreChimp recipes, and release regressions on your environments.
- [QA Infra Bootstrap: /testchimp init at Scale](https://testchimp.io/docs/qa-solutions/qa-infra-bootstrap): QA infra bootstrap accelerates what /testchimp init delivers - CI pipelines, seed/teardown endpoints, fixtures, mocking strategy, and SmartTests folder structure ready for agents.
- [Shift-Left QA Infra Upgrade for Pull Request Gates](https://testchimp.io/docs/qa-solutions/shift-left-qa-infra-upgrade): Shift-left upgrade moves teams from main-only testing to branch previews, PR SmartTests, exploratory runs, and Git-synced plans with agent orchestration.
- [TrueCoverage Setup Service for Production and CI Alignment](https://testchimp.io/docs/qa-solutions/truecoverage-setup): TrueCoverage setup implements consistent event emits on web/iOS/Android, wires @testchimp/playwright, and configures base vs coverage scopes for actionable gap analysis.
- [Download TestChimp Studio](https://testchimp.io/docs/studio/download): Download certified TestChimp Studio installers for macOS, Windows, and Linux, or run npx @testchimp/studio on any platform - then sign in and map a local project folder.
- [Install TestChimp Studio](https://testchimp.io/docs/studio/install): Install TestChimp Studio from certified releases, npx @testchimp/studio, or dogfood npx @testchimp/studio-beta, then sign in and map a local project folder.
- [TestChimp Studio: Desktop IDE for Software Delivery](https://testchimp.io/docs/studio/intro): TestChimp Studio is the desktop control pane for TestChimp - plan requirements, run agentic QA, govern releases, and inspect coverage without stitching together a dozen tools.
- [TestChimp Studio updates](https://testchimp.io/docs/studio/updates): Certified builds use a signed public feed; npm installs update via npx @testchimp/studio@latest.
- [Connect to Test Environment: Env Policy Gate](https://testchimp.io/docs/workflows/connect-to-test-env): Procure and connect to the test environment used by automation workflows - blocked until connect-to-test-env.policy.md (or --policy override) exists.
- [/testchimp init: Bootstrap QA Infra in Your Repo](https://testchimp.io/docs/workflows/init): /testchimp init establishes enterprise-grade QA infrastructure in your repository - CI, fixtures, seeds, mocks, TrueCoverage hooks, and folder layout agents reuse on every PR.
- [Skill Upgrade: Keep TestChimp Skill and CLI Current](https://testchimp.io/docs/workflows/skill-upgrade): Upgrade the installed TestChimp skill and required CLI so playbooks and tools match the current platform.
- [AI Test Generation Tool](https://testchimp.io/guides/solutions/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](https://testchimp.io/guides/solutions/ai-testing-tool): TestChimp is an AI-native testing tool - SmartTests, agent workflows, planning, and TrueCoverage for fast-moving teams.
- [Autonomous QA Platform](https://testchimp.io/guides/solutions/autonomous-qa-platform): Agent-orchestrated autonomous QA with /testchimp init, test, explore, and evolve - Playwright SmartTests, planning, and TrueCoverage.
- [QA Solutions for Fast-Moving Teams](https://testchimp.io/guides/solutions/intro): Commercial intent pages for AI testing, autonomous QA, Selenium replacement, and modern QA automation platforms.
- [Modern QA Automation Platform](https://testchimp.io/guides/solutions/modern-qa-automation-platform): Planning, SmartTests, exploration, test runs, and TrueCoverage in one modern QA automation platform for startups.
- [Selenium Replacement Tool](https://testchimp.io/guides/solutions/selenium-replacement-tool): Replace Selenium WebDriver suites with Playwright SmartTests, AI-assisted maintenance, and TestChimp QA orchestration.
- [How Generated Playwright Tests Get Arranged and Maintained](https://testchimp.io/guides/qa-in-the-age-of-ai/ai-test-generation-explained): How AI test generation works with Playwright SmartTests, markdown plans, agents, and TestChimp per-PR workflows.
- [E2E Testing for Startups: A Practical Framework](https://testchimp.io/guides/qa-in-the-age-of-ai/e2e-testing-startups-practical-framework): E2E testing for startups: a practical framework with Arrange/Act/Assert, seed routes, probe Assert, markdown plans, and the /testchimp loop on every PR.
- [QA in the Age of AI](https://testchimp.io/guides/qa-in-the-age-of-ai/intro): Modern QA is shifting from manual script maintenance to AI-driven test creation, orchestration, and coverage intelligence.
- [Probe Assert vs UI Assertions - When Each Wins](https://testchimp.io/guides/qa-in-the-age-of-ai/probe-assert-vs-ui-assertions): Methodology for E2E assertions - when probe endpoints beat UI checks, the expired-coupon pattern, and how to combine both without false greens.
- [QA Without a Dedicated Team - Developer-Led Quality](https://testchimp.io/guides/qa-in-the-age-of-ai/qa-without-dedicated-team): How startups automate QA without hiring - developer-led workflows, /testchimp on every PR, markdown plans, and agent maintenance instead of a QA org.
- [What is AI in QA Testing?](https://testchimp.io/guides/qa-in-the-age-of-ai/what-is-ai-in-qa-testing): AI in QA - from test generation and hybrid runtime steps to orchestration, TrueCoverage, and agent-driven maintenance.
- [Why Traditional QA Breaks in Fast Teams](https://testchimp.io/guides/qa-in-the-age-of-ai/why-traditional-qa-breaks-in-fast-teams): Spreadsheets, record-replay, slow TMS, and decoupled automation fail when startups ship daily - modern QA needs Git-native plans and orchestration.
- [TestChimp Documentation](https://testchimp.io/docs): Documentation home for TestChimp: QA workflow layer for agents, with links into Studio, SmartTests, workflows, and coverage.
## Writing tests
### Chrome extension
- [Create SmartTests with the TestChimp Chrome Extension](https://testchimp.io/docs/chrome-extension/creating-tests): Record a manual session in the extension, then paste the test generate prompt into your TestChimp-skilled agent to author Playwright SmartTests in your repo.
- [TestChimp Chrome Extension for In-Browser QA](https://testchimp.io/docs/chrome-extension/intro): The TestChimp Chrome extension connects browser work to your project - recording manual sessions with steps, notes, and bugs, then feeding that context to agent-authored SmartTests.
- [Manual Test Capture with TestChimp Chrome Extension](https://testchimp.io/docs/chrome-extension/manual-test-capture): Manual test capture logs what testers do in-product - preserving steps and artifacts for test runs, scenario updates, and SmartTest authoring follow-ups.
### Exploratory testing
- [Custom Instructions for ExploreChimp Explorations](https://testchimp.io/docs/explorations/custom-instructions): Custom instructions tune ExploreChimp recipes with product-specific context - feature flags, test accounts, sensitive areas, and UX priorities your startup cares about.
- [Git Branch Exploratory Runs on PR Previews](https://testchimp.io/docs/explorations/git-branch-exploratory-runs): Git-branch exploratory runs aim ExploreChimp at the same preview environments as branch-specific SmartTests so UX issues surface during code review - not after deploy.
- [How to Run ExploreChimp Explorations in TestChimp](https://testchimp.io/docs/explorations/how-to-run): Configure an exploration by selecting SmartTest scope, recipe, target environment/release, journey limits, and optional custom instructions - then run from the app or CLI skill.
- [ExploreChimp Explorations: AI UX Testing Guide](https://testchimp.io/docs/explorations/intro): An exploration is a set of ExploreChimp journeys following SmartTest paths with a recipe that defines analysis focus - DOM, screenshots, network, console, and metrics at each screen-state.
- [Bug Source Analytics Recipe for ExploreChimp](https://testchimp.io/docs/explorations/recipes/bug-source-analytics): Bug Source Analytics is the default recipe for teams with SmartTests - comprehensive multi-source analysis and regression checks at each screen-state checkpoint.
- [Form Validation Tester Recipe for ExploreChimp](https://testchimp.io/docs/explorations/recipes/form-validation-tester): Form Validation Tester prioritizes invalid inputs, boundary values, and error UX at forms encountered on SmartTest paths - surfacing harsh or missing validation feedback.
- [Localization Tester Recipe: Locale and i18n UX QA](https://testchimp.io/docs/explorations/recipes/localization-tester): The Localization Tester recipe exercises journeys across locales to surface dangling template strings, awkward translations, and locale-specific visual issues automated asserts miss.
- [Screen-State Discovery Recipe: Bootstrap SmartTests](https://testchimp.io/docs/explorations/recipes/screen-state-discovery): Screen-State Discovery logs in with provided credentials, maps major app states autonomously, and generates starter SmartTests ExploreChimp can guide on future runs.
- [Theme Tester Recipe: Light, Dark, and Visual Consistency](https://testchimp.io/docs/explorations/recipes/theme-tester): The Theme Tester recipe repeats guided journeys under different themes to catch layout breaks, missing assets, and inconsistent styling startups ship with design systems.
- [UX Bug Traceability from ExploreChimp to Atlas](https://testchimp.io/docs/explorations/ux-bug-trace