MSAMM
Back to course

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

A regression pack for integrations

Lesson 166 of 175 · 2 min

WHICH flows to re-run, with WHAT data, and how to keep the pack SMALL ENOUGH THAT SOMEBODY ACTUALLY RUNS IT. The size constraint is the design constraint, and stating it first is what makes this lesson practical. A regression pack covering thirty integrations takes two days, so it is skipped in the update window, so the estate has no regression testing at all. A pack of six flows that takes two hours gets run every quarter, and that is worth more than a thorough pack that is never executed. CHOOSE BY CONSEQUENCE, NOT BY COVERAGE. The flows that move money. The flows a partner depends on contractually. The flows whose failure is silent — per Module 13, those are the ones where a defect runs longest. An integration whose failure is loud and cheap does not need to be in the pack, because you will find out anyway, within the

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
A regression pack for integrations — Oracle Integration Cloud: Building Integrations That Survive Production — MSAMM