> 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/report-types.md). # Report types ## Report types Test Manager includes several report types. | Report Type | What it shows | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | Functional Test Execution Summary | Aggregated results such as total test cases, pass rate, failure rate, blocked count, execution duration, and top failing test cases. | | Defect Summary | Bug statistics such as total bugs, open versus resolved, severity distribution, top reporters, and creation trends. | | Requirement Coverage | Coverage across requirements, including linked test cases, execution progress, and overall requirement coverage status. | | Traceability Matrix | A coverage matrix that compares requirements against linked test cases, execution status, test planning, and related bugs. | ### Functional Test Execution Summary Use this report to review overall execution health for a selected scope of test runs. It summarizes how functional test cases are performing across active or completed execution cycles. This report helps teams answer key execution questions: * How many test cases passed, failed, or were blocked * Which test runs are progressing on track * Where bug creation is increasing during execution The report typically includes: * total executed test cases * pass, fail, blocked, and skipped counts * pass rate and failure rate * execution trend over time * top failing test cases * bugs raised from failed execution Use this report during daily test reviews, cycle tracking, and release checkpoints. It gives stakeholders a clear view of execution progress and functional quality. ### Defect Summary Use the defect summary to review bug volume, severity, and resolution trends across the selected scope. This report helps teams understand the quality impact of issues found during testing. It can help answer questions such as: * How many bugs are still open * Which severities are increasing * Whether defect resolution is keeping pace with discovery The report typically includes: * total bugs raised * open versus resolved bugs * severity and priority breakdown * bug creation trend * top reporters or impacted areas Use this report to track defect backlog health and release risk. ### Requirement Coverage Use this report to measure how much of the requirement set is backed by linked and executed tests. It focuses on coverage completeness rather than detailed bug-by-bug traceability. This report helps teams answer: * Which requirements already have linked test cases * Which requirements still lack execution coverage * What percentage of the requirement set is covered The report typically includes: * total requirements in scope * requirements with linked test cases * executed versus unexecuted coverage * covered, partial, and uncovered counts * overall coverage percentage Use this report before planning sign-off, coverage reviews, and release readiness checks. ### Traceability Matrix Use the traceability matrix to compare requirements against the testing work that supports them. It shows how each requirement maps to linked test cases and whether those test cases are being planned and executed. This helps teams answer three key questions: * Does each requirement have test coverage * Are the linked test cases included in active testing workflows * Are open bugs affecting covered requirements The matrix combines requirement linkage, latest execution state, and related bug data in one view. This makes it easier to spot gaps before release reviews. Teams can use this report to assess coverage completeness, defect impact, and overall release readiness for GA decisions. For the full workflow and coverage views, see [Traceability report](/test-context-manager-documentation/reports-and-analytics/generating-a-report/traceability-report.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://docs.mozark.ai/test-context-manager-documentation/reports-and-analytics/generating-a-report/report-types.md?ask=&goal= ``` `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.