Managing executions and test runs means reviewing testing sessions, opening details, updating test case sources, tracking progress, and using analysis views to decide what needs attention.
Release executions are managed from inside a release.
The executions table can show:
Users can search by title or description, sort supported columns, adjust visible columns, open execution details, and open analysis for one execution.
Release-level actions can also open Release Analysis and Defect Insights when available.
Test Runs are managed from the project Test Runs page.
The table can show:
Users can search by title or description, filter by execution status, filter by creation date, filter by project in workspace views, filter by supported custom fields, sort supported columns, adjust visible columns, open details, and open analysis.
The details view lets users review and update one execution or test run.
Users with access can update:
Newly added test cases start as Not Executed.
Executions and Test Runs can include test cases from manual selection, requirements, and test suites.
When a requirement or test suite is removed, Hawzu may remove test cases that were included only through that source.
Test cases remain when they are still included by another source, such as manual selection or another requirement or test suite.
Removing a test case from the execution or test run removes its recorded result from that testing session.
From the details view, users can open a selected test case and record results.
Supported results include:
Users can also add step-level notes, attach evidence, assign test cases, and apply bulk updates where available.
See Running Tests for the full shared workflow.
Use Execution Analysis to review one execution or test run in detail.
Use Defect Insights to review linked defects, failed test cases missing defects, critical defects, failure gaps, and defect pressure.
For releases, Release Analysis reviews all executions inside the release.
Users need project access to edit executions and test runs.
Release status can also block release execution changes:
Standalone Test Runs are not controlled by release status.