Oracle Integration Cloud: Building Integrations That Survive Production · Module 15 · Testing an integration properly
What "tested" means for an integration
Lesson 145 of 175 · 2 min
Not "it ran once". The FIVE things that must be demonstrated before anyone should sign for a flow. "It works" almost always means "I ran it with one good record and the record appeared." That is a necessary first step and it is roughly a fifth of the work, and every failure this course has catalogued lives in the other four fifths. ONE: THE HAPPY PATH, WITH REAL DATA SHAPES. A record goes in and the right record comes out — checked field by field in the target, not by the instance completing. An integration that completes and writes a wrong value is a worse outcome than one that fails. TWO: THE UNHAPPY DATA. Nulls, missing optional fields, maximum lengths, non-Latin characters, a record with forty child lines. Lesson 3, and it is the class that arrives in the first production hour. THREE: THE FAILURE PATHS. Every fault handler you…
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.