Playbook: Quarterly update regression testing

1. Four to six weeks before the test pod update, review the Readiness notes and list impacted features.
2. Refresh the test pod from production if data is stale (P2T).
3. Run the regression pack: critical end-to-end flows (record-to-report, procure-to-pay, order-to-cash, hire-to-retire, payroll), integrations, reports and personalisations.
4. Test opt-in features the client wants.
5. Log defects; raise Oracle SRs for product bugs.
6. Sign off before the production update weekend.
7. Smoke test production after the update.

Tip: automate the regression pack so each quarter takes days, not weeks.