Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
UI Steps
UI Step

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.

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

UI Step

Create planned Test Execution

There is a thigh relation close relationship between Test Plans and Test Execution therefor , therefore you are able to access information from the Test Plan to access information from 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.



Info

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

UI Step

Add Tests and Test Sets

While there is a

thigh relation

close relationship between Test Plans and Test Execution, the relation between Test and Tests Sets

its not hat 

While Test Sets address organization, Test Plans address planning. Thus, they have different purposes.

A Test Set is basically an ordered, flat list of Tests, grouped by any logical criteria (e.g., by business case, component, security, performance). You may have as many Test Sets as you want, and a Test may be included in multiple Test Sets. Test Sets are great if you want to have full control over certain groups of Tests. You can easily select them whenever you want (e.g., when creating Test Plans or Test Executions) instead of having to search individual Tests by hand. Test Sets can also be used to dynamically cover requirements.

Being them d

is not that close but you still have a easy way to add Test Sets to a Plan.

Image Added

Info

More information about Test Plans and Test Executions  adding tests in the next following sections.

UI Step

Table Filters

UI Step

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.

Image Added

Or, using JQL 


Image Added


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. 

Image Added

And applying a filter on "windows" as environment

Image Added

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

Image Added