Agile boards are an excellent way to visually keep track of the progress of your project's tasks.

Usually, you use agile boards to manage sprint-related issues, such as user stories, tasks and defects.

You can have more than one agile board per project, or even have an agile board with issues from several projects. 




Track the Coverage Status

Requirements, that can be user stories or other entities that you cover with tests, can have real-time feedback about the latest test results.

You add the Requirement Status Field at your board and track the coverage status easily. 



Use case

User Story

or

any other requirement issue type

  • track requirement status (uncovered , not run, ok , nok, unknowned)




Get to know more about the Coverage Status in the course "Understanding coverage"

Track test specification and organization


Tests, Pre-Conditions & Test Sets are regular Jira issues, that may have a specific workflow associated. 

The workflow will track the specification & approval process, for example. 

You can create an agile board to track the specification/ lifecycle progress. 



Use case
Test
  • track the test specification progress/lifecycle (e.g., a specific workflow is being monitored for reviewing purposes)
Pre-Condition
  • track the test specification progress/lifecycle (e.g., a specific workflow is being monitored for reviewing purposes)
Test Set
  • track the test specification progress/lifecycle (e.g., a specific workflow is being monitored for reviewing purposes)

Monitor planning and execution


You can use agile boards to track execution progress and the execution status.

For that, you just need to add the issue types Test Execution, Sub- Test execution ( if used) and Test Plan to your board. By including the specific custom field to your cards you can immediately visualize the status. 



Use caseNotes
Test Execution
  • track the daily execution-related tasks
  • including "Test Execution Status" custom field provides a quick overview of all the Tests that are part of the Test Execution
  • hard to scale, specially if CI is being adopted

Sub Test Execution

  • per each requirement, track the execution of the related Tests
  • including "Test Execution Status" custom field provides a quick overview of all the Tests that are part of the Sub-Test Execution
  • hard to scale with multiple executions
Test Plan
  • using scoped Test Plans (i.e., in a context of a sprint) quickly provides an overview of the progress of the execution of your Tests
  • including "Test Plan Status" custom field provides a quick overview of all the Tests that are part of the Test Plan
  • requires adding the "Sprint" field to the Test Plan


Test Runs are not issue types, so they can not be included in agile boards.