10X: Testing Room

The Testing Room is one place to centralize quality tracking across multiple teams and projects and where the team members are given a full view of the overall sprint quality.

To navigate to Testing Room:

  1. Select Team from the left menu bar.
  2. Under the Quality section of the menu bar, select Testing Room.

Prerequisites

  1. Program must exist in the system.
  2. PI must exist in the system and be tied to a program. 
  3. Sprints must be created and tied to a PI.
  4. Teams must be created and tied to a program.
  5. Stories must be created and tied to a sprint.

How to interpret Testing Room

  • Quality Stuff: the pane is a handy place to store such quality-related items as:
  • Sprint Coverage Report: the report shows all work done in a sprint, listing all stories from the selected sprint with their acceptance criteria and test cases if applicable. Clicking a story’s title opens its slide-out panel where you can view this story’s details.
  • Defect – Trends:
    • Team defect trend for this sprint = count of active, closed, opened, high, and critical defects in this sprint. Point to a corresponding line on the graph to view the count of defects for a specific date.
    • Team defect trend for this program increment = count of active, closed, opened, high, and critical defects in this PI. Point to a corresponding line on the graph to view the count of defects for a specific date.
    • Team find-fix rate for this sprint = daily counts of found (opened) and fixed (closed) defects for this sprint.
    • Defects by priority for this program increment = count of critical, high, medium, and low defects at daily intervals within this sprint.
  • Defect – Story Status: the story-to-defect report shows all stories for this sprint and a count of the defects associated with each story. The counts include the number of open (red) and closed (blue) defects categorized by severity level. 
  • Test Case – Trends: the testing charts include the following graphs:
    • Story automation trend for PI = a count of stories that were created and assigned to a team for this sprint vs. a count of the stories that were marked as automated.
    • Acceptance criteria automation trend for PI = displays a count of acceptance criteria created for stories assigned to a team for this sprint vs. a count of acceptance criteria that were marked as automated.
    • Stories created test case trend for PI = displays a count of stories that were created and assigned to a team for this sprint vs. a count of the stories that have test cases assigned to them.
  • Test Case – Test Results: shows all test plans with the associated test suites for the PI that this sprint is assigned to. Here, you can also find out if a test was run on a test case or not and if this test case is automated.
  • Test Case – Test Plans: shows all test suites associated with a test plan assigned to the PI this sprint is assigned to.
  • Sprint Summary: gives an outline of progress made through the sprint:
    • Planned sprint velocity = a sum of all LOE points on accepted stories
    • Average team velocity = a sum of all LOE points divided by the count of team sprints
    • Story automation coverage = percent of partially automated or fully automated stories in this sprint
    • Story test coverage = percent of stories that have associated test cases
    • Acceptance criteria automation coverage = percent of automated acceptance criteria
    • Acceptance criteria test coverage = percent of acceptance criteria that have test cases associated
    • Test cases for this sprint = test cases created in this sprint
    • Active defects out of total defects = count of all open defects in this sprint
    • Sprint goal = the team’s goal for this sprint. The goal is usually set during the sprint planning meeting or when creating a sprint.
    • Weather forecast = shows how the team feels about upcoming sprints. The weather prediction is set using the interactive sprint review meeting. 
  • Sprint Health: shows the percentage of stories that were either test and development complete or accepted out of total stories in the sprint. The red line under a story means that either this story has open defects, failed test cases, open acceptance criteria, or was split. Click the graph icon  to open the Sprint Quality report. 
Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.