Skip to content
Hawzu Docs
API reference Go to app

Execution 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.

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

Execution Analysis is most useful when the team needs operational detail for one testing session.

Readiness

Section titled “Readiness”

The readiness area summarizes whether the execution or test run looks ready for sign-off.

Readiness can consider:

  • Failed test cases
  • Open blocker or critical defects
  • Failed test cases without linked defects
  • Overall fail rate
  • 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.

Execution Pulse

Section titled “Execution Pulse”

Execution Pulse summarizes the current state of the testing session.

It helps users review:

  • Total selected test cases
  • Executed test cases
  • Remaining test cases
  • Execution coverage
  • Pass rate
  • Fail rate
  • Blocked rate
  • Skipped test cases

Use this section to understand the session at a glance before reviewing deeper signals.

Section titled “Pace And Trends”

Pace and trend views help teams understand whether testing activity is improving, steady, or slowing.

Depending on available history, the view may show:

  • Recent execution pace
  • Completion trend
  • Failure trend
  • Blockage trend
  • Forecast or trend guidance when enough history exists

If the testing session does not have enough history, Hawzu uses current activity signals instead of projecting a trend.

Ownership And Flow

Section titled “Ownership And Flow”

Ownership and Flow helps teams understand whether remaining work has clear owners.

It can highlight:

  • Active executors
  • Unassigned remaining test cases
  • Assigned work that has not moved recently
  • Users carrying a high share of remaining work
  • Ownership concentration risk

Use this area to rebalance work, assign unowned test cases, and prevent a single user from becoming the bottleneck.

Source Coverage

Section titled “Source Coverage”

Source Coverage explains how the execution or test run is covered by test case sources.

The view can group coverage by:

  • Requirements
  • Test suites
  • Manual test cases

For each source, users can review selected test cases, execution coverage, fail rate, and blocked rate. This helps teams see whether risk is concentrated in a requirement, suite, or manually selected group.

Hotspots

Section titled “Hotspots”

Hotspots show where testing attention is needed.

Common hotspot groups include:

  • Failed test cases
  • Blocked test cases
  • Not executed test cases

Use hotspots to decide what to investigate first, which areas need defects, and where testing still needs owners.

Action Queue

Section titled “Action Queue”

The action queue turns analysis signals into follow-up items.

It can surface items such as:

  • Remaining test cases
  • High failure rate
  • Blocked work
  • Unassigned remaining work
  • Assigned work that has not moved recently
  • Critical defects
  • Failed test cases missing defect links

Use the action queue during standups, release reviews, and execution closeout.

Defect Signals

Section titled “Defect Signals”

Execution Analysis includes lightweight defect signals when defect access is available.

These signals can include:

  • Linked defects
  • Open blocker or critical defects
  • Failed test cases missing defect links

Use Defect Insights for deeper defect review.

Section titled “Related Guides”