#ABAP#ATC#Code Inspector

ATC: what it is and why it retires the Code Inspector

The ABAP Test Cockpit isn't a Code Inspector with a new badge. It's a quality engine wired into ADT, with governed exemptions and mass runs over packages and transports. No fluff.

May 25, 2026

#ABAP#ATC#CI

ATC in CI: don't let quality depend on anyone's memory

Background runs, the Result Browser and the quality gate on transport release turn the ATC into a continuous control. That's how you bring quality into the pipeline, not to the end of the sprint.

May 24, 2026

#ABAP#ATC#priorities

Reds, yellows and blues: prioritizing ATC findings without drowning

An ATC run with three thousand findings isn't information: it's noise. Priorities, grouping and a baseline turn that impossible list into a real work queue. With judgment, not brute force.

May 22, 2026

#ABAP#ATC#ABAP Cloud

The ATC as your ABAP Cloud readiness radar

Before migrating to ABAP Cloud, the ABAP_CLOUD_READINESS variant tells you exactly what of your code survives and what doesn't. It's the map that turns a blind migration into a plan.

May 20, 2026

#ABAP#ATC#exemptions

ATC in the flow: exemptions and pragmas without sweeping under the rug

Pragmas, pseudo-comments and exemptions are the three ways to tell the ATC a finding is intentional. Used well, they keep the flow clean. Used badly, they hide bombs. Here's the difference.

May 19, 2026

#ABAP#ATC#variants

Check variants and baseline: the ATC doesn't measure everyone the same

ABAP_CLOUD_DEVELOPMENT_DEFAULT, ABAP_CLOUD_READINESS, ABAP_CLOUD_DEVELOPMENT_PARTNER. Picking the variant and setting a baseline is what separates a useful ATC from a sea of warnings nobody reads.

May 16, 2026

← All posts