Life after go-live: S/4HANA upgrade cadence, clean core and a regression strategy that keeps up

The go-live is the moment everyone plans for. The upgrade calendar is what you actually live with. On S/4HANA in the cloud, especially under RISE, that calendar is set by SAP, and the regression testing that goes with it is set by you. This guide is about building a regression practice that keeps up without consuming the team.

The cadence you are signing up for

S/4HANA Cloud Private Edition ships a base release every other year, with Feature Pack Stacks and Support Pack Stacks every six months. Mainstream maintenance lasts seven years per base release, and customers must take at least one upgrade every seven years to stay in it^[1]. Public Edition upgrades twice a year (for example 2502 and 2508), plus smaller monthly updates, and customers cannot defer them^[2].

Under RISE, SAP executes the technical upgrade; planning, preparation and testing stay with the customer or partner^[1],[7]. Six-monthly regression with a manual suite that takes six weeks leaves almost no quiet time in the year. That arithmetic is why automation stops being optional after go-live.

Use clean core levels to decide what to test

SAP grades extensions on four clean core levels: A uses only released APIs; B adds classic APIs that are generally upgrade-stable; C reaches into internal objects; D is not recommended and carries the highest risk^[3]. That is a ready-made risk model for regression:

• Level A: covered by your critical end-to-end suite; no dedicated tests per upgrade.
• Level B: in the suite, and reviewed when the upgrade notes mention the APIs involved.
• Level C: dedicated tests in every cycle, checked against SAP’s changelog for internal objects.
• Level D: dedicated tests in every cycle and a plan to remediate. Every upgrade is a risk event.

Tooling: Cloud ALM, automation and test content

SAP Cloud ALM provides test management for manual and automated tests in one place. For Public Edition it integrates SAP’s Test Automation Tool; for Private Edition, automated tests run against your QA system through integrated automation tools^[4]. SAP has also said it is bringing its own internal test content to Cloud ALM for release regression testing^[5]. SAP’s own automation offer, SAP Enterprise Continuous Testing by Tricentis, was rebuilt as a cloud-native, Cloud ALM-integrated service in May 2026, with AI-generated test cases paid for in SAP AI units^[6]. Independent tools integrate too; evaluate on your own processes before you commit.

A regression practice that keeps up

Measure three things per release: critical process coverage, regression cycle time and escaped defects. If cycle time is not falling release over release, the suite is not keeping up. For what to automate first, see this guide.