Deleting Executions and Test Runs
2 min read
Deleting an execution or test run removes the testing session and its recorded results. It does not delete the original test cases or the project work used to select them.
Delete A Release Execution
Section titled “Delete A Release Execution”Delete a release execution from the execution details view when the testing session should no longer remain in the release.
Deleting a release execution removes:
- The execution
- Selected test case results for that execution
- Execution progress and analysis for that execution
Deleting a release execution does not delete:
- The release
- Repository test cases
- Requirements
- Test suites
- Defects
Defects created during the run stay in Hawzu, but they are no longer tied to the deleted execution.
Release Status Restrictions
Section titled “Release Status Restrictions”Release status can affect deletion and editing.
- Paused releases block execution work.
- Completed releases block execution work and execution edits.
- Archived releases are read-only for execution work.
If deletion is unavailable, check the release status and user access.
Delete A Test Run
Section titled “Delete A Test Run”Delete a Test Run from the test run details view when the standalone testing session should be removed.
Deleting a Test Run removes:
- The test run
- Selected test case results for that test run
- Test run progress and analysis
Deleting a Test Run does not delete:
- Repository test cases
- Requirements
- Test suites
- Releases
- Defects
Defect Impact
Section titled “Defect Impact”Deleting an execution or test run does not delete defects.
Defects remain available in Hawzu. However, links and analysis signals tied to the deleted testing session may no longer be available.
Review defect links before deleting a testing session if the team still needs traceability for release review or audit purposes.
Before Deleting
Section titled “Before Deleting”Before deleting, review:
- Whether the testing session still has active results.
- Whether failed test cases still need defect follow-up.
- Whether the execution contributes to release readiness.
- Whether the team still needs the testing history.
- Whether a release review depends on this execution.
Deletion should be used when the testing session is no longer needed.
Related Guides
Section titled “Related Guides”- Learn how to Manage Executions and Test Runs
- Review Execution Analysis
- Review Defect Insights
- Review Release Statuses