> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-analyzer/source-code-analysis/coverage-reports.md).

# Coverage Reports

## Uploading Coverage Reports

{% hint style="warning" %}

* IZ Analyzer does not run MUnit tests or generate reports. It only imports the pre-generated reports in Json format.
  {% endhint %}

### How to generate coverage report

1. Coverage report should be configured in JSON format for IZ Analyzer to scan and upload the report. Refer to [Maven Configuration for Coverage](https://docs.mulesoft.com/munit/2.2/coverage-maven-concept).
2. Before scanning the project, make sure MUnit test cases are executed and coverage report is generated.

### Coverage report upload

1. IZ Analyzer scans the coverage JSON report from appropriate locations based on the Mule version. No additional configuration parameters are required to enable scanning of coverage reports
2. Following directories will be scanned for coverage report based on the mule version. (These are the default locations where MUnit coverage reports will be generated) -
   1. Mule 3 **`target/munit-reports/coverage-json/report.json`**
   2. Mule 4 **`target/site/munit/coverage/munit-coverage.json`**
3. On successful analysis coverage report should be uploaded to server with following statistics -
   1. Overall coverage percentage\
       

      <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FKfJtkA1iilhelyUhGmq0%2Fmunit-coverage_overall.png?alt=media&amp;token=560dea67-4469-4ea7-aafb-a1f9d4a9d3ef" alt=""><figcaption></figcaption></figure>
   2. File level coverage percentage\
      &#x20;

      <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FWbEUATgPoQdL7GOISSau%2Fmunit-coverage-file-level.png?alt=media&amp;token=733f7f1d-46b6-440b-ac40-b43399a6cdd1" alt=""><figcaption></figcaption></figure>
   3. Flow level coverage details details\ <br>

      <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F9syiSzJnr1SuwUPDNBDs%2Fmunit-coverage-flow-level.png?alt=media&amp;token=b656931e-4f22-42df-9b48-e3852804df5e" alt=""><figcaption></figcaption></figure>

## See Also

* [Code Analysis In Server](/product-guides/integral-zone/iz-analyzer/manage-server-plugin/install-server-plugin.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 by asking a question.

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

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-analyzer/source-code-analysis/coverage-reports.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.