Versions Compared

Old Version 1

changes.mady.by.user Sofia Canario

Saved on

compared with

New Version 2

changes.mady.by.user Sofia Canario

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Sub Test Execution works exactly like a Test Execution, but, as it is a sub-task, it is created within the context of a requirement.

At the Agile Board, Sub Test Executions will be displayed as sub-tasks of the requirement.

Sub Test Execution must be added to your Issue Type Scheme. A Test Plan tracks a group of Tests, regardless of the number of Test Executions for a given version. Test Plans may be used to group the Tests in the scope a given sprint and thus, consolidate the test results.

UI Steps
UI Step

Make sure that the Agile Board Scope includes Test Plan

Check the Agile Board Filter and confirm the issue type "Test Plan" is included. 


For more details check the module Setting scope for the Agile Board.


UI Step

Add the Test Plan Status Field


Go to the Project side Bar > Select Backlog or Active Sprint > Board > Configure. 

Image Added


Click the Card Layout and add the Test Plan Status to the Active Sprint.

Image Added


UI Step

Check the result

UI Step

Check the result

You can have a quick view of all test executions of a requirement, directly from the Jira Agile board, as long as the executions are created as Sub-Test Execution issues.

Image Removed

With this, your team can easily track all the work that needs to be done at the requirement level. 

You may, for example, have different Sub Test Executions to test the requirement in different environments. By displaying the Sub Test Execution at your board, you can see the result for each environment. 

Test Plans as a way to consolidate test results

You may create one or more Test Plans and associate them with a given Sprint.

By including the Test Plan Status custom field, you are able to see right away the overall progress of your Test Plans. 

You may also include the Test Execution Status custom field in your cards; thus, Sub-Test Executions progress may be promptly visualized.

Requirement Status may also be included in the card configuration, allowing you to assess the coverage status of the requirements present on the board.

Image Removed


Image Added


Tip

Typically, you will have a Test Plan per sprint, like in the example. But if you want you can create several test plans into your sprint.