#Test Runs & Execution FAQs - Common Questions
This section answers common questions about test runs and test execution in Hawzu.
#What is a test run?
A test run is an execution session where selected test cases are executed and their results are recorded.
Test runs help you:
- Track execution progress
- Record test case outcomes
- Assign work to team members
- Analyze execution results
#How do I create a test run?
To create a test run:
- Navigate to Test Runs
- Click Create Test Run
- Enter test run details (title and description)
- Select test cases using:
- Manual selection
- Test suites
- Requirements
- Click Create
For detailed steps, see Test Runs Overview.
#Can I create a test run without a release?
Yes.
Test runs can be created independently, without linking them to a release.
This is useful for:
- Ad-hoc testing
- Exploratory testing
- Validation outside formal release cycles
#What’s the difference between a test run and a release?
- Test Run: A single execution instance containing test cases and results
- Release: A container that groups multiple test runs over time for a specific version or milestone
Releases provide historical context and progress tracking across multiple executions.
#What are the test case statuses in a test run?
Each test case in a test run can have one of the following statuses:
- Not Executed – Test has not been run yet
- Passed – Test executed successfully
- Failed – Test execution failed
- Blocked – Execution blocked by an external dependency
- Skipped – Test intentionally skipped
#How do I update a test case status?
To update a test case status:
- Open the test run
- Click on a test case
- Execute the steps
- Select the appropriate status
- Add step-level notes if needed
- Save the result
Statuses can also be updated in bulk for multiple test cases.
#Can I assign test cases to team members?
Yes.
Test cases can be assigned:
- During test run creation
- After creation using bulk actions
Assignments help distribute workload and clarify ownership during execution.
#When is a test run considered completed?
A test run is considered completed when all test cases have been executed
(Passed, Failed, Blocked, or Skipped).
Completed test runs:
- Remain fully visible
- Retain all execution history
- Are used for analytics and reporting
#Can I modify a test run after execution starts?
- Execution results remain intact
- Test case assignments can be updated
- Test case results can be corrected if needed
Whether test cases can be added or removed after creation depends on your project’s execution rules.
#Can I add test cases to an existing test run?
This depends on project configuration.
Some projects allow:
- Adding new test cases after creation
Others enforce:
- A locked test run once execution begins
Check with your project administrator if you’re unsure.
#Still have questions?