> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/general/missing-or-insufficient-test-stage-coverage/unit-test-coverage-troubleshooting.md).

# Unit Test Coverage Troubleshooting

<figure><img src="/files/GngB4Jvh1bz6a4OyTg3u" alt="" width="563"><figcaption></figcaption></figure>

## Verify Build data reported <a href="#verify-build-data-reported" id="verify-build-data-reported"></a>

Under Cockpit > Build Monitor, check if the overall Build information is correct e.g. the expected number of modules and methods reported. If not, check the Sealights `packagesIncluded` and `packagesExcluded` arguments.

<figure><img src="/files/4fiO622ZXU7bWfsEouZv" alt=""><figcaption></figcaption></figure>

## Verify Test Listener status <a href="#verify-test-listener-status" id="verify-test-listener-status"></a>

Under Cockpit > Build Monitor, on Unit Tests tab, check there is at least one Test Listener entry present and the status color of the Coverage Data Indicator. Green indicates coverage has been successfully sent to Sealights.

<figure><img src="/files/ys4S8TpdwUC3YmWH71aG" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="Java" %}
When using Sealights Maven plugin with Surefire, check that the Test Listener shows the “surefire” tag. Check CI log for Unit Test step if no Test Listener agent is listed in Build Monitor.
{% endtab %}

{% tab title=".NET" %}
When using Azure DevOps / VSTS plugin, ensure that the correct process architecture is defined for the process running the tests (MSTest, xUnit etc.)
{% endtab %}
{% endtabs %}

## Contact Sealights Support <a href="#contact-sealights-support" id="contact-sealights-support"></a>

If none of the above suggestions helped you to resolve the issue please [contact us](https://docs.sealights.io/knowledgebase/contact-support) for assistance.


---

# 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.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/general/missing-or-insufficient-test-stage-coverage/unit-test-coverage-troubleshooting.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.