FAQ

Does SeaLights require a baseline of test execution history before it can recommend tests?

No. The Day Zero layer operates entirely on structural analysis — dependency maps and risk heuristics — with no execution history required. You get change impact analysis and a recommended test set from the very first cycle. Execution history improves accuracy over time but is not a prerequisite.

What is a "transport" in the context of SeaLights for ABAP?

A transport (also called a Transport Request) is the standard SAP mechanism for moving code changes, configuration, or customization between SAP systems (e.g., from Development to QA to Production). SeaLights uses the transport as the input unit for change analysis — each cycle is scoped to one or more transports.

What happens if a changed object has no tests covering it at all?

It appears in the Test Gaps tab of the cycle results. The team then has three documented options: test it manually in this cycle, write a new automated test, or formally accept the risk and document that decision. Nothing is silently skipped.

Can we carry untested items forward from a previous cycle?

Yes. When creating a new cycle, choose Carry Over instead of Start Clean. Carry Over inherits every untested item from the previous cycle, so teams pick up exactly where they left off without losing prior gap context.

How does the "optimal" test set differ from the full "covering" test list?

The covering list includes every test that exercises at least one most-at-risk executable — but multiple tests may cover the same executable, creating redundancy. The optimal set is the mathematically smallest combination of tests that still guarantees every most-at-risk executable is covered at least once. Teams can choose to run the optimal set for maximum efficiency, or the full covering set for broader confidence.

Which SAP environments and release types are supported?

SeaLights supports SAP S/4HANA Cloud Private Edition, SAP S/4HANA Enterprise Management, and SAP ECC. Covered scenarios include S/4HANA upgrades, ECC-to-S/4HANA migrations, support packs, feature packs, custom releases, and third-party add-on upgrades.

How current is the coverage data during an active test cycle?

Coverage updates approximately every 15 minutes — including mid-cycle — eliminating the need to wait for a nightly refresh.