Coverage
Coverage in Qalion is requirement-based: each requirement gets a verdict from the latest results of the test cases that prove it.
What coverage means
It is not code coverage and there is no coverage percentage. For each requirement, Qalion answers one question: do the test cases linked to it pass? Coverage is measured per project and is available to Owners and Admins.
Requirements
Click New requirement to add one:
| Field | Notes |
|---|---|
| Key | Required and unique in the project, for example ACME-1240 |
| What it says | Required: the requirement itself, up to 500 characters |
| Description | Rich text with images |
| Feature | Groups requirements, for example Checkout |
| Release | For example 24.11 |
| Status | Draft, Active or Obsolete. An Obsolete requirement drops out of coverage but keeps its links. |
Deleting a requirement moves it to the Trash.
Link test cases
- In a test case, open the Proves section and click + Link.
- In a requirement, the cases that prove it are listed under Proven by, where you can Unlink them.
- Links Qalion AI suggests appear under Suggested by Qalion AI. They count once you click Confirm; Dismiss drops them.
How the verdict is computed
Qalion takes the latest finished result of each linked case, across all runs and environments, and applies these rules in order:
| Verdict | When |
|---|---|
| Not covered | No test case is linked. |
| Failing | Any linked case's latest result is Failed or Error. |
| Verified | Otherwise, at least one linked case's latest result is Passed. |
| Not run | Otherwise. It reads "Only drafts" when every linked case is a Draft. |
Skipped results count as no result. Obsolete and deleted requirements are left out.
Reading the page
- Release readiness reads Not ready if anything is failing, Not proven yet if anything is not run or not covered, and Ready otherwise. It also counts the test cases that prove no requirement. Click a segment to filter the list.
- Quality by feature shows, per feature, its verdicts ("… of … verified") and the pass rate of its cases.
- Tabs: Gaps (everything not Verified; the default) and All requirements. Filter by verdict and feature, and group By feature or as a List.
Note
The Coverage page doesn't refresh when a run finishes. Reload it to see new verdicts.
Requirements from Jira
- To import Jira tickets as requirements, connect Jira under Integrations, then ask Qalion AI to import them.
- Sync from Jira appears once imported requirements exist. It re-reads up to 50 tickets per click and never writes to Jira.
- When a ticket was reworded since the last sync, its row shows Ticket changed. Editing the requirement clears the badge.
- Imported requirements have an Open in the tracker link.
Was this page helpful?