> 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/whats-new/march-2025/test-gaps-coverage-focus.md).

# Test Gaps: Coverage Focus

<figure><img src="https://3871776571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTqMveDrJ1pB6OErwHvF0%2Fuploads%2FPXZ3vLFhh6K2uZbhvQSq%2FScreenshot%202025-03-24%20at%2021.53.37.png?alt=media&amp;token=1b6ae1a9-aacb-43f5-a090-7b886005535e" alt=""><figcaption><p>Coverage Percentage instead of Gap Percentage</p></figcaption></figure>

We've made some exciting updates to the Test Gaps Analysis (TGA) Report, all aimed at giving you a more straightforward and actionable understanding of your test coverage. We're shifting the focus from **gap** **percentages** to actual **coverage** **percentages**. This means you'll now see a clearer picture of how well your codebase is being tested, making it easier to identify areas needing attention.

So, what's changed? You'll notice new columns in both the TGA Report List and the TGA Report Page: "Overall Code Coverage" and "Code Changes Coverage". These columns directly show you the percentage of your code that's covered by tests. Next to these columns are the "Untested Overall Code" and "Untested Code Changes" columns, which tell you the exact number of methods that aren't being tested.

<figure><img src="https://3871776571-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTqMveDrJ1pB6OErwHvF0%2Fuploads%2FDcZrh9X672sYotINLUrL%2FScreenshot%202025-03-24%20at%2021.52.56.png?alt=media&amp;token=22449d11-17af-4085-aa22-7c2e8d6b39e6" alt=""><figcaption><p>New Terminology</p></figcaption></figure>

To make things even clearer, we've updated some of the terminology. For example, "# of Modified Methods" is now simply "Code Changes," and "# of Untested Modified Methods" is "Untested Code Changes." We've also removed the old "Overall Coverage Gap" and "Modified Coverage Gaps" columns, as they're no longer needed with the new coverage-focused approach.

And to ensure you understand everything at a glance, we've added help buttons to all the new columns. Just hover over them to get a quick explanation.&#x20;

These changes will make the TGA Report an even more valuable tool for ensuring your code is thoroughly tested.


---

# 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/whats-new/march-2025/test-gaps-coverage-focus.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.