# Test Runner: Running the tests and seeing the coverage

Running the tests is done via the **test\_runner** pipeline, in this pipeline you'll see some of the most popular testing frameworks and how it's integrated with Sealights. 

{% hint style="info" %}
We're not going to dive into every testing framework. If you want to know how to integrate Sealights test runner agent on a specific testing framework check the relevant pipeline stage.

You can find the pipeline in the repository under jenkins/jenkinsfiles/test\_runner.groovy
{% endhint %}

When running the test\_runner you will be redirected to the "stage view", there you'll see the pipeline's stages.

<figure><img src="https://600168856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHdVvmW2UjgonyUPlD7oS%2Fuploads%2FfzDRscagPghmhrxaUoKH%2Fimage.png?alt=media&#x26;token=144a8121-c923-4d03-be1f-5a9440245ef4" alt=""><figcaption><p>pipeline's stages</p></figcaption></figure>

When starting a test stage you should be able to see the new integration build in the Sealight's website dashboard.

<figure><img src="https://600168856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHdVvmW2UjgonyUPlD7oS%2Fuploads%2FEVd7tllpL26OsmAbrUvC%2FScreenshot%20from%202023-12-25%2009-34-50.png?alt=media&#x26;token=37c25185-cc6e-4ab5-8507-ed4ea2616596" alt=""><figcaption><p>Integration build updated</p></figcaption></figure>

{% hint style="info" %}
The difference between a normal build and an integration build is that the normal build is one scanning one app and you run the tests on it. The integration build consists of multiple apps that share the same lab\_id, when running tests using a lab\_id which is given to multiple Sealights agents who are currently online (apps running with Sealights) it automatically understands you're trying to test an app of multiple microservices.
{% endhint %}

When clicking on the coverage (The 0% in the picture) you will be redirected to the stage view page, there you should be able to see all the microservice that were deployed and **are currently running** using the same lab\_id that we used to run the tests

<figure><img src="https://600168856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHdVvmW2UjgonyUPlD7oS%2Fuploads%2FtOzUWEbgUKwVT8yb3l3U%2FScreenshot%20from%202023-12-25%2010-15-03.png?alt=media&#x26;token=363d1ff4-6d59-451a-9e1b-788726013dc0" alt=""><figcaption><p>All the microservices that are running that share the same lab_id</p></figcaption></figure>

After some time you should start seeing the (in progress) under the integration build's coverage indicating that there is a test in progress

<figure><img src="https://600168856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHdVvmW2UjgonyUPlD7oS%2Fuploads%2FTkCZ4Dt5eOysXqMJswwt%2FScreenshot%20from%202023-12-25%2015-47-31.png?alt=media&#x26;token=846609a0-368f-4858-bf3c-7a9e91d86a3e" alt=""><figcaption><p>Integration build under test</p></figcaption></figure>

When clicking the bar (for example public-BTQ the build name) it will reveal all the test stages including those in progress.

<figure><img src="https://600168856-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHdVvmW2UjgonyUPlD7oS%2Fuploads%2F7YhO6bTp1jO79mJIBVZg%2FScreenshot%20from%202023-12-25%2015-48-03.png?alt=media&#x26;token=eb7e0630-8a85-43c1-abd4-16f01f65418f" alt=""><figcaption><p>Revealing test stages</p></figcaption></figure>

After a while you should be able to see the coverage start increasing until reaching 68% in this example.

\--------------- add percentage without in progress /// going to show percentages, need them to be stable

Congrats, you can now see the tests coverage of the code, the next step is getting modified coverage. Meaning getting how much of the code changes are covered by the tests. There is a way to do it easily and we'll show you how next.

Or if you're not currently interested in that we suggest we give you a tour in our website to show you very useful features we offer that will help you understand your code and/or debug.

{% content-ref url="../../sealights-website/tour-through-sealights-website" %}
[tour-through-sealights-website](https://docs.sealights.io/boutique-project/sealights-website/tour-through-sealights-website)
{% endcontent-ref %}