Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Problem: My Test stage shows 0% Coverage

Solution

Functional and Automated Tests

  • In the Cockpit > Build Monitor, Is there an Agent from the App Server reported for the Test Stage

    • Is the application server properly configured with a Sealights' Coverage Collector agent ? A Test Listener entry with Lab ID should be visible along with the agent coverage indicator (green indicates coverage was reported to Sealights)

    • Is the right Lab ID set?

    • Is the right BSID provided ? Check in the Build monitor JSON entry if the Test Listener BSID is the expected one

      • Are the tests properly executed against the right instance of Application Server with SL instrumentation ?

      • Please provide the logs at INFO level to Sealights via a Ticket opened to Support.

Unit Tests

  • Java

    • In the Cockpit > Build Monitor, check the general build scan information to ensure the expected data was reported to Sealights e.g. expected number of modules and methods, check that the packagesIncluded and packagesexcluded strings are correct.

If using Sealights Maven plugin with surefire for Unit Tests, check in the Cockpit > Build Monitor in the Test Listeners tab that there are Test Listener(s) agents showing with the “surefire” tag and that they have reported coverage to Sealights (green indicator) as shown below.

  • slnodejs

  • dotnet

  • No labels