Defect Insights
2 min read
Defect Insights helps teams connect testing results to defects.
For release executions, the view can summarize defect pressure across a release and its executions. For standalone test runs, it helps teams review failures, linked defects, and missing defect follow-up for the selected testing session.
When To Use Defect Insights
Section titled “When To Use Defect Insights”Use Defect Insights:
- During active testing
- Before completing a release execution or test run
- Before moving a release to Completed
- When failed test cases need defect follow-up
- When blocker or critical defects are still open
- During quality review
Readiness
Section titled “Readiness”The readiness indicator summarizes whether testing quality looks ready for sign-off.
Readiness can consider:
- Failed test cases
- Failed test cases without linked defects
- Open blocker or critical defects
- Failure rate
- Defect pressure across executions or test cases
The view also explains why the readiness state appears, so teams can see what needs attention.
Summary Cards
Section titled “Summary Cards”The top summary helps users review quality quickly.
It can show:
- Failed test cases
- Linked defects
- Action required
- Readiness state
- Release or execution status
- Number of executions where release-level data is available
Use these cards to understand whether the testing session needs defect triage, retesting, or additional execution work.
What Changed Recently
Section titled “What Changed Recently”Recent-change signals help teams see whether defect pressure is changing.
This can include:
- New defects today
- Reopened defect rate
- Reopened defect count
Use these signals to understand whether quality is stabilizing or whether issues are returning after fixes.
Defect Breakdown
Section titled “Defect Breakdown”Defect Insights can break down linked defects by:
- Severity
- Priority
- Status
Use this section to understand whether testing is carrying high-impact defects, many unresolved defects, or defects concentrated in a specific status.
Critical Open Defects
Section titled “Critical Open Defects”The critical defects section highlights blocker and critical defects that are still open.
Users can open defect details from this area. Where defects are connected to executions, users can also open the related execution.
This section is useful before release completion because open blocker or critical defects may indicate the release is not ready.
Defect Trend
Section titled “Defect Trend”The defect trend shows linked defect volume across the available testing window.
Use it to understand:
- When defects were introduced
- Whether defect activity is increasing
- The window being evaluated
- Peak defect days
If there is not enough activity, Hawzu shows that a trend is not available yet.
Execution Impact
Section titled “Execution Impact”Execution Impact shows which executions are carrying the most defect pressure.
It can show:
- Linked defects per execution
- Failed test cases in the execution
- Failed test cases missing defects
- Open critical defects tied to the execution
Use this section to decide which execution needs review first.
Failure Gaps
Section titled “Failure Gaps”Failure gaps are failed test cases that do not yet have testcase-level defect links.
Users can:
- Open the failed test case
- Open the related execution
- Create a defect when they have access
This helps teams close the gap between failed testing work and defect tracking.
Linked Defect Inventory
Section titled “Linked Defect Inventory”The linked defect inventory lists defects connected to the testing work.
Users can filter or review defects by:
- Severity
- Priority
- Status
- Execution
- New defects today
- Reopened defects
Each listed defect can show mapped test cases and related executions. Users with access can open defect details from the list.
Related Guides
Section titled “Related Guides”- Review Execution Analysis
- Learn about Release Executions
- Learn about Test Runs
- Review Defects