# Test Stage Filtering for Group Coverage Trends

At SeaLights, we believe in consistency across your quality data. Based on customer feedback, we’ve updated the **Group Coverage Trend** report to include **Test Stage Filtering**, aligning it with our standard single-app coverage trend report.

#### The Update: Granular Visibility Across Apps

You can now filter the Group Coverage Trend by specific test stages. The filter dynamically displays all stages that reported data within your selected timeframe, allowing you to isolate specific phases—like *Unit*, *Functional*, or *SIT*—across your entire application group.

#### Why It Matters

* **Unified Reporting:** Use the same filtering logic for a single microservice as you do for an entire business unit.
* **Targeted Insights:** Instantly identify which specific test stage is driving (or lagging) coverage across multiple projects.
* **Sharper Quality Gates:** Base your aggregate quality decisions on the specific stages that matter most for your current release.

#### How to Use It

<div><figure><img src="/files/B4NCZSrWXUW1yE9xQ4Le" alt="" width="455"><figcaption><p>New Switch for Test Stages</p></figcaption></figure> <figure><img src="/files/qdwCrpgWrurdxDQhJY1q" alt="" width="455"><figcaption><p>Dynamic List of Test Stages</p></figcaption></figure></div>

Simply navigate to your Group Coverage Trend report, under Quality Analytics and switch on the new **"Test Stages"** section to refine your view. The trend lines will instantly recalculate to show the specific coverage contributed by your selected stages.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sealights.io/knowledgebase/whats-new/february-2026/test-stage-filtering-for-group-coverage-trends.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.