Skip to content
Hawzu Docs
API reference Go to app

Requirement Usages

2 min read

Requirements are reusable project records. Once created, they can be linked and reviewed across several Hawzu areas to support coverage and traceability.

Requirement Details

Section titled “Requirement Details”

The requirement details view is the main place to review usage.

It shows:

  • Linked test cases
  • Related releases
  • Related testruns
  • Directly linked defects
  • Defects linked through the requirement’s test cases

Use these tabs to understand how a requirement is being validated and where related issues appear.

Test Cases

Section titled “Test Cases”

Requirements can be selected while creating or editing repository test cases.

Linking requirements to test cases helps show which requirements have coverage and which requirements still need tests.

Requirements also appear in test-case filters as:

  • With Requirements
  • Without Requirements
  • Specific requirements

Test Suites

Section titled “Test Suites”

Test suites can use requirements in test-case filters. This helps teams build suites around specific requirements or find test cases with or without requirement coverage.

When a test suite uses requirement filters, the suite selection stays aligned with the requirement links on matching test cases.

Testruns And Executions

Section titled “Testruns And Executions”

Requirements can be selected while creating or updating testruns and executions.

When you add a requirement, Hawzu can add the test cases linked to that requirement. If you later remove the requirement from the run, test cases that were added only because of that requirement may be removed from the run.

Deleted requirements may still appear as historical snapshots in existing runs until removed from that run.

Releases

Section titled “Releases”

Requirement details show releases and release executions that use the requirement.

Use this to understand whether a requirement is part of release validation and which release executions are connected to it.

Defects

Section titled “Defects”

Defects can be linked to requirements through traceability.

In defect traceability, users can select:

  • Requirements
  • Test cases
  • Releases and executions

Requirement details separate defect relationships into:

  • Directly Linked Defects
  • Defects Linked via Testcases

This helps distinguish defects tied directly to a requirement from defects discovered through related test cases.

Labels

Section titled “Labels”

Requirements support labels. Labels help categorize requirements alongside other project items such as test cases and releases.

Label details also show requirements that use a label, making it easier to review all work grouped under the same label.

Repository Coverage

Section titled “Repository Coverage”

Repository views use requirement links to help calculate and display traceability coverage.

Use requirement coverage signals to find:

  • Requirements without linked test cases
  • Test cases without requirements
  • Areas where traceability may need cleanup

Next Steps

Section titled “Next Steps”