Defect Coverage Gaps
3 min read
A bug that was found once and never got a test can be found again. Defect coverage gaps lists the defects in a project that have no test case linked, and lets you write the missing test case and link it in one step.
Opening the list
Section titled “Opening the list”-
Open the Repository for your project.
-
Open the actions menu in the top-right of the repository toolbar.
-
Under Repository, select Defect coverage gaps.
The action is visible to users who can both view defects and create test cases — it exists to be acted on, so it is hidden from anyone who could only look.
Reading the list
Section titled “Reading the list”The heading counts the gap against the whole project: “12 of 148 open defects have no linked test case.”
Each row shows the Defect code (which opens the defect), its Title, Status, Priority, Severity, Assignee, and when it was Raised.
Three filters narrow the list:
- Search code or title — free text over both.
- Status and Severity — the options offered are drawn from the defects actually in the list, so you are never filtering to an empty result.
- Include closed & resolved — off by default. Open defects are the ones worth writing a test for first; closed ones are a backlog exercise.
When there is nothing to do, the list says so: “Every open defect in this project is already linked to at least one test case.”
Closing a gap
Section titled “Closing a gap”Select Create test case on any row. Hawzu closes the gaps list and opens the create-test-case form, pre-filled from the defect:
- The title comes from the defect’s title.
- The description comes from the defect’s description as plain text.
Edit whatever you like — the prefill is a starting point, not a template. Real regression tests usually need steps and an expected result the defect never spelled out.
On save, the new test case is linked back to the defect automatically, and Hawzu confirms it with a Linked to defect message naming the test case and the defect code.
If the link itself fails, the test case is still created and Hawzu tells you plainly rather than silently — a Test case created, but not linked warning that points you at the defect’s Traceability section to add the link by hand.
Either way you land back on the gaps list, refreshed — so the row you just handled disappears and you can work down the list.
When to use it
Section titled “When to use it”- After a release. Sweep the defects that release produced and turn the ones worth guarding into regression tests.
- Before a sign-off. A high gap count on critical-severity defects is a straightforward argument that the suite is not ready.
- As a backlog. Tick Include closed & resolved and work through historic bugs that never became tests.