Lesson 6 of 6
Reworking your test library
7 min
Most ECC customers have a library of test cases built over years: regression scripts, user acceptance tests, key-user checklists. Moving to SAP S/4HANA does not make that library worthless, but it does not survive untouched either. Some tests still work, some need changes, some are obsolete, and some new tests are needed for things ECC never had.
Classify every test
| Category | Meaning | Contoso example |
|---|---|---|
| Still valid | Process, steps and expected results are unchanged | Create a standard sales order with VA01 and check the price |
| Needs change | Same business goal, but steps, transactions, data or expected results differ | Create a customer: XD01 steps become BP with roles; vendor tests likewise |
| Obsolete | The function no longer exists or is replaced entirely | FI-CO reconciliation ledger checks; KA01 cost element creation |
| New | A new function, mandatory feature or check that ECC tests never covered | Business partner role completeness; credit release in SAP Credit Management; material ledger values |
Four categories for an existing test library.
A simple impact tag
Link every test that needs change, is obsolete or is new to the simplification item that caused it. A short tag, such as SI: Business Partner or SI: Credit Management, makes the library searchable and lets you answer two questions quickly: which tests must be updated for this item, and which items still have no test coverage.
- InventoryExport the current test library with process area and transactions used
- MatchCompare each test with the relevant simplification items for that area
- ClassifyStill valid, needs change, obsolete or new
- TagAdd the simplification item tag to every affected test
- ReworkUpdate steps, data and expected results; retire obsolete tests; write new ones
- ProveRun the reworked library in the converted test system before sign-off
Where expected results change
The trickiest tests are the ones whose steps still work but whose expected results change. A goods receipt test may run perfectly, but the journal entry now sits in the Universal Journal with additional attributes, and material ledger fields appear. A billing test may pass, but the invoice form now comes from the new output management. A test that only checks "document saved" will pass and miss these differences. Update the expected results, not just the steps.
- Transactions: replace obsolete transaction codes (XD01, XK01, MB1A, KA01) with their successors (BP, MIGO, FS00).
- Master data: test data now uses business partners with roles; update data sheets.
- Expected postings: check journal entries for profit center, segment and market segment attributes.
- Outputs: update expected forms and channels for output management.
- Roles: run tests with the new business roles and Fiori apps where users will work there.
- Does the business process still exist in SAP S/4HANA?Yes → continue · No → obsolete; record the replacing item
- Are the steps and transactions the same?Yes → continue · No → needs change; update steps
- Are the expected results the same (postings, outputs, statuses)?Yes → still valid; rerun to confirm · No → needs change; update expected results
- Is there a new function or mandatory feature with no test?Yes → write a new test and tag it · No → coverage complete for this area
Do not forget non-functional checks
Business test libraries tend to focus on functional steps. A conversion also changes performance characteristics, authorizations and interfaces. Long-running reports may become much faster, while some custom programs may slow down until they are optimized. Business roles are often redesigned around Fiori apps, so a user who could do everything in ECC may find a gap in the new role. Interfaces to banks, tax engines, carriers and EDI partners carry business documents and must be tested end to end. Add a small set of tests for each of these to the reworked library.
What would you do?
Contoso's regression suite has 600 ECC tests. The program wants to save time by running them all unchanged in the converted system and fixing whatever fails. What is the risk?
- Classify each ECC test as still valid, needs change, obsolete or new.
- Tag affected tests with the simplification item that caused the change.
- Update expected results, not just steps: postings, outputs and statuses change.
- Sign off only when every relevant simplification item is covered by a passing test.
Check your understanding · not graded
Lesson check
1. How would you classify an ECC test for creating a vendor with XK01?
2. What is the purpose of tagging tests with a simplification item?
3. A test checking the FI-CO reconciliation ledger should be classified as:
4. Why can an unchanged ECC test pass in SAP S/4HANA and still miss a defect?