Skip to content
Hawzu Docs

Executions Overview

2 min read

An execution is a testing cycle that belongs to a release. It gathers test cases, records a result for each, and feeds the release’s progress and readiness — which is what separates it from a standalone test run.

Use executions for milestone validation, smoke testing, regression, and revalidation inside a release.

Executions and test runs

Section titled “Executions and test runs”

Hawzu has two testing workflows. They share the same test cases, statuses, and analysis views; the difference is what the session belongs to and what it affects.

Release ExecutionsTest Runs
Lives inA releaseA project
Affects release progressYesNo
Affects release readinessYesNo
Blocked by release statusYesNo
Best forMilestone validation, smoke, regression, revalidationAd-hoc checks, exploratory testing, sprint validation, quick regression

Choose an execution when the testing belongs to a release, version, or delivery decision. Choose a Test Run when it should stand alone and not move release metrics.

Shared concepts

Section titled “Shared concepts”

Executions and test runs share the same testing model:

  • Select test cases manually, from requirements, or from test suites.
  • Run test cases and record results.
  • Use Passed, Failed, Blocked, Skipped, and Not Executed.
  • Add notes and attachments at the step level.
  • Assign test cases to users.
  • Review progress, analysis, and defect signals.

Manual and automated

Section titled “Manual and automated”

Independently of whether it belongs to a release, a session is either manual — worked through by testers — or automated, driven by a CI/CD pipeline that Hawzu triggers, watches, and imports results from. Automated sessions use the same statuses, analysis, and sign-off reporting as manual ones. See Automated Test Runs.

Access and release status

Section titled “Access and release status”

Available actions depend on project access. Users may be able to view executions and results, create them, update details and selected test cases, run test cases, assign work, create defects from failed work, and delete executions.

Release status also gates release executions — Paused, Completed, and Archived releases block execution work.

Where to start

Section titled “Where to start”
Section titled “Related Guides”