Page History
...
The coverage analysis can also be done taking into account just the tests from a given Test Plan and its related Test Executions.
| Table of Contents |
|---|
Create Test Plan
To create a new Test Plan Issue,
...
Step 5a: If you selected the Create another checkbox, a new Create Issue dialog appears. This issue is automatically pre-populated with your previous Test Plan details, while leaving the Summary field blank.
Add Tests to a Test Plan
Aside from adding Tests to the Test Plan using the issue create screen, you can also do it in the Test issue page or directly in the tests section of the Test Plan issue page, as follows.
...
Step 6: Add tests by pressing "Add selected".
Reorder Tests
Ranking of Tests within the Test Plan can be done in two ways: directly in the Test Plan issue screen (if Hierarchical Test Oganization is disabled) or in the Test Plan Board (if Hierarchical Test Organization is enabled). This means you can rank Tests, whether you use hierarchies or not.
...
| Section | ||||
|---|---|---|---|---|
|
Associate Test Executions to the Test Plan
Since the table only shows Test Runs for tests that are in the Test Plan and for Test Executions that are associated with the Test Plan, it's necessary to associate Test Executions with the Test Plan.
...
Test Executions can also be associated with a Test Plan by editing the custom field Test Plan in the Test Execution issue view page or directly in the create issue screen in the Test Execution Details tab. Note that with this method, only the Test Execution shall be associated with the Test Plan; the Tests will not be associated.
Test Plan table
The Test Plan Test view section in the issue page provides you with a table where you can see all the Tests that were added to the Test Plan and their Test Executions (if they are associated to the Test Plan).
...
This inner table is similar to the Test Run table as it allows for inline execution ( 1 ) and for operations like assignee and remove ( 2 ). This inner columns are not configurable.
Create Test Executions from the Test Plan
There are several ways to create Test Executions directly in the Test Plan issue page.
Create planned Test Execution
The most common and straightforward option to create a Test Execution for all the Tests, or for a subset of those that are currently in some consolidated status, is by using the option available at the top of the Test Plan issue screen.
...
| Info | ||
|---|---|---|
| ||
In order to create a related Test Execution from the Test Plan, the user must be allowed to the edit the current Test Plan since the results on the Test Execution will affect the consolidated information shown at the Test Plan. The user will only be able to create Test Executions in certain projects, therefore the list of projects shown in the creation dialog will be filtered out accordingly. |
All tests...
Lets you create a Test Execution with all the tests that are associated with the Test Plan.
Note: If the revision field is not configured in the create issue screen of the Test Execution for the selected Project, the field will not appear in the dialog. If there are some mandatory fields, the standard create issue screen will be shown.
With status...
Choose the Tests based on their consolidated status in a specific Test Environment. You can choose all Tests using the top left-side option; the Test Environment can be chosen in the top right-side option. For all shown status, you can see the amount of Tests that are currently in that consolidated status. You may choose one or more statuses. In the example below, we will be including just the (1) Test that is currently failing.
Bulk action
You can select some Tests, using the bulk selection (1), and then schedule a Test Execution for them.
Clone Test Plan and respective Board
A Test Plan along with its respective hierarchical information (i.e. the Board folder structure) can be cloned.
The new Test Plan will be created in a clean state, containing the original Tests without any execution related information. If hierarchical test organization, the Board folder structure is also cloned.
