> For the complete documentation index, see [llms.txt](https://sealights-docs.tricentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sealights-docs.tricentis.com/readme.md). # Welcome! ## SeaLights for ABAP Every SAP release cycle revolves around four questions. SeaLights answers all of them — automatically, for every transport.
*** #### A change just landed. Which tests should I run? Without a live map from SAP objects to tests, teams guess — or run everything just to be safe. SeaLights builds that map automatically from your transports, tracing every changed object to the executables that depend on it and the tests that cover them. #### Testing takes time. What's the smallest set of tests that still covers the risk? Running everything "to be safe" is a tax on every release. SeaLights ranks executables by risk and produces an **Optimal Test Set** — the minimum number of tests that leaves no most-at-risk executable unverified. #### The tests ran. Did they actually cover the change? A green test run doesn't prove the change was ever exercised. SeaLights observes what each test actually touched at runtime and confirms — or corrects — every predicted link between tests and changed objects. #### What changed that has no test at all? The riskiest gaps are the ones nobody is looking for. SeaLights surfaces every changed object with zero test coverage in the **Test Gaps** tab, so teams can consciously decide to test, write a new test, or formally accept the risk. *** #### Discover SeaLights for ABAP
Cover image

Test Cycles

Learn what are test cycles, when to create one and how to make the most out of the outputs, and track progress

Ocean Deep.pngBroken link

How It Works

Learn how the dependency map is built, what is Most-At-Risk and what is considered an optimal test

Gentler Forest.pngBroken link

Coverage Analysis

How to read the Coverage Analysis to make the most out of it and when it is updated

Nebula.pngBroken link
--- # 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://sealights-docs.tricentis.com/readme.md?ask=&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.