Versions Compared

Key

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

...


Use caseNotes
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)

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, specialy 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


Configuring Agile Board (Active Sprint and Backlog)

In order to make sure that only the relevant issues appear (e.g. Stories, Bugs, Test Plans and not Tests) in the Backlog and in the Active Sprint, you need to configure the Board properly. 

You may configure your Agile Board right from the screens of the Backlog / Active Sprint, using the project shortcuts on the left side bar.

You need to go Board > Configure.


Image Added


Then, choose General and edit the Saved Filter.

Image Added


The query of the saved filter 

Image Added


The exact filter to use depends on the issue types you have on your project; a possible filter could be:


project = CALC AND issuetype in (Story, Epic,Bug, Task,"Test Plan", "Test Execution", "Sub Test Execution") ORDER BY Rank ASC

Usage scenarios

A typical concern with Agile boards is having them as clear and as "non-polluted" as possible, so you can focus on what's important.

...