Testing implications and choosing an option

Each deployment option creates a different regression demand: how often the system changes underneath you, how much of it you own, and how much time you get to prove it still works. This lesson turns the earlier dimensions into a test planning view and closes with a way to recommend an option for a scenario.

Regression demand by option

In the public edition, regression is frequent and fixed: two major upgrades a year, each with a test window of about three weeks, plus continuous feature delivery. You cannot postpone it, so the answer is automation. SAP recommends its Test Automation Tool for the public edition, and the Release Assessment and Scope Dependency tool and the What's New Viewer help identify which changes affect your scope.

In the private edition and on-premise, regression is less frequent but larger, and its timing is yours: each feature pack or support pack stack, each base release upgrade, and every one of your own releases. The risk shifts from "not enough time" to "too much change at once", especially when custom code at levels C and D must be retested. On-premise adds technical changes you run yourself, such as operating system and database updates, which also need at least a technical smoke test.

Automation matters in the private edition too, just for a different reason. A regression set that runs only every year or two decays: test data expires, users change and nobody remembers the steps. Contoso plans to keep its key process tests in SAP Cloud ALM, run a small automated core set after every transport cycle so it stays alive, and expand to the full set for stacks and upgrades. Kenji's team adds ABAP Unit tests to the custom code it keeps, so the core return agreements logic is checked every time it changes rather than only at upgrade time.

What stays the same everywhere

• The customer always tests and accepts. No option moves business sign-off to SAP.
• A risk-based regression set built from your processes, not SAP's whole scope, is the core asset.
• Integrations and extensions are the most fragile parts and deserve contract tests.
• Evidence must be stored where auditors can find it, in SAP Cloud ALM or your test management tool.

Recommending an option

Contoso's main program answered the first question with "yes", so it converted to the private edition. Wave 2 raised the question again: after the conversion Contoso acquires Alternadores del Norte S.A. de C.V. in Monterrey. The team considered a two-tier setup with a public edition system for the subsidiary, then chose to load Alternadores' legacy data into the converted system as company code 1910, so that intercompany flows and reporting stay in one system. Either answer could be right; what matters is that the option was compared on the same five dimensions.