# Methods Not Showing as Covered

## Problem <a href="#problem" id="problem"></a>

I have tests hitting certain areas of my code for sure but SeaLights dashboard marks them as ‘Untested’.

## Solution <a href="#solution" id="solution"></a>

Verify that the tests are actually calling the methods in question by adding a system console log at the beginning of the method. Java example below:

{% code overflow="wrap" lineNumbers="true" %}

```
System.out.println("Sealights: <method name> was called");
```

{% endcode %}

**If the string does not appear:**

* Is the configuration of your tests validated to run against the right server?
* Is the same bytecode/artifact scanned by Sealights agent and used in the application server for sure?
* Is there a mocking tool used in this project or specifically in this testing configuration?
* Is the app behind a load balancer? If yes, is the log missing from all the instances behind the LB?

**If the string appears,** [open a Support ticket](https://docs.sealights.io/knowledgebase/contact-support) and provide SeaLights with the following:

* The relevant App,Branch,Build OR include a link to the SeaLights **cockpit** for the App,Branch,Build
* The test stage affected
* The console output that explicitly shows the method logs with the exact timestamp of the log (and the timezone set on the server)
* SeaLights agents logs from the application server in question in verbose mode (INFO)
* The CLASS file (Java) or any binary for SeaLights to analyze
* Provide SeaLights with a copy of the source code (file or code snippet containing the specific ‘missing’ method)
  * At a minimum, please provide a screenshot of the specific method code and its class definition.

In addition, **answer the following questions**

* Is this a new problem? If so, when did it start?
* Can we reproduce the issue in isolation of a single test? This single test can be manual or automated.
  * It is recommended to have a sandbox ready for troubleshooting and reproduction.
* Is the problem present only on a single specific test stage or is the method marked as untested in several stages?
  * did you/can you test on a different one?