Test pods update on the first Friday of the release month, production two weeks later - with SCM's mandatory Redwood UI transition landing in Q4 2026, and Oracle Integration Cloud on a separate quarterly clock of its own underneath it all. We validate Financials, Procurement, Supply Chain and HCM before every one of them reaches production - starting with a QA Health Check, then scaling into automation build and ongoing coverage as your environment needs it.
DEV and PROD environments diverge silently.
A lookup value or approval rule added in test never makes it to production - surfacing weeks later as a failed month-end close.
Reports, Interfaces, Conversions and Extensions weren't validated against the release.
Custom RICE components are the least-tested layer in most Oracle environments - and the first to break silently when a quarterly update ships.
Oracle Integration Cloud runs its own release calendar, and its own update windows.
OIC moved to a quarterly cycle of its own in January 2026, numbered separately from Fusion's A/B/C/D letters. A Fusion update can change behaviour your integrations depend on with no corresponding OIC release to explain it - and no single calendar shows you both.
Custom report templates and data models shift under an update.
Bursting schedules, data models and output formatting can break silently - finance finds out when the board report is wrong.
Page Composer customizations don't survive Redwood conversion.
Sandbox personalizations and FlexFields built on Classic UI don't automatically carry over - SCM's mandatory transition lands in Q4 2026.
Duty roles or data security policies shift after a configuration change.
Segregation-of-duties violations can slip through silently - a compliance issue, not just a testing one.
Even small changes can cascade into major operational risks if not tested thoroughly.
None of these are hypothetical. Each one shortens the warning you get before an update reaches production - and raises the cost of finding out about a regression from your finance team instead of from us.
Oracle's phased Redwood UI migration reaches its next hard deadline: Supply Chain Management modules must complete the transition by the 26D release. Personalizations and page customizations built on the Classic UI don't carry over automatically.
Test pods update on the first Friday of the release month; production follows exactly two weeks later, on the third Friday. There's no opt-out and no extension - whatever hasn't been tested by then goes live anyway.
Oracle Integration Cloud moved to its own quarterly cycle in January 2026, under its own numbering rather than Fusion's A/B/C/D letters. Inside that cycle, instances are assigned to one of two update windows two weeks apart - and changing which window you sit in takes seven weeks or more to take effect. Teams that never set it have non-production and production updating together, which leaves no gap to catch a broken integration in.
Select a process to see how we validate it end to end, every release.
26C's Feature Listing passed 900 changes, close to 60% of them carrying Oracle's Redwood flag and SCM taking the largest share. 26D lands on top of all of it - and it's the release where Redwood stops being optional for Supply Chain. Our test library spans the modules enterprises actually run: standard flows out of the box, plus the custom RICE components, OIC integrations and Page Composer personalizations we build coverage for during onboarding.
Don't see your workflow? We build custom test coverage for client-specific RICE components, OIC integrations and Page Composer personalizations during onboarding - never a reason to wait.
Deliverable: A prioritized QA roadmap with specific recommendations for your Oracle Fusion environment.
Deliverable: Working automation suite with reusable test assets and regression framework.
Deliverable: Monthly regression reports and update-readiness assessments.
How this scales. Most engagements start with a QA Health Check, move into a scoped Automation & Functional QA Enablement build, then step into Continuous QA Enablement for ongoing release and service-update coverage - drawing on our pre-built Oracle Fusion test asset library at every stage to cut build time.
Your environment, your data. Every engagement - starting with the QA Health Check - begins under a signed NDA, with access scoped strictly to what the engagement requires. Backed by our ISO/IEC 27001-certified information security practices.
We inventory your Oracle Fusion environment - RICE customizations, OIC integrations and existing test coverage against the quarterly release calendar - the input for your prioritized roadmap.
We build pre-built and custom Oracle Fusion test assets for your specific configuration, and set up the Opkey automation framework.
Full regression each quarterly release, RICE and OIC integration validation, Redwood UI transition checks - run through Opkey, with a go/no-go readiness report every cycle.
Rather than pad this out, here is the Oracle engagement we have published in full. Oracle Fusion case studies are in preparation and will be added as they are cleared.
A heavily customised EBS implementation with insufficient checkpoints - every upgrade caused production issues, and limited testing windows meant the client could not thoroughly validate changes before go-live.
Complete ownership of verification and validation for the EBS-based portal across web and mobile - manual testing of critical UAT flows plus a purpose-built automation framework covering 70% of the regression suite. Execution time dropped by two weeks in the first cycle and three in subsequent cycles.
Fusion engagements are underway. Case studies will be published here as each client clears them for release. Need a reference before then? Ask — we will tell you what we can share and what we cannot.
Oracle's Regression Testing Program for EPM builds scripts tied to a single business process and hands you the results - it doesn't cover RICE customizations, OIC integrations, or cross-module Fusion flows. Our assets are built and maintained by test engineers, cover your custom layer by design, and aren't limited to what Oracle itself is willing to script for you.
The QA Health Check is a free, 1-2 week environment review that ends in a prioritized QA roadmap. Automation & Functional QA Enablement (4-8 weeks) is where we build the actual working automation suite and reusable test assets. Continuous QA Enablement is the ongoing monthly engagement that keeps that suite running against every quarterly release, with monthly regression reports and update-readiness assessments.
Both. Our pre-built assets cover standard flows out of the box; we build and maintain coverage for your client-specific RICE components, BI Publisher reports, Page Composer personalizations and OIC integrations during the Automation & Functional QA Enablement stage.
We scope regression coverage to fit inside Oracle's fixed window - full regression on the processes that matter most (close cycle, procure-to-pay, custom integrations), targeted regression everywhere else, so you're never starting from zero when the test pod updates.
Yes — as functionality, not as magic. Oracle's AI features sit inside business processes you already depend on: forecasting, anomaly detection, document recognition. We validate the process outcome the same way we validate any other release change, and we flag AI-driven behaviour that has changed between releases so a finance or HR owner can decide whether it is acceptable. Where a feature's output is not deterministic, we test the guardrails around it rather than pretending a fixed expected result exists.
With a QA Health Check - free, typically 1-2 weeks, ending in a prioritized roadmap for your Oracle Fusion environment. From there, most clients move into Automation & Functional QA Enablement, then Continuous QA Enablement for ongoing coverage.
Our specialists review your environment and identify the highest-risk gaps across Financials, Procurement, Supply Chain and HCM - before the next quarterly update reaches production.