> 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/phased-onboarding/java-onboarding-guide/phase-2-advanced-coverage-analytics.md).

# Phase 2: Advanced Coverage Analytics

{% hint style="warning" %}
**Prerequisite:** You have completed [Phase 1: Core Coverage](/knowledgebase/phased-onboarding/java-onboarding-guide/phase-1-core-coverage.md)
{% endhint %}

## Overview

In this phase, you'll enable SeaLights to capture **granular coverage information**—specifically, coverage per **test stage**.

For example, if your test strategy includes distinct testing categories (such as *Functional Tests*, *End-to-End Tests*, etc.) or uses multiple testing frameworks (e.g., JUnit, TestNG), this phase allows you to view **coverage breakdowns by test stage** in SeaLights.

You'll be able to answer questions like:

> *"What percentage of the code changed in this sprint was covered by functional tests?"*

### What You'll Get

* **Granular coverage by test stage** — View coverage across different test types such as Integration, Regression, and E2E
* **Optimized test strategy insights** — Understand which test types need improvement
* **Data-driven release decisions** — Make more informed decisions based on coverage by test type

#### Supported Test Types

SeaLights supports capturing this level of detail for:

* Standard test frameworks (e.g., JUnit, TestNG) executed without Maven or Gradle
* Standard test frameworks executed via Maven or Gradle
* Custom test frameworks
* Manual test runs

## Implementation Steps

### Choosing Your Implementation Path

Before proceeding, please determine **which kind of test runner or framework you are using**, as the next steps will vary:

* If you are using a **supported test framework** such as TestNG, JUnit, or Cucumber, continue to:  [Using Supported Test Frameworks](/knowledgebase/phased-onboarding/java-onboarding-guide/phase-2-advanced-coverage-analytics/using-supported-test-frameworks.md)
* If you are **not using a supported test framework**, continue to [Using Non-Supported Test Frameworks](/knowledgebase/phased-onboarding/java-onboarding-guide/phase-2-advanced-coverage-analytics/using-non-supported-test-frameworks.md)


---

# 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/phased-onboarding/java-onboarding-guide/phase-2-advanced-coverage-analytics.md?ask=<question>&goal=<user_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.