SAP S/4HANA Test Scenario Tracker
Testing is where most S/4HANA programs discover their real status. This tracker keeps execution, pass rate and critical defects per process area visible, without a heavy test tool.
| Scenario | Process area | Test phase | Planned cases | Executed | Passed | Failed | Pass rate | Execution progress | Open sev 1-2 defects | Lead tester | |
|---|---|---|---|---|---|---|---|---|---|---|---|
2 | 91.7% | 100% | |||||||||
3 | 88.5% | 86.7% | |||||||||
6 | 80% | 83.3% | |||||||||
2 | 80% | 55.6% | |||||||||
1 | 91.7% | 100% |
Set exit criteria before testing starts, for example 100 percent of critical scenarios executed, 95 percent pass rate and no open severity 1 or 2 defects. Counts here are by test case, so one scenario row can hold several cases.
Regression testing help
Learn how to compare legacy and S/4HANA outputs automatically for regression runs. Optional.
Optional. The tool and every export work without this. No spam.
How to use the tracker
Create one row per end-to-end scenario and test phase, with the planned number of cases. Testers update executed and passed counts daily. Failed cases, pass rate and execution progress calculate automatically. Add the number of open severity 1 and 2 defects from your defect tool. Export to Excel for the daily test stand-up.
- Update counts at the same time every day
- Track by end-to-end scenario, not by module
- Keep a separate row per test phase
- Link defect numbers in the exported file
Reading the numbers
Execution progress shows how much testing is done, and pass rate shows quality of what was executed. High pass rate with low execution is not good news, because the hard scenarios are often last. Watch process areas with failed cases plus open high-severity defects, as they hold up exit. Compare progress to plan each day to catch slippage early.
Test phases for S/4HANA
Typical programs run unit tests during build, then one or two rounds of integration testing, user acceptance testing and a regression round before cutover. Add performance and security tests, plus testing of interfaces, print forms and authorizations. Business users should run UAT using real master data and realistic volumes.
Common mistakes
Teams skip negative tests, use clean demo data, and test only the happy path. Others do not retest after defect fixes or transports. Define exit criteria upfront and do not lower them under date pressure without a documented decision.
Frequently Asked Questions
What are good exit criteria for SIT?
Common criteria are all critical scenarios executed, a pass rate of at least 95 percent, and no open severity 1 or 2 defects. Agree the exact thresholds in the test strategy before testing begins.
How is UAT different from SIT?
SIT checks that the integrated system works end to end, usually run by the project team. UAT is run by business users to confirm that the solution supports their real work.
Can I use this instead of a test management tool?
For small to mid-size programs, it can be enough. For hundreds of cases with traceability needs, use a test tool and keep this as a summary view.
Does it track individual defects?
No. It holds counts of open high-severity defects per area. Track detail in your defect tool.
Netray can help generate test data and compare outputs between legacy and new systems, so regression checks run faster and with less manual effort.
Related Tools
SAP Fit-to-Standard Workshop Log
Record each business process reviewed in fit-to-standard workshops, its fit rating, gap resolution and estimated effort. Exports to Excel.
SAPSAP Migration RAID Log Worksheet
Log risks, assumptions, issues and dependencies for an SAP migration with automatic risk scores. Exports to Excel.
SAPSAP Cutover Runbook Timing Worksheet
Build the hour-by-hour cutover runbook with task owners, durations and buffers, and total the business downtime. Exports to Excel.
SAPSAP S/4HANA Steering Committee Status Report Template
A one-page monthly status report for SAP S/4HANA steering committees: RAG by workstream, milestones, top risks and decisions needed.