Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Linking Tests to Requirements

Connect test cases to requirements so coverage and traceability stay intact.

Overview

Linking tests to requirements provides end-to-end traceability. Links also surface coverage gaps before UAT.

Screenshot placeholder: requirement detail view with a “Linked tests” section.

Key Concepts

  • Coverage: requirement to test case mapping

  • Traceability: links that connect scope to validation evidence

  • Verification: defining “done” as tested

How It’s Used

Link tests after requirement approval. Use links for coverage reporting and go/no-go readiness.

Benefits

  • Clearer definition of done for scope items

  • Faster coverage reporting

  • Better audit evidence through linked results

Setup Steps

When to link

Link tests when:

  • The requirement is approved and ready for verification.

  • A clear “done means tested” criterion is required.

  • Stakeholders need a coverage view.

Link from a requirement

1

Open the requirement

  1. Go to Requirements.

  2. Open the requirement to validate.

2

Add linked tests

  1. Find Tests / Linked tests.

  2. Click Link test (or Add test).

  3. Select one or more test cases.

GIF placeholder: linking an existing test case to a requirement.

Link from a test case

1

Open the test case

  1. Go to Tests.

  2. Open the test case.

2

Link requirements

  1. Find Requirements / Linked requirements.

  2. Click Link requirement.

  3. Select the requirement(s) this test verifies.

Best Practices

  • Keep links 1:many when possible.

    • One requirement can map to multiple tests.

  • Put the pass/fail criteria in the test steps.

  • Use a “smoke” test for broad requirements.

  • Add a note when coverage is intentionally out-of-scope.

Troubleshooting

Requirement or test is not available in the link picker

Common causes:

  • Missing access to the item Project scope.

  • The item is in a different Project.

  • Filters are applied in the picker.

Try clearing filters. Then confirm access with a Project Admin.

Links do not appear in reports

Check:

  • The change was saved after linking.

  • The report uses the correct Project and date filters.

  • The report is using requirements/test case objects (not tasks).

Summary

Linking tests to requirements provides coverage tracking.

Links also support traceability for audits and readiness reviews.

Related:

Last updated