Versions Compared

Old Version 4

changes.mady.by.user Unknown User (tdda)

Saved on

compared with

New Version Current

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 On the Agile Boardagile board, Sub Test Executions will be displayed as sub-tasks of the requirement.

Sub Test Execution must be added to your Issue Type Scheme. 

UI Steps
UI Step

Make sure that the

Agile Board Scope

agile board scope includes Sub Test Executions

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


For more Review details check at the module step Setting scope for the Agile Board, from this module.


UI Step

Make sure that the

Agile Board Scope

agile board scope includes Test Plan

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


For more Review details check at the module step Setting scope for the Agile Board, from this module.


UI Step

Add the Test Execution Status


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


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



UI Step

Check the result


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

With this, Now 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. 

Note

Note that you are limited on the number of fields (3) you're able to include in each card on the board. 

...