Skip to content
Hawzu Docs

Analysis

3 min read

Execution Analysis is a detailed view for one execution or one standalone test run. It helps teams understand whether testing is moving well, where work is blocked, and what needs follow-up.

For release executions, this view supports release sign-off. For standalone test runs, it helps teams close out project-level testing work with the same level of detail. It can be exported as a Sign-off Report.

Execution Analysis is organized as a tabbed workspace:

  • Overview — readiness verdict, risks and blockers, execution pulse, and burndown.
  • Coverage & Flow — pace and completion, ownership and flow, and coverage by source.
  • Defects — the Defect Insights view.

When To Use Execution Analysis

Section titled “When To Use Execution Analysis”

Use Execution Analysis:

  • During active testing
  • Before treating an execution or test run as complete
  • When failures or blocked tests are increasing
  • When work needs to be reassigned
  • When failed test cases need defect follow-up
  • Before reviewing release readiness

Overview Tab

Section titled “Overview Tab”

Readiness

Section titled “Readiness”

The readiness verdict summarizes whether the execution or test run looks ready for sign-off. It can consider failed test cases, open blocker or critical defects, failed test cases without linked defects, overall fail rate, and remaining unexecuted work.

If defect access is not available, Hawzu shows that defect-based readiness needs defect access before it can provide a complete sign-off signal.

Risks & Blockers

Section titled “Risks & Blockers”

The risks and blockers list turns analysis 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. Use it during standups, release reviews, and execution closeout.

Execution Pulse

Section titled “Execution Pulse”

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

Burndown

Section titled “Burndown”

A burndown chart of remaining (unexecuted) testcases across the window versus the ideal line sits beneath the pulse — a quick read on whether the session will finish on time.

Coverage & Flow Tab

Section titled “Coverage & Flow Tab”

Pace & Completion

Section titled “Pace & Completion”

Pace and completion help teams understand whether testing activity is improving, steady, or slowing. Depending on available history, it shows a burn-up of executed testcases over time, recent pace, completion and failure trends, and an estimated completion when enough history exists. When history is thin, Hawzu uses current activity signals instead of projecting a trend.

Ownership & Flow

Section titled “Ownership & Flow”

Ownership and flow shows whether remaining work has clear owners — active executors, unassigned remaining test cases, work that has not moved recently, users carrying a high share of remaining work, and ownership concentration risk. Use it to rebalance work and prevent a single user from becoming the bottleneck.

Coverage By Source

Section titled “Coverage By Source”

Coverage by source explains how the execution or test run is covered by requirements, test suites, and manual test cases. For each source, users can review selected test cases, execution coverage, fail rate, and blocked rate — so teams can see whether risk is concentrated in a requirement, suite, or manual group.

Defects Tab

Section titled “Defects Tab”

The Defects tab embeds Defect Insights for the execution or test run — linked defects, failure gaps, critical open defects, aging, and the defect trend. Opening Defects from the execution or test run overview menu takes you straight to this tab.

Export A Sign-off Report

Section titled “Export A Sign-off Report”

Select Export in the Analysis header to download a Sign-off Report — a PDF with the sign-off gates, test execution, coverage by source, top failing tests, defects, and (for release executions) the burndown and defect-trend charts.

Frozen Analytics Snapshot

Section titled “Frozen Analytics Snapshot”

When an execution or test run is completed, its defect-derived analytics freeze to an “as of” snapshot so the figures do not drift when defects change later. Release executions also freeze when their parent release is completed or archived. See Frozen analytics snapshot.

Section titled “Related Guides”