Page History
...
- T: Title section
- T1: Test Plan's issue key (with the possibility of switching to another issue)
- T2: Test Plan's Overall Execution Status
- A: Folders section
- A1: "All" and "Orphans" metafolders
- A2: the Test Repository itself, composed of folders and sub-folders with Tests organized within them
- A3: CRUD actions for the current selected folder (e.g. create, rename, delte)
- A4: information about the the amount of Tests within in the current folder and the total Tests, including sub-folders
- B: Tests section
- B1: path of the folder
- B2: overall execution status for this folder (takes into account the Test Environment selected)
- B3: Test Environment to consider for the calculation computation of the overall execution status forstatus
- B4: filter for Tests Test filters
- B5: additional information about the shown Displayed Tests vs the actual total amount of Tests within the current folder
- B6: ranked list of Tests within the current folder (only direct childschildren)
- B7: calculated status for each Test, based on runs from related Test Executions, on the selected Test Environment
Clicking on T1 will jump into redirect to the standard Test Plan issue screen.
How to access it
In order to go To reach the Test Plan Board UI , you can simply use the proper project icon or the top "Tests" menu.
Besides it, uou can jump into the Board associated with some existing Test Plan, It is also accessible right from the Test Plan issue screen.
...
Step 1: Click on the icon near the Test Plan issue key
Step 2: ChooseSearch/write select the issue key of the other desired Test Plan.
Tracking progress
...
The analysis per folder takes into account the selected Test Environment; by default it shows the calculated status for "All Environments".
The values shown per for each folder only take into account the immediate child Tests (i.e. the Tests that are within that folder). Thus, this bar shows the totals for the Tests that are seen "underneath" it.
...
Analysis by Test Environment
Tests can be analyzed per by Test Environment (i.e. taking into account the results for some given Test Environment) using the proper action (B3), so you can see the current testing status for that environment.
...
The analysis by Test Environment is only applicable to the folder progress bar (B2) and the individual test statuses (B7).
| Info | ||
|---|---|---|
| ||
If you want to evaluate the overall status of your Test Plan for some Test Environment, you can do it in the "All" meta-folder. |
...
This action in fact corresponds on to "moving" them from any folder they may already be in (including the Orphans) to the destination folder. Thus, if you "add" a Test that currently is in some folder within the Board, to some destination folder, then it will be moved from the source folder to the destination folder.
Note that Tests must already be part of the Test Plan. If you with want to add Tests to the Test Plan, then you need to go to the Test Plan issue screen and use the "Add Tests" button there.
...
Step 2: Use the context action "Add to Tests"
Step 3: Choose the Tests you want using the provided filters, a previously saved filter or by JQL
...
The list of visibile Tests can be filtered, so you can easily see and obtain the relevant Tests you need. Note that the filter keeps applies remains applied even if you change to another folder.
...