> 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/knowledge-base/sealights-for-abap/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

/files/Iy5JD7YdE3gRygwRc7If/pages/nTLogNnsgk267pyWXZGH

How It Works

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

/files/eFak515Dgmvzr3u2ZLE8/pages/Hd06pQgnOaHnhYKOX6LA

Coverage Analysis

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

/files/rKVMvKo9wuseQ40IvvYM/pages/tAyqy14hZeNIM4iHEhnD
--- # 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/knowledge-base/sealights-for-abap/readme.md?ask=&goal= ``` `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.