SeaLights for ABAP: Mapping SAP Risk and Closing Test Gaps
Pair SAP change tracking with automatic test mapping to know exactly what a transport touches, and what still needs coverage. In this walkthrough, Kateryna Serdinsky, Product Marketing Manager at Tricentis, demonstrates how to set up a test cycle, run risk-based impact analysis, and close coverage gaps in SeaLights for ABAP.
SAP teams test, but most can’t say with confidence what a given transport actually touched or whether it was covered. Kateryna walks through creating a test cycle, scoping it to a landscape and transport range, and reviewing the resulting risk analysis. You’ll also see how the coverage view flags the exact objects that were never tested, broken down by app area.
Highlights:
- Test what's at risk, not everything: in Kateryna's example, testing every executable means around 3,000 objects, tracing dependencies gets you to 2,000, and risk-based testing narrows it to around 400, an 85% reduction
- Works from day zero, before a single test run, by mapping SAP executables to ABAP objects to tests in your repository, including Tosca, qTest, and Excel
- Scope each test cycle by landscape, system, test repository, and a single transport, multiple transports, or a date range, or carry over a previous cycle
- Risk analysis shows impacted and most at risk executables, with a downloadable Excel report of the details
- Run recommended tests manually in qTest or automatically through a Tosca playlist
- Coverage analysis calls out the specific objects your tests missed, organized by app area
Learn more: https://bit.ly/4yJkuB8