Page History

The purpose of a Test Plan is to enable you to have a better visibility and management over your Tests.

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.

A Test Plan can be defined as:

• Static: by adding Tests explicitly to the Test Plan issue using the Xray issue picker.
• Dynamic: by defining a saved filter as the source of Tests for the Test Plan. This way, all Tests on the filter will be added automatically into the Test Plan by Xray. For example, you can define a Test Plan with a filter containing the Tests associated with Stories from a Sprint. Your Test Plan will collect all relevant Tests for that Sprint automatically. If a Test Plan is configured with a saved filter, it is not possible for users to add or remove Tests explicitly from the Test Plan.

If tracking a particular version, the Test Plan will present the latest status for each Test, independent of the number of testing iterations (i.e.,Test Executions) you make with them.

...

The coverage analysis can also be done taking into account just the tests from a given Test Plan and its related Test Executions. 

...

The purpose of Dynamic Test Plans is the possibility to have dynamic list of Tests based on some given criteria/filter (i.e. JQL). 

It is possible to define the Test Plan as static or saved filter. The default type when a Test Plan is created is static:  

• Static: composed of a list of Tests that can be added and removed by the users
• Saved Filter: defined with a Saved Filter. The Tests will be fetched automatically from the configured Saved Filter and users can not add or remove Tests without editing/changing the saved filter

You can configure from saved filter to static. In this case, the Tests are not be removed. The Tests will remain on the Test Plan and users will be able to add/remove Tests.

Create Test Plan

To create a new Test Plan Issue, 

...