Version-controlled alongside your code
Readable and editable by humans
Directly consumable by AI Agents
Organised Like Code, Not Tickets
stories
auth
purchase flows
pay-with-credit
add-to-cart
scenarios
happy path
payment-success
Author Stories and Scenarios with AI
Human-Friendly Workflows on Top
While test plans live as files and power agents behind the scenes, TestChimp layers intuitive workflows for day-to-day collaboration - so teams get structure without sacrificing usability.
Frequently Asked Questions
How does TestChimp compare with Jira / Linear for test planning?
TestChimp is not a general issue tracker like Jira or Linear; It is a "Docs as Code" approach for test planning that is more agent-friendly as plans become available in your repo, organized in folders. TestChimp natively consolidates test authoring, execution, exploratory testing and ties them back to your plans, enabling deeper QA intelligence.
What makes this different from Xray or Zephyr?
Tools like Xray and Zephyr require form-based issue linking, whereas TestChimp uses annotation comments directly in test code that is agent friendly, and unifies planning with real execution data - including attributing exploratory bugs back to scenarios.
How does TestChimp connect plans to tests?
Scenarios are linked in test code using annotation comments (// @scenario), allowing executions, and regressions to map automatically back to the original plan. Since linking is done directly on code, coding agents can easily do the linking. This removes the need for manually maintained spreadsheets and disconnected systems.
How are UX bugs traced back to test scenarios?
Yes — in TestChimp, exploratory agents run based on existing functional tests (where the agent walks through the path and captures UX bugs). Since test to scenario mappings already exist, the bugs found by the exploratory agents are mapped to the scenarios they affect, enabling non-functional bug attribution back to your plans.
Can I import my existing stories and scenarios from Jira?
Yes - user stories and test scenarios in Jira can be imported to bootstrap your planning layer without recreating everything. You can also import TestRail test cases as scenarios, and Linear issues as stories.
How do test plans get synced to the code repo?
You can map an existing folder in your repo for stories and scenarios. Sync is bi-directional. Use "Sync to Git Repo" in the Test Planning Import/Export menu to raise a pull request with your plan changes. Commits to the mapped plans folder are pulled back into TestChimp through repository webhooks, and plans stay on the default branch.
