Release Insights

3 min read

Release Analysis shows whether a release is ready to ship, across all of its executions. Use it during release review meetings, before you move a release to Completed, and to export a Release Sign-off Report.

The Verdict In The Header

The page header shows the release’s verdict and its score out of 100. It stays visible on every tab. The verdict is one of:

Ready: no gate has failed and the score is healthy.
At risk: nothing is blocking yet, but something needs attention, such as a failure with no defect logged.
Not ready: a gate is blocking the release, such as an open blocker or critical defect.
Not started: no tests have been executed yet.

The score also has a status: Healthy, Needs Attention, At Risk or Not Ready. A failed gate always wins over a good score. The verdict and score are the same ones the Release Readiness report shows.

If you can’t view defects in the project, the header says Needs defect access, because a readiness call needs the defects.

Overview Tab

Oracle Summary

Select Summarize to have Oracle, Hawzu’s AI, write a short summary of the release’s readiness and its Top risks from the current figures. If your project has release criteria documents in Canon, the summary uses them. Select Regenerate for a fresh one. Check the summary before you sign off. It’s shown only to people who can view defects.

Readiness Gates

The checks a release has to pass, each with the value reached, its target and whether it passed:

Execution coverage
Fail rate under control
No open blocker / critical defects
Every failure has a defect
Requirements verified, when the release traces requirements

The badge beside the title shows the score. Hover a gate to see the parts of the score behind it, and select a gate to go to the items behind it. See How the score is made up.

What’s Blocking

The work to do next, such as failures that need a defect or open critical defects. Select an item to go to it.

Progress

Where the release’s tests stand: a bar with passed, failed, blocked, skipped, needs rerun and not executed, plus Pass rate, Velocity and Open defects, each with how it has changed.

Burndown

Remaining unexecuted test cases across the release window, against the ideal line, so you can see whether the release will finish on time.

Executions Tab

Execution rollout: each execution in the release, with its progress and results, highest fail rate first.
Remaining work owners: who still has test cases to run.

Requirements Tab

How many of the release’s requirements are verified, and the coverage of each requirement. Select a requirement to open it.

Defects Tab

The release’s Defect Insights: linked defects, failures with no defect, open blocker and critical defects, aging and SLA, and the defect trend across the release window. The tab is shown to people who can view defects.

Map Tab

The Map tab (beta) shows the project’s Atlas map coloured by this release’s results. You can narrow it to one run. You can’t edit the map here. See See the map for one release or test run.

Export A Sign-off Report

Select Export report in the action bar on the right edge of the page to download a Release Sign-off Report. It’s a PDF with the readiness dashboard, the gates, execution health, requirements, top failing tests, defects, and the burndown and defect-trend charts.

Refresh release analysis, in the same bar, reloads the figures.

Snapshot On Completed Or Archived

When a release is moved to Completed or Archived, Release Analysis freezes its figures as a snapshot and the header shows Frozen snapshot as of with the date. Defects can still be linked or changed afterwards, but the frozen figures, and any sign-off report you export, don’t change.

Reopening the release returns it to live figures. No Frozen snapshot as of note means the figures are live.