> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/transformations/linking-tests-to-requirements.md).

# Linking Tests to Requirements

### Overview

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

{% hint style="info" %}
Screenshot placeholder: requirement detail view with a “Linked tests” section.
{% endhint %}

### 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

{% stepper %}
{% step %}

### Open the requirement

1. Go to **Requirements**.
2. Open the requirement to validate.
   {% endstep %}

{% step %}

### Add linked tests

1. Find **Tests** / **Linked tests**.
2. Click **Link test** (or **Add test**).
3. Select one or more test cases.

{% hint style="info" %}
GIF placeholder: linking an existing test case to a requirement.
{% endhint %}
{% endstep %}
{% endstepper %}

#### Link from a test case

{% stepper %}
{% step %}

### Open the test case

1. Go to **Tests**.
2. Open the test case.
   {% endstep %}

{% step %}

### Link requirements

1. Find **Requirements** / **Linked requirements**.
2. Click **Link requirement**.
3. Select the requirement(s) this test verifies.
   {% endstep %}
   {% endstepper %}

### 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

<details>

<summary>Requirement or test is not available in the link picker</summary>

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.

</details>

<details>

<summary>Links do not appear in reports</summary>

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).

</details>

### Summary

Linking tests to requirements provides coverage tracking.

Links also support traceability for audits and readiness reviews.

Related:

* [Create Test Cases](/transformations/create-test-cases.md)
* [Test Organization and Views](/transformations/test-organization-and-views.md)
* [Requirements](/transformations/requirements.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/transformations/linking-tests-to-requirements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.