Oracle Updates Four Times A Year. You Get Two Weeks To Prove Nothing Broke.
AI agents that test Fusion Cloud and E-Business Suite by intent instead of selectors — so a quarterly update, a Redwood reskin, or a changed element ID stops eating the two weeks you have between your test pod and production.
26A
Redwood conversion and AI agents begin
26B
Payment governance, OIC expansion
26C
Largest 2026 release · current
26D
Next quarterly update
Four Updates A Year. Two Weeks Each To Prove Nothing Broke.
Oracle sets the calendar and you cannot opt out of it. The window between your test pod updating and production updating is the whole of your regression cycle.
Four Updates A Year, Two Weeks To Test
Oracle updates test environments on the first Friday of the update month and production on the third. That two-week gap is your entire regression window, and it repeats four times a year — 26A, 26B, 26C, 26D.
Redwood Is Rewriting The Interface
The Redwood migration is the defining change of the 2026 cycle: independent trackers flagged roughly 60% of 26C features as Redwood. Every reskinned page is a fresh set of element IDs for selector-based scripts to lose.
Processes That Cross Every Module
Procure-to-pay, order-to-cash and record-to-report don't sit in one module. A single flow touches Payables, Receivables, GL, Procurement and SCM — then leaves through OIC, FBDI and HDL loaders, and REST and SOAP services on their own release schedules.
Two Estates, One QA Team
E-Business Suite is not going anywhere: Oracle extended 12.2 Premier Support to at least 2037 in March 2026, the ninth annual extension, with quarterly Critical Patch Updates continuing. Most teams are testing Fusion and EBS side by side, indefinitely.
Tests That Describe Intent, Not Selectors
TestZeus agents read your Oracle pages the way a functional consultant does. Nothing points at an element ID, so a Redwood reskin has nothing to break — and the journey does not stop where Fusion ends.
Three Things Generic Test Automation Cannot Do In Oracle
Redwood-Proof By Architecture, Not By Repair
Self-healing repairs a broken selector after it breaks. TestZeus agents never bind to one. A flow described as "enter an invoice, validate it, and run the payment batch" survives the Redwood reskin, the quarterly update, and the classic-to-Redwood profile switch — because nothing in it points at an element ID.
One Journey Across Fusion, EBS And The Integrations
A business process rarely stops at the application boundary. TestZeus agents follow procure-to-pay from requisition to payment, assert on the REST and SOAP calls underneath, check the FBDI or HDL load landed, and confirm the notification email — in one test, across Fusion and EBS.
Evidence Your Auditors Will Accept
Quarterly updates in a SOX-scoped Financials tenant need more than a green tick. Every TestZeus run captures video and network logs and emits JUnit reports, so the artefact your control owner needs is a by-product of testing rather than a separate documentation exercise.
Into Your Pods, Out To Your Pipeline
Agents run against the test pod the moment it updates, follow the process into OIC, the file loaders and the API layer, and report into your pipeline — with video and network logs captured on every run.
Manual UAT, Scripts, Or Agents
| Manual UAT | Selector-based scripts | TestZeus agents | |
|---|---|---|---|
| Fits a two-week window | Rarely | If nothing broke | Yes |
| Survives a Redwood reskin | Yes, slowly | Needs repair | No selectors to break |
| Cross-module P2P and O2C | Manual handoffs | Brittle | One journey |
| Fusion and EBS together | Two teams | Two suites | One suite |
| Audit evidence | Screenshots by hand | Varies | Video, logs, JUnit |
| Cost per quarter | Repeats in full | Repair then run | Run |
See It Run On Your Own Instance
Bring one workflow that breaks every release. We will build it as an agent test and run it against your upgrade preview instance.
Frequently Asked Questions
Oracle Fusion Cloud Applications update quarterly — 26A, 26B, 26C and 26D in 2026. Within each quarter, test environments update on the first Friday of the update month and production follows two weeks later on the third Friday. Which month you get depends on your cohort: for 26C, Cohort A test environments updated on 7 August 2026 with production on 21 August, Cohort B in September and Cohort C in October.
About two weeks. The gap between your test environment updating on the first Friday and production updating on the third Friday is the whole regression window. Oracle publishes readiness content — What's New, Feature Summary and the weekly Feature Listing — ahead of that, so most teams get roughly a month of planning lead time but only a fortnight of hands-on validation against the new code.
No. Fusion Cloud updates are applied on Oracle's schedule, and your cohort determines when rather than whether. This is the structural difference from on-premises ERP: there is no option to stay on a prior release while you catch up, so regression testing has to fit the calendar instead of the calendar fitting your testing.
Redwood rebuilds pages on Oracle's current design system, which changes the underlying markup and the element identifiers that scripted tests target. It is the defining theme of the 2026 releases — independent trackers flagged around 60% of 26C features as Redwood. Because many Redwood pages are controlled by a profile option, teams often run classic and Redwood versions of the same page in parallel, which doubles the surface a selector-based suite has to cover.
Yes. Oracle extended Premier Support for E-Business Suite 12.2 through at least 2037, announced on 25 March 2026 — the ninth consecutive annual extension since the Continuous Innovation model began in June 2018. That is full Premier Support, including regulatory updates, certifications and quarterly Critical Patch Updates. Any plan that assumes EBS is about to go dark is working from an out-of-date slide.
Enough that reading the full list is not a plan. For 26C, independent trackers published counts ranging from roughly 600 to over 900 feature changes, depending on their counting method — Oracle does not publish a single canonical total. Treat those figures as directional evidence of scale and use Oracle's own readiness pages for the module-by-module detail that applies to your configuration.
With TestZeus, yes. A single test can raise a requisition in Fusion, assert on the REST or SOAP call that carries it onward, confirm an FBDI or HDL load landed, and check the resulting notification email. This matters in Oracle estates because integrations such as OIC run on release schedules independent of the Fusion quarterly cycle, so the seams between systems are exactly where quarterly updates tend to surface problems.
No. TestZeus tests are written in plain English and executed by AI agents that work from intent rather than scripted selectors. That matters more in Oracle than in most estates, because the people who know whether a payment run is correct are finance and functional consultants, not automation engineers — and a plain-English suite is one they can review and sign off themselves.
Stop Rebuilding Your Suite Every Quarter
26D lands in Q4. Be ready before your test pod updates, not after.
