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

Test Cycles

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

How It Works

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

Coverage Analysis

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