Regression Testing Strategy for SAP Releases, Support Packs and Notes

Keep this: job aid

SAP regression strategy card

• Every transport, note and stack is a regression risk: retest the change, regress the rest.
• Tiers: smoke under an hour (every import), core one to two days (stacks, releases), extended one to two weeks (upgrades).
• Score tests: 3 × criticality + 2 × change + 2 × usage + 2 × defects + 1 × integration; criticality 5 always stays in core.
• Regression set per change = smoke + affected process tests (+ core if significant).
• Private cloud and on premise: base release every two years, stacks roughly every six months; the customer owns upgrade testing.
• Public Edition: upgrades in February and August, test system first, about three weeks to regress; hotfix collections in between.
• Notes: assess prerequisites, implement in DEV with SNOTE, transport, targeted regression plus smoke, then production smoke.
• Plan one calendar with SAP deliveries, monthly security patch day, business blackouts and named key users.
• Automate tests that run often on stable processes with deterministic data; start with smoke; budget maintenance.
• Sign-off states which tier ran, what was excluded and why, open defects and evidence.