> 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/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/multi-app-coverage-report-for-test-cycle.md).

# Multi-App Coverage Report for Test Cycle

Every SAP Manual Testing Cycle automatically generates a dedicated **Multi-App Coverage Report** the moment the cycle is created. The report is scoped to the exact application, test environment, test stage, and transports defined in the cycle, and refreshes daily without any manual action. This creates a direct link between each testing effort and its coverage outcomes, with no report setup required.

The report is accessed from the **Test Cycle List** via the Coverage Report button on each cycle row, which opens it in a new tab.

For a full explanation of how the report is structured and what its data represents for SAP, see [Multi-App Coverage Report: SAP Report Structure](/knowledgebase/coverage-and-quality-insights/multi-app-coverage-report/multi-app-coverage-report-sap-report-structure.md).

<figure><img src="/files/AvGX0yJ1cFuRNQWs4eB1" alt=""><figcaption></figcaption></figure>

***

### Business Value & Key Use Cases

* **SAP QA leads** move from triggering a test cycle to viewing live coverage data in a single click, without any additional configuration.
* **Test managers closing a release cycle** use the report as an authoritative coverage record for that transport batch - a final update runs automatically at cycle closure.
* **Hybrid teams** (SAP + other technologies) see SAP cycle coverage alongside reports for other apps in the standard Multi-App Coverage workspace.

***

### Automatic Report Creation

When a cycle is created, SeaLights automatically generates a coverage report inheriting the cycle's application, test environment, test stage, and transport scope. No manual configuration is needed.

The report automatically includes all builds from the starting transport up to the moment of the cycle creation.

The report refreshes daily while the cycle is active. When the cycle is closed, a final refresh runs automatically, after which the report is considered finalized and stops updating.

The transport scope (build IDs) stored in the report metadata is **not altered** by scheduled updates, only the coverage data is recalculated.

### Access and Editing

Auto-generated cycle reports **cannot be edited or duplicated**. To change the coverage scope, create a new cycle with the desired configuration.

The report name defaults to the cycle name and can be renamed at any time without affecting the cycle or its data.

For SAP-only accounts, coverage reports are accessible only via the Cycle List. For hybrid accounts (SAP + other technologies), they also appear in the standard Multi-App Coverage report list.

***

### FAQ

<details>

<summary><strong>Can I manually trigger a report update?</strong> </summary>

No. The report refreshes automatically each day at 00:00 UTC while the cycle is active, and once more when the cycle is closed.

</details>

<details>

<summary><strong>Can I change the report name?</strong> </summary>

Yes, renaming the report has no effect on the cycle or its data.

</details>

<details>

<summary><strong>Can I find SAP cycle reports in the standard Multi-App Coverage report list?</strong> </summary>

Yes, the SAP cycle reports are available in the Multi-App Coverage report list.

</details>

<details>

<summary><strong>Can I edit the report's scope or configuration?</strong> </summary>

No. The report is derived from the cycle and cannot be modified.&#x20;

</details>

<details>

<summary><strong>Why does the report show "NA" for Overall Coverage?</strong> </summary>

The Overall Coverage metric is not applicable to SAP manual testing cycles in the current implementation. This is expected behavior, not an error.

</details>

<details>

<summary><mark style="color:red;"><strong>Can the daily refresh schedule be changed to run more frequently?</strong></mark> </summary>

This may be configurable at the account level depending on infrastructure support. Contact your SeaLights Customer Success Manager or Solution Architect to explore this option.

</details>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.sealights.io/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/multi-app-coverage-report-for-test-cycle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.