Ship on evidence, not on a hunch.
A release in TestChimp holds everything that decides whether it ships: what changed since the last one, every manual and automated result with its evidence, and the UX, performance and security checks, all scoped to that release.
14 days, no credit card. Works with any coding agent.
Problem
Green CI.Still not sure it’s ready.
Release readiness usually lives in a spreadsheet, a Slack thread and three dashboards. Test case managers record pass or fail with no evidence behind it, CI goes green without saying what changed, and nobody can say whether the new refund flow was actually tested.
One place for everything a release needs.
Create a release in TestChimp and it becomes the record for that version: what is in it, how it was tested, and what is still open.
Release delta
Know what changed.
Give the release the commit it is cut at. TestChimp compares it with the prior release, so you start from what is new.
Compared with the prior release
Test runs
Assurance with evidence.
Scope runs to story and scenario folders and track manual and automated results together, each with its evidence.
Manual and automated
Release checks
One view before you ship.
Verification, UX, performance and security checks gather on the same release, beside the functional results.
Functional · UX · perf · security
Start from what changed.
Most release reviews start from a blank checklist. A TestChimp release starts from the difference between this version and the last one.
The release delta
TestChimp compares the commit the release is cut at with the prior release: new and updated stories, scenarios, tests and screens. You see what needs testing before anyone starts, and what was added to the suite along the way.
Assurance with evidence.
A pass mark in a spreadsheet tells you someone clicked a box. TestChimp keeps what actually happened.
Test runs across manual and automated
Scope a test run to story or scenario folders, as you would in TestRail or Qase. Automated results arrive from CI through the TestChimp reporter, with a screenshot for every pass and a full trace for every failure. Manual results arrive as captured sessions.
UAT without the spreadsheet
Assign scenarios to the people who should check them. Each tester sees what is theirs, captures the session in the Chrome extension or TestChimp Studio, with steps, screenshots, video, voice-over and notes, and the result lands in the run.
- Scenarios assigned per tester.
- Sessions linked to the run, no evidence uploads.
- Progress across the whole run, manual and automated.
Functional and non-functional, in one view.
The release also gathers the checks that usually live in other tools, scoped to what this release introduced.
Everything between you and shipping
Verification status of the release’s tests, UX issues ExploreChimp found on the screens it changed, performance runs compared with the last release, and security findings, on the same page as the functional results. Sign-off becomes a decision on facts.
- Verified and stale tests counted per release.
- Only newly introduced issues, against the prior release.
- A downloadable report for sharing.
How release readiness is usually judged.
| Spreadsheets and Slack | Test case managers | CI dashboards | TestChimp | |
|---|---|---|---|---|
| What changed since the last release | No | No | Partly | Yes |
| Manual results with evidence | No | Pass or fail only | No | Yes |
| Automated results with screenshots and traces | No | Partly | Yes | Yes |
| Scenarios assigned for UAT | Partly | Yes | No | Yes |
| Verified and stale tests | No | No | No | Yes |
| UX, performance and security in the same view | No | No | Partly | Yes |
| Plans versioned in git | No | No | No | Yes |
Test case managers: TestRail, Qase, PractiTest and similar tools.
Questions about releases.
What is a release in TestChimp?
How is this different from TestRail or Qase?
How do Playwright CI results reach a release?
Can testers outside engineering take part?
Can I share a release report?
Sign off on evidence, not hope.
Create a release, cut it at a commit, and see everything that decides whether it ships.
14 days, no credit card.