Skip to content
Hawzu Docs

Releases Overview

2 min read

Releases represent planned versions, milestones, or delivery phases in a project. They help teams organize test execution around a specific target and track quality over time.

A release can contain multiple executions. Each execution can include test cases selected manually, from requirements, and from test suites.

How Releases Work

Section titled “How Releases Work”

Use releases when testing is tied to a planned milestone, such as:

  • A product version
  • A sprint
  • A hotfix
  • A customer delivery
  • A regression cycle

Each release acts as a container for execution work. Instead of putting every test case into one large run, teams can create separate executions for sanity, smoke, regression, revalidation, or final sign-off.

Releases And Executions

Section titled “Releases And Executions”

A release can have many executions.

An execution is a testing session inside the release. Each execution has its own title, description, selected test cases, progress, results, and analysis.

Execution test cases can come from:

  • Manual selection
  • Requirements
  • Test suites

If the same test case is included from more than one source, Hawzu keeps one test case in the execution and tracks the sources that added it.

Releases Page

Section titled “Releases Page”

Open a project and select Releases to view project releases.

The Releases table can show:

  • Title
  • Status
  • Labels
  • Start Date
  • End Date
  • Created On
  • Actions

Use the column control in the page header to choose which columns are visible.

Search, Filter, And Sort

Section titled “Search, Filter, And Sort”

The Releases page supports:

  • Search by title
  • Filter by status
  • Filter by labels
  • Filter by start date
  • Filter by end date
  • Filter by creation date
  • Filter by dropdown-style custom fields
  • Sort by title or created date
  • Pagination and page-size selection

Release Statuses

Section titled “Release Statuses”

Release status controls what can happen inside the release.

Current release statuses are:

  • Not Started
  • In Progress
  • Paused
  • Completed
  • Archived

Not Started allows execution with a warning. In Progress allows execution without restrictions. Paused, Completed, and Archived block execution.

Release Actions

Section titled “Release Actions”

From the Releases table, users with the right access can:

  • Open release executions by selecting a release row
  • View and edit release details from View Details
  • Update release status
  • Delete a release
  • Open release-level analysis
  • Open release defect insights

Actions depend on project access and release status.

Releases And Standalone Test Runs

Section titled “Releases And Standalone Test Runs”

Release executions are tied to a release.

Standalone testruns are independent and are useful for quick validation, investigation, or ad-hoc testing. Use releases when the work belongs to a version, milestone, or planned delivery phase.

Next Steps

Section titled “Next Steps”