Hawzu supports two testing workflows: Executions and Test Runs.
Both workflows let teams run selected test cases, record results, assign work, add step-level notes, attach evidence, and review analysis. The difference is where the testing session lives.
| Workflow | Where It Lives | Best For | Affects Release Progress |
|---|---|---|---|
| Release Executions | Inside a release | Milestone validation, smoke, regression, revalidation | Yes |
| Test Runs | Directly in a project | Ad-hoc checks, exploratory testing, sprint validation, quick regression | No |
Choose Release Executions when testing belongs to a release, version, or delivery decision.
Choose Test Runs when testing should stand alone and should not affect release metrics.
Executions and Test Runs share the same testing model:
For detailed creation steps, use Creating Executions and Test Runs.
Available actions depend on project access.
Users may be able to:
Release status can also affect release executions. For example, Paused, Completed, and Archived releases block execution work.
Use these guides based on what you want to do: