Test Coverage Report

Test Cases

Overview

The test coverage report shows how much of your work has been validated by test cases. It answers two questions: which stories have tests written for them, and which of those tests have actually been executed? Low coverage before a release is one of the clearest signals of release risk.

Coverage is driven by links between test cases and stories. A test case that isn't linked to any story contributes to execution history but not to story coverage — so linking is important to get accurate numbers.

Coverage metrics

MetricWhat it means
Story coverage %Percentage of stories that have at least one linked test case
Execution coverage %Percentage of linked test cases that have been executed at least once
Pass rate %Percentage of executed test cases that passed in the most recent run
Untested storiesStories with no linked test cases — the highest-risk items for a release
Failing casesTest cases with a Failed status in the current run

Linking test cases to stories

Coverage is only meaningful when test cases are linked to the stories they verify. There are two ways to create the link:

From the test case

1Open the test case
2Find the Linked Stories field
3Search for the story by ID or title and select it
4Save — the link appears in both the test case and the story's detail view

From the story

1Open the story detail view
2Click the Test Cases tab
3Click Link Test Case and search for the relevant test case

Reading the coverage report

Navigate to KPIs & Reports → Test Coverage to open the report. The report shows:

  • A summary bar at the top showing overall story coverage %, execution coverage %, and pass rate
  • A per-story breakdown listing every story in the project with its linked test case count and execution status
  • An Untested Stories filter to quickly find stories with no linked test cases
  • A sprint or release filter to scope coverage to a specific delivery window

Using coverage for release readiness

Before marking a release as ready, use the coverage report filtered to the release's stories to assess risk:

  • Any story with 0 test cases is high-risk — either write a test or explicitly accept the risk
  • Any test case with a Failed result blocks readiness unless it has an accepted known-issue note
  • Target at least 80% execution coverage before a production release — running 100% of tests on every release is ideal but not always practical
Coverage percentage alone doesn't guarantee quality — a test case with a weak expected result can pass and still miss a bug. Use coverage as a risk indicator, not a quality guarantee.

Troubleshooting

The coverage percentage is 0% even though I have test cases

Coverage is calculated from test cases linked to stories, not from the total test case count. Open a test case, find the Linked Stories field, and add the relevant story. Once linked, it appears in the coverage report.

A story shows as untested but I ran tests for it

The test cases you ran may not be linked to that story. Open the test cases you ran and verify each one has the story in its Linked Stories field.

The pass rate looks wrong

Pass rate reflects the most recent execution result per test case. If a test case was run multiple times, only the latest result counts. Check the test case's execution history to see all past results.

I don't see a Coverage tab

The Coverage report is in KPIs & Reports → Test Coverage. If it's not visible, check that your project has the test cases feature enabled in Project Settings.

On this page