MSAMM
Back to course

Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 17 · Release readiness: quarterly updates and regression

Testing in the update window

Lesson 167 of 177 · 2 min

The sequence across environments is what makes this possible at all: TEST IS UPDATED FIRST, production follows. The gap between them is the entire opportunity. How much time you actually get is less than the calendar suggests. Part of the window is a weekend, part of it is people who are not available, and the update itself takes some of it. Plan on having a fraction of the nominal gap, and that is why Lesson 3 insists the pack must be executable in that fraction. The order to test in is the ranking from Lesson 2: reports first, personalisations next, then integrations. Run the highest-consequence tests on the first day the environment is available, not the most convenient ones, because a defect found on day one has options and one found on the last day does not. WHAT TO DO WHEN A DEFECT APPEARS WITH DAYS TO GO. There are…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 17 · Release readiness: quarterly updates and regression

  1. 1Reading an update for riskFree preview
  2. 2What is exposed, and what is safe
  3. 3Building a regression pack that stays useful
  4. 4Testing in the update window
  5. 5New features: opting in deliberately
  6. 6Communicating an update to the business
  7. 7What breaks: after the update landed
  8. 8Lab briefing · Assess a real release note