Skip to content
Hawzu Docs
API reference Go to app

Executions and Test Runs Overview

1 min read

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.

The Difference

Section titled “The Difference”

| 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.

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.

For detailed creation steps, use Creating Executions and Test Runs.

Access And Availability

Section titled “Access And Availability”

Available actions depend on project access.

Users may be able to:

  • View executions, test runs, and results.
  • Create executions and test runs.
  • Update details and selected test cases.
  • Run test cases.
  • Assign work.
  • Create defects from failed testing work.
  • Delete executions or test runs.

Release status can also affect release executions. For example, Paused, Completed, and Archived releases block execution work.

Where To Start

Section titled “Where To Start”

Use these guides based on what you want to do:

Section titled “Related Guides”