#Releases FAQs - Management Questions
This section answers common questions about managing releases in Hawzu.
#What is a release?
A release represents a planned version, milestone, or delivery phase of your project.
Releases help you:
- Organize test executions by version or milestone
- Track testing progress over time
- Run multiple execution cycles within the same release
- Report and analyze quality at a release level
#How do I create a release?
To create a release:
- Navigate to Releases
- Click Create Release
- Enter release details (title, description, dates)
- Create the release (it starts in Draft status)
For detailed steps, see Creating Releases.
#Which release statuses allow test execution?
Release status controls whether test executions can be created.
#Executable statuses
You can create test executions when the release is in:
- In Progress – Active testing phase
- In Review – Validation and sign-off phase
- Approved – Approved but still executable
#Executable with warning
- Not Started – Executions are allowed, but a warning is shown
#Not executable
You cannot create test executions when the release is in:
- Draft
- Rejected
- Paused
- Completed
- Archived
#Can I have multiple test runs in one release?
Yes.
A single release can contain multiple test runs, which allows you to:
- Run initial testing
- Execute regression cycles
- Validate fixes
- Perform final verification
Each execution remains independently tracked within the release.
#What happens when I change a release status?
Changing a release status directly affects executability:
- Moving to Draft, Rejected, Paused, Completed, or Archived
- Blocks creation of new test executions
- Moving to Not Started
- Allows executions with a warning
- Moving to In Progress, In Review, or Approved
- Fully enables test execution
Existing executions are never deleted when a status changes.
#What does “Completed” mean for a release?
When a release is marked Completed:
- All testing is considered finished
- No new executions can be created
- Execution history remains visible
- The release becomes read-only for execution planning
Completed releases are typically archived after reporting is done.
#How do I track release progress?
You can track release progress by:
- Viewing execution completion across test runs
- Monitoring test case pass/fail distribution
- Reviewing linked defects and their status
- Using Observatory dashboards and analytics
#Can executions be modified after a release is completed?
- Existing execution data remains visible
- No new executions can be created
- Execution history is preserved for reporting and audits
#Still have questions?