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.
Use releases when testing is tied to a planned milestone, such as:
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.
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:
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.
Open a project and select Releases to view project releases.
The Releases table can show:
Use the column control in the page header to choose which columns are visible.
The Releases page supports:
Release status controls what can happen inside the release.
Current release statuses are:
Not Started allows execution with a warning. In Progress allows execution without restrictions. Paused, Completed, and Archived block execution.
From the Releases table, users with the right access can:
Actions depend on project access and release status.
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.