Quality Engineering for Clean Core

Keep this: job aid

Clean core quality card

• Record every extension's clean core level (A–D), criticality and owner.
• Weight upgrade regression by level and criticality; C and D need dependency analysis.
• On-stack: ABAP Unit with CDS and ABAP SQL test doubles; RAP via EML.
• Side-by-side: unit and cds.test service tests; mocks from real API definitions.
• Contract tests: specification check plus provider verification in QAS.
• Gate at transport release: ATC (block P1–P2) plus passing unit tests.
• Exemptions: approved, reasoned, owned, time-limited, reported.
• Rerun consumer contract tests when S/4HANA changes.
• Dashboard: levels trend, findings, coverage, contracts, actual upgrade effort.
• Remediate the critical few; retire unused code instead of testing it.