> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/test-context-manager-documentation/requirements/creating-a-requirement/traceability.md).

# Traceability

Link requirements, test cases, and bugs to measure coverage.

## Traceability

Traceability connects requirements to the test cases that verify them.

It also connects requirements to the bugs found while testing those areas.

To build traceability:

1. Open a requirement detail page.
2. Link the test cases that cover the requirement in **Linked Work Items**.
3. Open a test case detail page.
4. Link the requirements covered by that test case.
5. Open a bug detail page.
6. Link the related test case and requirement.

After these links are in place, the traceability report shows the coverage matrix.

### Coverage status

| Coverage Status | Meaning                                           |
| --------------- | ------------------------------------------------- |
| Covered         | At least one linked, passing test case exists.    |
| Partial         | Linked test cases exist, but not all are passing. |
| Uncovered       | No linked test cases exist for the requirement.   |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mozark.ai/test-context-manager-documentation/requirements/creating-a-requirement/traceability.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.