MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 17 · Quarterly updates and OIC

Testing in the update window

Lesson 167 of 175 · 3 min

The ORDER across environments, how much TIME you get, and what to do when a defect appears WITH TWO DAYS LEFT. Updates arrive on a schedule you do not set, and non-production environments are updated before production. That gap is the entire opportunity: it is the only window in which a problem can be found before it is in front of a client. SO THE ORDER IS FIXED AND THE FIRST STEP IS THE ONE PEOPLE SKIP. The moment the test instance is updated, run the regression pack there. Not at the end of the window when there is time — at the start, because everything you can do about a defect depends on how many days remain when you find it. THE WINDOW IS SHORTER THAN IT LOOKS. A published gap of a fortnight is reduced by the days before anybody notices the update landed, the days the pack

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.

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 · Quarterly updates and OIC

  1. 1Two update calendars, not one
  2. 2Reading an OIC release note for risk
  3. 3Adapter versions and regeneration
  4. 4A regression pack for integrations
  5. 5Testing in the update window
  6. 6What breaks: after the update
  7. 7Lab briefing · Assess a real release note