Week 3 of 8
Write the test strategy
SAP programs inherit quality gates from SAP Activate. Oracle programs mostly inherit their partner’s method, and those vary. Oracle’s Success Navigator gives milestones and guidance, but not test levels or exit criteria. So write them down yourself, once.
The strategy must cover two lives: the implementation (or EBS migration), and the run phase after go-live, when a mandatory update lands every quarter and you have about two weeks to prove it.
This week: draft the strategy and get it signed
- Define test levels: configuration unit tests, process (string) tests, SIT with integrations, data load and reconciliation, security and roles, UAT, performance, cutover rehearsal, and quarterly update regression.
- Write numeric exit criteria. For example: 100% of critical scenarios executed, zero open severity 1 defects, severity 2 only with an approved workaround (example — set your own).
- Add a run-phase section: who reads What’s New, when impact analysis must be finished, which suite runs in the test pod, and who signs before production.
- Name your system of record for tests and defects, and how Oracle service requests are linked to defects.
- Get it signed by the program director, test manager and business sponsor.
Number of the week
2 weeks
between the test pod update (first Friday) and the production update (third Friday). Your regression exit criteria have to fit inside it.
Source: Oracle, Understanding Environment Maintenance (OCI documentation)Use this week
- EBS / JDE to Fusion Migration Test Plan (Word) →
Test levels, entry and exit criteria and the run-phase regression plan, written for Fusion.
- Testing Risk Register →
Record the risks that set test depth, with owners and mitigations.
Next week: a strategy needs scope. We build the process library that tells you what to test, and what changes coming from EBS.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.