Executions and Test Runs FAQs
1 min read
These answers explain the difference between release-bound executions and standalone test runs.
What is an execution?
Section titled “What is an execution?”An execution is a testing session inside a release. A release can contain multiple executions, such as initial testing, fix validation, regression, and final sign-off.
Executions follow release status rules.
What is a test run?
Section titled “What is a test run?”A test run is a standalone project testing session. It is not tied to a release.
Use test runs for ad-hoc testing, exploratory testing, quick validation, and regression outside formal release cycles.
How do I choose test cases?
Section titled “How do I choose test cases?”Both executions and test runs can include test cases selected:
- Manually.
- From requirements.
- From test suites.
Hawzu deduplicates selected test cases where the same test case appears from multiple sources.
What result statuses are available?
Section titled “What result statuses are available?”Test cases can be marked:
- Passed
- Failed
- Blocked
- Skipped
- Not Executed
Learn more in Running Tests.
Can I assign test cases?
Section titled “Can I assign test cases?”Yes. Assignments help distribute execution work and clarify ownership.
Use assignments consistently, especially for large executions or test runs.
Where do I review analysis?
Section titled “Where do I review analysis?”Use:
- Execution Analysis for a single execution or test run.
- Defect Insights for failed test cases, linked defects, and defect pressure.
- Release Insights for release-level readiness.