> 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/reports-and-analytics/generating-a-report/traceability-report.md). # Traceability report View requirement coverage, linked test cases, and related bugs in one matrix. ## Traceability report The traceability report provides a full matrix connecting requirements, test cases, and bugs. Open **Reports** → **Traceability** to access it. Use this report to compare product requirements against the testing work and defects connected to them. The report shows: * every requirement in the project * the test cases linked to each requirement * the latest execution status of each linked test case * any bugs linked to those test cases * an overall coverage status for each requirement ### What it helps you compare The matrix helps you review each requirement against three related signals: * linked test cases for planned coverage * latest execution results for actual coverage * linked bugs for quality risk This view helps you see whether a requirement is covered, partially covered, or still exposed. It also helps you compare one requirement against another during release reviews. Coverage status values include: * `Covered` * `Partial` * `Uncovered` ### How teams use it Teams often use the traceability report to answer these questions: * Which requirements are fully covered by tests * Which covered areas still have open bugs * Which requirements need more testing before release This report is especially useful before sign-off or GA review. It provides a single view of coverage depth, execution outcomes, and defect linkage. You can use these signals to support a release readiness or GA readiness assessment. Additional views include: * **Coverage by Priority** as a bar chart * **Coverage Trend** as a line chart * **Uncovered List** as a sortable table --- # 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/reports-and-analytics/generating-a-report/traceability-report.md?ask=&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.