Page History
The purpose of a Test Plan purpose is to address effective test planning, namely by tracking relevant Tests (i.e. the ones in the Test Plan) and their results. Therefore, the Test Plan allows the user is to enable you to have a better overview visibility and management over their your Tests.
The way the Test Plan does this is by providing the user with It provides a table that shows all the Tests added to the Test Plan and their respective Test Executions , that are also associated with the Test Plan.
For a given Test Plan you can put the Tests you want to track for a given version and the Test Plan will show you the consolidated results for those Tests; in other words, it If tracking a particular version, the Test Plan will present the latest status for each Test, independently independent of the number of testing iterations (i.e.,Test Executions) you make with them.
Thus, a Test Plan can also be seen as a way to You can group a bunch of Test Executions and easily give feedback on the current/latest status of the Tests involved in those Test Executions.
From the Test Plan, it's possible to create one or more Test Executions, for all or just a subset of the Tests contained within the Test Plan (e.g. for the , only those Tests that are still failling).
You are also able to assign one , or more , Test Plans to a given release and track progress of those tests within each Test Plan.
The Requirement Requirements 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
Your Test Plan starts by specifying the planned begin and end dates, along with the Tests that will be part of it. Normally, you would also indicate the Fix Version, so that executions you create in the Test Plan context will inherit it.
In order to To create a new Test Plan Issue the user must:,
Step 1: Click the Create Issue at the top of the screen to open the Create Issue dialog box / page.
...
Step 3: Under the General tab, type a Summary for the test execution and fill any all appropriate fields — mandatory fields are marked with an asterisk. It If you're working with versions, then you should also fill out the Fix Version, whose purpose is to say indicate that you're tracking the results of the Tests for that version; the Fix Version of the Test Plan will then . This will be used afterwards also to automatically fill out the Fix Version for of the planned Test Executions (i.e., the ones linked to/created from the this Test Plan).
Step 4: Under the Test Plan Details tab, you can populate the Test Plan custom fields provided by Xray, namely the Begin/End date. In this tab, you can also add tests to the Test Plan.
...
Optional: To create a series of similar test plans Test Plans – in within the same Project – select the Create another check box checkbox at the bottom of the dialog;.
Step 5: When you are satisfied with the content of your test planTest Plan, click the Create button.
Step 5a: If you selected the Create another check box (above) checkbox, a new Create Issue dialog appears. This issue is automatically pre-populated with your previous test plan Test Plan details, while leaving the Summary field blank.
Add Tests
...
to a Test Plan – (not sure what steps are being described here. is this the Test Plan issue page or the Test issue page?)
Aside
...
Besides adding the Tests to the Test Plan in the issue create screen the user can also do it in the Test issue page.
...
Step 2: The user can choose to add Tests or Test Sets;
Step 3: Click add selected in the open dialog when all the Tests or Test Sets the user;
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.
The user You can also add existing Test Execution issues directly to a Test Plan.
...
The selected Test Executions will be added as well as , including the Tests associated with those Test Executions.
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. With Note that with this method, only the Test Execution shall be associated with the Test Plan. The ; the Tests will not be associated.
...
The Test Plan Test view section in the issue page provides the user you with a table where he you can see all the Tests that were added to the Test plan Plan and their Test Executions (if they are associated to the Test Plan).
...
- Create planned Test Execution (see next Section), so its results be reflected on the current Test Plan;
- Add Tests and Test Sets;
- Test Plan Progress Bar;
- Table Filters;
- Use a Test Environment to calculate the status for test issues for that environment.
...
Each row represents a Test with configurable columns, with the exception of the Latest Status one. Each row also contains an inner table with information about the Test Execution, by clicking . Click on the blue arrow the user will show to see the inner table for the respective a particular test.
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
The Test Plan provides the user with There are 2 ways to create Test Executions directly in the Test Plan issue page:
The Create Test Execution
...
button will open a dropdown that has 2 options
...
.
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.
- The second option
With status... will open a dialog that will allow the user to filter the tests that will be associated to the Test Execution by Test Run Status.
- Bulk action create; – I assume this is the second way but no description?
