Waterfall Development (with Test Plans and Test-Execution Cycles)
|We’re excited to announce that TM4J, Test Management for Jira, is now part of the SmartBear family. Learn more.|
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.
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 artefacts, including test plans, to the issue in the Traceability section.
From the Reports view, you can select a report and filter by test plan (among other filter options) to track progress and quality of the linked test cycles.