> 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/test-stage-coverage-troubleshooting.md).

# Test Stage Coverage Troubleshooting

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

## Check for open Test Stage execution <a href="#check-for-open-test-stage-execution" id="check-for-open-test-stage-execution"></a>

Check on the Cockpit > Build Monitor if there is open test execution as indicated below for your specific Test stage. If so, either wait for the testing to complete or close the execution. Coverage will be calculated for the stage when all executions have been closed.

<figure><img src="/files/0OfbtvosISNHF9K2pHNh" alt=""><figcaption></figcaption></figure>

## Verify Application integration with a Test Listener <a href="#verify-application-integration-with-a-test-listener" id="verify-application-integration-with-a-test-listener"></a>

If the Application under test has not been integrated with the Sealights Test Listener, please refer to the setup and configuration pages [here](https://sealights.atlassian.net/wiki/spaces/SUP/pages/627114028) depending on the technology type.

If the Application has been integrated with the Sealights Test Listener, check on the Cockpit > Build Monitor if a Test Listener agent entry is present and the status of the Coverage Data Indicator icon. Green indicates coverage information has been sent to Sealights as below.

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

## Check for Active Test Listener Agents <a href="#check-for-active-test-listener-agents" id="check-for-active-test-listener-agents"></a>

Active Sealight Test Listener agents are viewable under the Cockpit > Agent Monitor as below. If your application is still running and nothing is reporting here, the Test Listener did not start properly when your application was launched. Check the application start up logging for activity relating to Sealights.

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

{% tabs %}
{% tab title="Java" %}
Refer to the [Command Reference](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/java-agent/command-reference.md#logging) for how to enable additional logging.
{% endtab %}

{% tab title="Node.js" %}
Refer to the [Command Reference](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/node.js-agent/command-reference.md#logging) for how to enable additional logging.
{% endtab %}

{% tab title=".NET" %}
Ensure the process from which coverage should be calculated is running and properly configured with SeaLights.\
Profiler logging instructions can be found in [Collecting Profiler Logs](/knowledgebase/setup-and-configuration/troubleshooting-faq/.net-.netcore/collecting-profiler-logs.md) doc.
{% 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/test-stage-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.