Test Run Analysis

2 min read

Analysis is a tabbed workspace for one test run. It answers whether testing is moving well, where work is stuck, and what needs following up before the run is closed out.

Open it from the test run’s overflow menu, or from Analysis on the Test Runs table.

When to use it

During active testing.
Before treating a test run as complete.
When failures or blocked tests are increasing.
When work needs reassigning.
When failed test cases need defect follow-up.

Overview tab

Readiness summarises whether the run looks ready for sign-off, weighing failed test cases, open blocker or critical defects, failed test cases with no linked defect, overall fail rate, and remaining unexecuted work.

If you do not have defect access, Hawzu says so rather than quietly returning an incomplete verdict.

Risks & Blockers turns those signals into follow-up items — remaining test cases, high failure rate, blocked work, unassigned remaining work, work that has not moved recently, critical defects, and failed test cases missing defect links.

Execution Pulse is the run at a glance: total selected test cases, executed, remaining, execution coverage, pass rate, fail rate, blocked rate, and skipped test cases.

Burndown charts remaining unexecuted test cases against the ideal line — a quick read on whether the run will finish on time.

Coverage & Flow tab

Pace & Completion shows whether testing activity is improving, steady, or slowing: a burn-up of executed test cases over time, recent pace, completion and failure trends, and an estimated completion once there is enough history. With thin history, Hawzu uses current activity signals rather than projecting a trend it cannot support.

Ownership & Flow shows whether remaining work has clear owners — active executors, unassigned test cases, work that has not moved recently, users carrying a high share of what is left, and ownership concentration risk.

Coverage By Source breaks the run down by requirements, test suites, and manual selection, with selected test cases, execution coverage, fail rate, and blocked rate for each — so you can see whether the risk sits in one requirement, one suite, or the ad-hoc picks.

Defects tab

The Defects tab embeds Defect Insights for the run — linked defects, failure gaps, critical open defects, aging, and the defect trend. Opening Defects from the test run’s menu goes straight here.

Automated runs

Analysis works identically on an automated run, with one thing worth knowing: results the pipeline reported that matched no test case in the run are excluded from every figure here. They cannot inflate a pass rate or hide a gap.

Those rows are visible on the build itself, and summarised over time in the Automation Health report.

Export a sign-off report

Select Export in the Analysis header for a Sign-off Report PDF — sign-off gates, test execution, coverage by source, top failing tests, and defects.

Frozen analytics

Completing a test run freezes its defect-derived analytics to an “as of” snapshot, so the numbers you signed off do not drift when defects change afterwards. See Complete and Resume.