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). 


  1. Create planned Test Execution (see next Section), so its results be reflected on the current Test Plan
  2. Add Tests and Test Sets (see next Section)
  3. Test Plan Progress Bar
  4. Table Filters
  5. Use a Test Environment to calculate the status for test issues for that environment.

You can filter tests by status in the Test Plan Progress Bar as shown in the image below:

Create planned Test Execution

There is a close relationship between Test Plans and Test Execution, therefore you are able to access information from the Test Plan to the Test Execution of the associated tests.



Each row represents a Test with configurable columns, with the exception of the Latest Status. Each row also contains an inner table with information about the Test Execution. Click on the blue arrow to see the inner table for a particular test.



More information about Test Plans and Test Executions go to the next sections.

Add Tests and Test Sets

While there is a close relationship between Test Plans and Test Execution, the relation between Test and Tests Sets is not that close but you still have a easy way to add Test Sets to a Plan.

More information about adding tests in the following sections.

Table Filters

The plan table provides a filtering function that can used to refine what is displayed, namely, filter the Tests and results regarding a specific Version, Assignee or Status.

You can do it by using a "simple search" feature.

Or, using JQL 



Using Test Environment to calculate the status for test issues for that environment

A general use of the filtering function is to provide a view of the test plan and respective tests under a given environment.

See the example below. 

And applying a filter on "windows" as environment

The list is reduced to the Tests that have executions under that environment.







  • No labels