Skip to content
Hawzu Docs
API reference Go to app

Release Executions

3 min read

Executions are testing sessions inside a release. They help teams validate a release through one or more planned testing cycles.

A release can contain multiple executions. Each execution has its own title, description, selected test cases, progress, results, analysis, and defect follow-up.

When To Use Release Executions

Section titled “When To Use Release Executions”

Use release executions when testing is tied to a release milestone.

Common examples include:

  • Smoke testing before wider validation.
  • Regression testing before a release.
  • Revalidation after fixes.
  • Final release readiness checks.
  • Separate execution cycles for different teams or areas.

Use Test Runs instead when the work is independent of a release.

Release Status Rules

Section titled “Release Status Rules”

Release status controls whether execution work is available.

| Release Status | Execution Behavior | |------|------| | Not Started | Executions are allowed with a warning. | | In Progress | Executions are allowed. | | Paused | Executions are blocked. | | Completed | Executions are blocked and execution edits are not available. | | Archived | Executions are blocked, edits are not available, and the release is read-only. |

Completed and archived releases prevent execution edits. Archived releases also prevent status changes.

Create An Execution

Section titled “Create An Execution”

To create an execution:

  1. Open a release.
  2. Go to the release executions area.
  3. Click Create Execution.
  4. Enter a required Title.
  5. Add an optional Description.
  6. Select test cases.
  7. Click Create.

The execution title may start with the release name so it is easier to identify in analysis and defect views.

Create ExecutionCreate Execution
Create an execution by selecting test cases from requirements, test suites, or manual selection

Select Test Cases

Section titled “Select Test Cases”

Executions can include test cases from three sources.

Manual selection
Use Add / Update Test Cases to choose individual test cases directly.

Requirements
Add requirements to include test cases linked to those requirements.

Test Suites
Add test suites to include test cases from those suites.

You can combine all three sources. If the same test case appears from more than one source, Hawzu keeps one copy and shows source indicators.

Source Indicators And Deduplication

Section titled “Source Indicators And Deduplication”

Source indicators show why a test case is included.

A test case can appear as:

  • Manual
  • Requirement-based
  • Test suite-based
  • A combination of sources

When a test case has more than one source, removing one source does not remove the test case if another source still includes it.

If a requirement or test suite is removed, Hawzu may remove test cases that were included only through that source. Test cases that were also added manually or through another source remain.

Executions Table

Section titled “Executions Table”

Inside a release, the executions table can show:

  • Title
  • Description
  • Execution Status
  • Actions

The execution status column summarizes result counts across the selected test cases. Users can sort supported columns, search by title or description, and adjust visible columns.

Actions can open:

  • Execution details
  • Execution analysis

The page also provides release-level actions for Release Analysis and Defect Insights when available.

Manage An Execution

Section titled “Manage An Execution”

Open the execution details view to review and update the execution.

Users with access can update:

  • Title
  • Description
  • Manual test case selection
  • Selected requirements
  • Selected test suites

Newly added test cases start as Not Executed. Removing a test case removes that test case from the execution and removes its results from that execution.

Run Tests In An Execution

Section titled “Run Tests In An Execution”

Open an execution and select a test case to run it.

During testing, users can:

  • Review test case details, steps, expected results, and attachments.
  • Mark the test case as Passed, Failed, Blocked, Skipped, or Not Executed.
  • Add step-level notes.
  • Attach evidence to steps.
  • Assign test cases to users.
  • Apply bulk result or assignment updates where available.

See Running Tests for the shared testing workflow.

Delete An Execution

Section titled “Delete An Execution”

Deleting an execution removes the execution and its recorded results from the release.

Deleting an execution does not delete:

  • The release
  • Repository test cases
  • Requirements
  • Test suites
  • Defects

Defects created during testing remain in Hawzu, but they are no longer tied to the deleted execution.

Analysis And Defect Insights

Section titled “Analysis And Defect Insights”

Release executions connect to several decision-support views.

Execution Analysis focuses on one execution. It helps review progress, result distribution, unexecuted work, ownership, hotspots, and defect gaps.

Release Analysis combines all executions in the release. It helps review release readiness, rollout progress, ownership, failed and blocked hotspots, and quality signals across the release.

Defect Insights connects release testing to defects. It helps identify failed test cases without linked defects, defect pressure by execution, and defects that may need follow-up before release completion.

Section titled “Related Guides”