Test Suite Usages

Test suites are designed for reuse. Once a suite is created, it can be selected in testruns and executions to add the suite’s test cases quickly.

---

Testruns

Test suites can be selected when creating or editing testruns.

When you add a test suite, Hawzu adds the test cases from that suite to the run. If the suite combines manual and filter-based selections, the run receives the unique test cases from both sources.

When you remove a test suite from a testrun, test cases that were added only because of that suite may be removed from the run.

Removing a suite from a testrun does not delete the test suite itself.

---

Executions

Test suites can also be selected when creating or editing executions.

The test suite picker shows active suites and previews the test cases that will be added. Suites already selected in the same run or execution are not shown again.

---

Releases

Executions can be grouped under releases. When those executions use test suites, the suites help define the testing scope for release validation.

Use suites for release checks when the same group of tests should be reused across release cycles.

---

Test Case Sources In Runs

Runs and executions can include test cases from several sources:

• Direct manual selection
• Requirements
• Test suites

Hawzu tracks which source added each test case. If a test case is included by more than one source, it appears once in the run.

---

Deleted Test Suites In Existing Runs

If a test suite is deleted after it was used in a testrun, the run may still show a snapshot of that deleted suite.

The deleted suite cannot be selected again after it is removed from the run.

---

Usage Counts

The Test Suites page includes a Usages column. Use it to see whether a suite is actively used before editing or deleting it.

---

Next Steps

• Learn how to create test suites
• Review how to manage test suites
• Learn about test runs