What is TestChimp? An overview for engineering teams
TestChimp runs the entire QA process, orchestrating a closed feedback loop that makes agents address product risks. Test plans live as Markdown and tests as Playwright code in your own git repo. Governance comes from Verified Tests, API schema coverage, TrueCoverage and semantic coverage, so humans get transparency.
Last updated: 2026-10-01
What does TestChimp do?
TestChimp is a QA platform for teams whose code is increasingly written with AI agents. It surfaces product risks and coverage gaps, agents work through them, and the results flow back in, so QA runs as a feedback loop instead of a one-off test pass. Humans stay in control of intent (what the product should do). Agents do the execution and upkeep against that intent.
It is built by Aware Labs Pvt Ltd and is available at testchimp.io.
How does the QA loop work?
- Plans live in your repo. User stories and test scenarios are Markdown files in a folder you map. They sync both ways with TestChimp, and changes arrive as pull requests or merge requests you review.
- Per pull request, run QA. A developer runs
/testchimp run QAin their agent (such as Claude Code or Cursor). It chains planning, environment, test and smoke steps under one scope. - In CI, results are reported back. The
@testchimp/playwrightplugin reports runs and traces to TestChimp. - On a cadence, upkeep.
/testchimp upkeepcloses coverage gaps found from requirements and real user behavior.
The TestChimp web app, and TestChimp Studio on the desktop, are the control plane where risks, coverage gaps, bugs found by exploration and workflow runs are visible.
How do requirements stay current?
Meet-Bots and AgentWatch keep the QA surface current, so tests are written against up-to-date requirements.
- Meet-Bots join Google Meet, Zoom, Microsoft Teams and Webex calls, transcribe them, and keep summaries and notes. Decisions can be turned into stories and scenarios.
- AgentWatch (in TestChimp Studio) watches local coding-agent sessions, such as Cursor and Claude Code, spots when business rules or UX expectations were decided in chat, and proposes updates to your stories and scenarios. You review and approve.
See Meet-Bots and AgentWatch.
What governance signals does TestChimp give?
| Signal | What it shows |
|---|---|
| Verified Tests | Whether a named person inspected a test and confirmed it covers a linked scenario. The badge goes stale if an agent later patches the test |
| API schema coverage (API contract coverage) | Which API operations and fields from your OpenAPI specs are exercised by tests, based on captured traffic |
| TrueCoverage | Which real user pathways, seen in production, have no test coverage |
| Semantic coverage | What is close in meaning across stories, scenarios, tests and events, whether it has a linked test, and which tests are near-duplicates |
Together with requirement coverage by scenario, these give people a view of QA posture and release evidence. See Verified Tests, API contract governance, TrueCoverage and Semantic Canvas.
Who owns the data?
You do. Tests are standard Playwright files and plans are Markdown with frontmatter, in your own git repo, with two-way sync. Only Verified Tests status lives solely in TestChimp. A full download covers any data that is not stored in git. That is what exit-safe means. See Exit-safe test management.
What can it import?
TestChimp imports TestRail test cases as scenarios, and Jira and Linear issues as user stories. A preview shows what will be imported, credentials are not stored, and the most recent import can be reverted. See Migrate TestRail test cases to Markdown in git.
Who is TestChimp for?
Teams where coding agents have raised delivery speed faster than QA coverage, requirements accuracy and release confidence. It is aimed at engineering leaders at growth-stage companies, including teams with no dedicated QA function and teams with a small QA function that sets the intent.
For example, a financial risk analytics company with 20 engineers and 1 QA engineer has developers run /testchimp run QA after each pull request while the QA engineer writes stories and scenarios. The team reports 98% coverage across more than 1,000 scenarios in about 10 weeks (customer-reported).
How much does TestChimp cost?
Team is $420 per month and Growth is $667 per month. These are annual-billing prices shown as the effective monthly price; monthly billing is $500 and $800. Team includes 20 users and 5 projects. Growth adds unlimited users and projects, TrueCoverage, API contract coverage and performance testing. Meet-Bots usage is bundled (20 hours on Team, 80 hours on Growth) and AgentWatch is included in both. Enterprise pricing is bespoke. There is a 14-day risk-free trial. See testchimp.io/pricing.
What platforms does it support?
Web through Playwright and native iOS and Android through Mobilewright. Plans and tests sync with GitHub or GitLab (including self-managed GitLab). Agents connect through the @testchimp/cli MCP server and the TestChimp skill.
How is TestChimp different from using an AI model alone?
An AI model can write tests. TestChimp tells agents which tests to write and why, using requirements, real user behavior and the results of CI runs, and then shows people what is covered and who verified it. See How to trust AI-written tests.
Frequently asked questions
What is TestChimp in one sentence?
TestChimp runs the entire QA process, orchestrating a closed feedback loop that makes agents address product risks, with tests and plans kept in your git repo.
Is TestChimp a test management tool?
It covers plans, linked tests, runs, coverage and release views, so many teams use it in place of a test case manager. It differs from hosted tools by keeping plans and tests as files in your git repo. See A git-native TestRail alternative.
Do I need to leave git or change my test framework?
No. Tests are standard Playwright files in your repo and plans are Markdown. Sync is two-way.
What is a Verified Test?
A test that a project member has inspected and confirmed actually covers a linked scenario, recorded with who and when.
What are Meet-Bots and AgentWatch?
Meet-Bots capture decisions from meetings, and AgentWatch captures decisions from coding-agent chats. Both propose updates to stories and scenarios, and people approve them.
Can I leave without losing my tests?
Yes. Your tests and plans are in your repo. Only Verified Tests status lives solely in TestChimp, and a full download covers data not in git.