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

# Test Optimization for SAP

SeaLights supports test optimization for SAP/ABAP environments across both automated and manual testing workflows. Most of the Test Optimization experience, including the Optimization Strategy, Monthly Savings Report, and general configuration, works the same way for SAP as for any other technology. The SAP-specific adaptations are focused in two areas.

***

### Automated Test Optimization

Automated test optimization for SAP follows the same flow as any other technology integrated with SeaLights. When a transport is imported, SeaLights identifies the impacted ABAP objects and recommends the tests that should run, directly within the CI/CD pipeline or test automation tool.

The main SAP-specific difference is in the **Savings Breakdown page**, which adapts its terminology and hierarchy to reflect SAP concepts: transports replace builds, and results are organized by App Area and Execution rather than by file or path. See [Savings Breakdown for SAP](/knowledgebase/test-optimization/test-optimization-for-sap/savings-breakdown-for-abap-sap.md) for details.

***

### Manual Test Optimization

Manual test optimization for SAP has a dedicated experience within SeaLights, enabling teams to plan and execute transport-based testing directly from the SeaLights UI. Testers can create test cycles, retrieve prioritized test recommendations, identify test gaps, and track coverage - all scoped to a specific set of transports. This gives SAP teams a focused workflow for reducing manual testing effort while maintaining confidence in release quality.

{% hint style="info" %}
This workflow is intended for teams using SeaLights as the primary interface for SAP manual test optimization. Teams with a full external test management integration may consume recommendations through their integrated test management workflow instead.
{% endhint %}

See [Test Recommendations for Manual Testing](/knowledgebase/test-optimization/test-optimization-for-sap/test-recommendations-for-manual-testing.md) for the full workflow.

<details>

<summary>Supported Test Management Frameworks</summary>

SeaLights can construct and maintain the semantic mapping, between SAP executions, ABAP objects, and test cases, for the following frameworks. This means teams using these frameworks can receive recommendations via the SeaLights UI based on the semantic model. It does not involve reporting test results back to SeaLights or delivering recommendations inside the framework itself.

* **qTest** (Cloud and on-prem)
* **Tosca** (Cloud and on-prem)\
  Although Tosca is an automated testing framework, teams can use this flow to get recommendations from the semantic model, then execute the recommended tests through their regular Tosca integration, with results reported back to SeaLights as normal. This allows them to benefit from targeted recommendations even before a statistical model has been built.
* **OpenText ALM**
* **Worksoft Certify**
* **SAP Solution Manager**
* **Microsoft Azure DevOps**
* **Xray** (Requires Jira export)
* **Excel**

For more on how the semantic model works and what it means for recommendation precision, see [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).

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