> 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
## Verify Build data reported
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.
## Verify Test Listener status
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.
{% 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
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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/general/missing-or-insufficient-test-stage-coverage/unit-test-coverage-troubleshooting.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.
.png?alt=media&token=ef21b515-3bfc-4882-a090-4cf22388ef6a)
