> 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.md).

# Test Recommendations for Manual Testing

{% hint style="info" %}
The feature is available exclusively to SAP customers.
{% endhint %}

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

Test Recommendations for Manual Testing enables SAP customers to apply **Risk-Based Testing** without requiring a full integration with an external test management tool. By selecting the scope of their testing effort and triggering an analysis in SeaLights, manual testers receive a prioritized, downloadable list of test cases that covers all code and non-code changes introduced in a given set of SAP transports, moving teams from "test everything" to testing only what matters.

The feature is available exclusively to SAP customers, accessed via **Test Optimization → Test Recommendations** in the main navigation.

***

### Business Outcomes and Use Cases

* **SAP teams without test management tool integrations** get structured, change-driven test recommendations without any updates to the test management tool.
* **UAT and regression coordinators** scope a testing effort to a specific transport batch instead of running an entire test suite.
* **QA leads managing carry-over work** roll untested items from a previous cycle into a new one, maintaining continuity across releases.
* **QA leads managing carry-over work** roll untested items from a previous cycle into a new one, maintaining continuity across releases. When actual test results are reported back to SeaLights, Carry Over becomes especially powerful - completed and passed tests are automatically excluded from the new cycle, so teams continue exactly where they left off without manually tracking what's already been done.
* **Test authors and QA architects** use Test Gaps data to identify which modified SAP objects have no test coverage at all. Because gaps are presented within their execution context (the process flow they belong to), it is much easier to understand the functional impact of the gap and write a meaningful test that targets the right scenario.

***

### Three Outputs, One Cycle

Every Test Cycle produces three complementary results:

**Test Recommendations / what to run now** Existing test cases in your suite that cover the changes in the selected transports. Running these gives confidence that all modified SAP objects are validated by tests that already exist.

**Test Gaps / where your suite has no coverage** \
Modified SAP objects with no associated test case in the current suite. These are blind spots: even if every recommended test passes, these objects remain untested. Test Gaps are the actionable input for writing new tests and eliminating coverage debt over time.

**Coverage Report /** **how testing is progressing** A coverage report is automatically created for each cycle, tracking how much of the changed scope has been tested as the cycle progresses. It updates daily without any manual action, giving test managers and stakeholders a view of testing progress against the transport batch.

> 💡 Test Gaps are not failures, they are visibility. SeaLights surfaces them so teams can decide: accept the risk for this cycle, or invest in new tests before the next release.

***

### How It Works

Each Test Cycle is created through a short wizard where the user defines the application, test environment, test stage, and transport scope. SeaLights then runs a background analysis, tracing execution paths, mapping changed objects to the existing test suite, and identifying uncovered objects, and delivers both outputs as downloadable CSVs.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Full workflow of generating test recommendations.</td><td><a href="/files/XJ55ovj2FWpS1S9hDOzf">/files/XJ55ovj2FWpS1S9hDOzf</a></td><td><a href="/pages/Y3z8cVTCEHAF6LPP1TOw">/pages/Y3z8cVTCEHAF6LPP1TOw</a></td></tr><tr><td>Managing and reviewing past cycles.</td><td><a href="/files/UMyqJTz28tGS7OZJiqfn">/files/UMyqJTz28tGS7OZJiqfn</a></td><td><a href="/pages/GurgRTptis9Mgp0eCIdd">/pages/GurgRTptis9Mgp0eCIdd</a></td></tr><tr><td>Coverage tracking tied to each cycle.</td><td><a href="/files/nLdGYEUYS2X6XHZXUdpL">/files/nLdGYEUYS2X6XHZXUdpL</a></td><td><a href="/pages/9rhjrHL1I0O9uYnZKMKI">/pages/9rhjrHL1I0O9uYnZKMKI</a></td></tr></tbody></table>

### Test Recommendations&#x20;

The quality and precision of manual test recommendations depend on how deeply SeaLights is integrated into your testing workflow - specifically, whether test executions are reported back to SeaLights. There are three integration levels, each producing progressively more targeted recommendations.

Read more on [How SeaLights Builds Test Recommendations for SAP](/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing/how-sealights-builds-test-recommendations-for-sap.md)

***

### Key Concepts

<table data-search="false"><thead><tr><th width="180.2578125">Term</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Test Cycle</strong></td><td>A scoped recommendation request. Each cycle targets a specific application, test environment, test stage, and set of transports. Cycles are numbered sequentially and retained for 1 year.</td></tr><tr><td><strong>Test Recommendations</strong></td><td>The subset of your existing test suite that covers all changes in the cycle's transport scope. Delivered as a downloadable CSV.</td></tr><tr><td><strong>Test Gaps</strong></td><td>Modified SAP objects in the transport scope that have no test case in the current suite. Signals where new tests need to be written.</td></tr><tr><td><strong>Start Clean</strong></td><td>Cycle scope based on a new transport batch only — no carry-over from previous cycles.</td></tr><tr><td><strong>Carry Over</strong></td><td>Cycle scope that inherits pending (untested) items from a previous cycle, optionally supplemented with new transports.</td></tr><tr><td><strong>Transport / Build</strong></td><td>A unit of change in SAP. The transport scope defines which changes are analyzed in a given cycle.</td></tr><tr><td><strong>Execution</strong></td><td>A specific process flow (e.g., Order-to-Cash) used to group impacted objects and test cases.</td></tr><tr><td><strong>Coverage Report</strong></td><td>A Multi-App Coverage Report automatically generated for each cycle, updated daily while the cycle is active.</td></tr></tbody></table>


---

# 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.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.