For QA engineers and development teams who already plan their work in Jira: write test cases once, run them for every release, record pass and fail results, and see which issues are covered and which are not — without leaving Jira.
I need thisEarly access · No payment is taken on this page yet
A team of twelve ships a mobile app every two weeks. Their 300 test cases used to live in a spreadsheet next to Jira. Now each release has a test run in Jira: two testers mark results during the regression day, three failed steps become Jira bugs with the steps attached, and the product owner sees on the release page that two new stories still have no tests.
Choose your planMany software teams plan and track their work in Jira, but keep their tests somewhere else: a spreadsheet, a shared document or a separate tool. Before each release someone copies the test list, testers mark results by hand, and the link between a failed test and the Jira issue it belongs to is lost along the way.
Test management apps for Jira solve this, and teams that use them rarely go back to spreadsheets. For a small team, though, the price of the established apps grows quickly with the number of Jira users, because the whole site is billed, not only the people who test.
The service is a test management app for Jira Cloud built for small and mid-sized teams. It keeps test cases, test runs and results inside Jira, next to the stories, tasks and bugs they cover.
A test case has a title, preconditions, steps and the expected result for each step. Cases are organised in folders, can be reused across releases and are linked to the Jira issues they check. Existing cases can be imported from a spreadsheet file.
For each release or sprint you create a test run: pick the cases, assign them to testers and set a target date. Testers go through the steps and mark each case as passed, failed or blocked, adding a comment or a screenshot where needed.
When a step fails, a Jira bug can be created from it in one click. The bug already contains the steps, the expected and the actual result, and it stays linked to the test case, so the next run shows whether the fix worked.
Every Jira issue shows its tests and their latest results. A coverage view shows which stories in a release are tested, which failed and which have no tests at all, so gaps are visible before the release, not after it.
Reports show the progress of a run, results by tester and the history of each case across releases. They can be shared with the team or exported for a release review.
The app works in Jira Cloud and uses Jira's own users and permissions. Nothing needs to be installed on your servers, and your test data stays connected to your Jira site.
Pricing follows the size of the Jira site in a few simple steps, so a team of ten or twenty people pays for a small team, and the price is known before the first test run.
The service is in preparation: we are checking whether teams on Jira Cloud need it before it is built.
The app records the tests and results your team enters. It does not run automated tests by itself, and the decision to release stays with your team.
QA engineers and development teams that plan their work in Jira Cloud and want their tests next to their issues.
Yes, from a spreadsheet file with titles, steps and expected results.
Yes, in one click, with the steps and results filled in and linked to the test case.
No. It manages test cases, runs and results that your team records.
Not yet. The service is in preparation, and we are checking whether teams on Jira Cloud need it.