Annual Documentation Survey

Do you have 4 minutes to help us improve our documentation? Please take our annual survey!

Skip to end of metadata
Go to start of metadata

Table of Contents

Common Usage

Test Management for Jira supports flexible workflows to foster collaboration between teams using traditional or agile development methodologies. Due to its flexible nature, there are many ways to manage your testing efforts with Test Management for Jira, so the following sections cover best practices. However, best practices are simply guidelines, and your testing processes and needs should dictate which of the suggested practices you adopt.

A brief summary of the common usage scenarios:

  • Agile development: Ad-hoc/lightweight approach for small teams using acceptance tests and BDD

  • Waterfall development (with test execution cycles): Structured testing that takes place when it’s required to plan the test-execution cycles and assignments in advance (for structured regression testing)

  • Waterfall development (with test plans and test-execution cycles): Structured testing with formal test planning. Instead of using Microsoft Word or Excel to specify traditional test-plan documents, you can create and customize test plans with Test Management for Jira to address any planning topics, such as scope, strategy, resources, environments, risks, and more.

Agile development

With Test Management for Jira, small and agile teams can manage testing in a lightweight and straightforward fashion. You can create and link test cases or acceptance tests to user stories/bugs and then fire up single test execution directly from the issue screen in Jira or the kanban board.

For small and agile teams, there is no need to create and plan test cycles and test plans in advance. Using Test Management for Jira, you can manage your testing efforts without hassle and focus only on managing the test coverage and the test execution, as displayed in the following relationship diagram:

In Test Management for Jira

In the Traceability section of the user story/bug, you can link existing test cases or create new ones as acceptance tests.

When the user story/bug is finished or ready to be tested, you can start a single test execution for each linked test case by clicking the "play" button.

On the test player screen, you can execute the test case and input the test-execution results.

From the issue screen, you can track the latest (and previous) test-execution results for each test case.

You can also perform these tasks from the agile/kanban screen by selecting a card and navigating to the Traceability section in the details panel.

Test Management for Jira allows you to easily generate reports to track your progress and success rates. Just filter by version/fix version or by iteration (sprint).

Waterfall Development (with Test-Execution Cycles)

Test Management for Jira supports traditional/waterfall development and testing processes. Traditional approaches demand that you plan test assignment and execution in advance, sometimes even before any code has been released. Using Test Management for Jira, you have the ability plan who will execute what test and when. Plus, you can track and compare the estimated progress against the actual results in real time, during test execution.

To plan testing efforts in waterfall, you need to create and manage test cycles, which are containers/groups of ordered test cases assigned to testers and environments. When a test case is executed, a test-execution result is generated and linked to the test cycle. The test case stores useful information, like the tester responsible for the execution, the execution date, the defects raised, the environment used, and the status of the execution (e.g., passed, failed, etc). With that in mind, when you generate reports and statistics filtered by test cycle, the information displays test-execution results, metrics, and coverage of the test cases associated with the test cycle, since the cycle is the container/group.

In Test Management for Jira

Within a project, manage your test library from the Tests view. Test cases in the test library can be shared across Jira projects.

Create a new test cycle and manage the test-execution cycle from the Cycles view.

On the Test Cycle screen, add a name and other field information to the Details tab.

On the Test Cases tab, click Add Test Cases to add existing test cases from any Jira project to the cycle. You can assign the tester responsible for executing the test case as well as a target environment.

The testing team can fire up the Test Player to execute the planned test cases in the Test Cycle, set test results, and raise defects.

From the issue view, you can link test cycles to the issue in the Traceability section.

From the Reports view, you can select a report and filter by test cycle to track progress and quality.

Waterfall development (with Test Plans and Test-Execution Cycles)

Test Management for Jira supports traditional/waterfall development and testing processes. Traditional approaches demand that you plan test assignment and execution in advance, sometimes even before any code has been released. Some software companies, however, require greater emphasis and detail about the planning phase. To meet this requirement, you can use Test Management for Jira’s test plans. Instead of using Microsoft Word or Excel to create a master test plan, you can create and customize a test plan within Jira to address a broad range of planning topics, such as scope, strategy, resources, environments, risks, and others.

Test plans provide a comprehensive view of your testing effort. You can even track the test-execution cycles from a higher level by linking test cycles to a test plan. In this scenario, test plans behave as a group of test cycles, so when you generate reports and statistics filtered by test plans, the information aggregates and displays the test-execution results, metrics, and coverage of the test cases associated with the linked test cycles, since the cycle is the container/group of test cases.

In Test Management for Jira

Use the Tests view to manage your project’s test library. Test cases in the test library can be shared across Jira projects.

Use the Plans view to create a new test plan and manage high-level test planning.

On the Test Plan screen, add a name and other field information to the Details tab. You can create custom fields to address scope, test strategy, risks, etc, to meet test-planning requirements.

On the Traceability tab, you can link test cycles to the test plan. Test plans behave as a group of test cycles, so when you generate reports and statistics filtered by test plans, the information aggregates and displays the test-execution results, metrics, and coverage of the test cases associated with the linked test cycles.

Use the Cycles view to create a new test cycle and manage the test-execution cycle.

On the Test Cycle screen, add a name and other field information to the Details tab.

On the Test Cases tab, click Add Test Cases to add existing test cases from any Jira project to the cycle. You can also assign the tester responsible for executing the test case as well as a target environment.

The testing team can fire up the Test Player to execute the test cases planned in the Test Cycle, set results, and raise defects.

From the issue view, you can link test plans to the issue in the Traceability section.

From the Reports view, you can select a report and filter by test plan to track progress and quality of the linked test cycles.

Next Steps

Have a question for us?


  • No labels