Manage Test Runs
2 min read
Test runs are managed from the project Test Runs page, and from the workspace-level view when you need to look across projects.
The Test Runs table
Section titled “The Test Runs table”The table can show:
- Title
- Description
- Project, in workspace views
- Labels
- Execution Status
- Created On
- Actions
You can search by title or description, filter by execution status, creation date, project (in workspace views), and supported custom fields, sort supported columns, adjust which columns are visible, and open a run’s details or analysis.
The details view
Section titled “The details view”Opening a test run shows its test cases, sources, progress, and editable details.
Users with access can update:
- Title
- Description
- Labels
- Custom fields
- Manual test case selection
- Selected requirements
- Selected test suites
Newly added test cases start as Not Executed.
Changing test case sources
Section titled “Changing test case sources”A run’s test cases can come from manual selection, requirements, and test suites, and those sources can be changed after creation.
When a requirement or test suite is removed, Hawzu removes the test cases that source alone contributed. Test cases still covered by another source — manual selection, or another requirement or suite — stay.
Removing a test case from the run removes its recorded result for that session.
Recording and updating results
Section titled “Recording and updating results”From the details view you can open a test case and record its result, add step-level notes, attach evidence, assign work, and apply bulk updates. See Running Tests.
On an automated run, results arrive from the pipeline’s report instead — see Automated Test Runs.
Completing and resuming
Section titled “Completing and resuming”Marking a test run complete locks it: results, test case selection, and details stop accepting edits, which is what makes a finished run trustworthy to cite.
Resume the run to re-enable changes. Automation follows the same rule — a completed run refuses imports until it is resumed, and says so.
See Complete and Resume.
Exporting and sharing
Section titled “Exporting and sharing”Export a run’s results as CSV or JSON, or copy a shareable link that preserves your current filters. See Export and Share.
For the analysis workspace and its sign-off PDF, see Test Run Analysis.
Access
Section titled “Access”You need project access to edit test runs. Unlike release executions, a test run is never blocked by a release’s status — it does not belong to one.