Oracle Integration Cloud: Building Integrations That Survive Production · Module 15 · Testing an integration properly
Lab briefing · A test plan somebody would sign
Lesson 152 of 175 · 3 min
Write and execute a plan for an existing flow covering data, failure, idempotency and volume — then have it REVIEWED AS IF IT WERE A DELIVERABLE. The review is the exercise. Anybody can execute a test plan they wrote; the discipline is writing one somebody else can read, disagree with, and sign. WRITE IT AS CASES, EACH WITH THREE PARTS: the input, the action, and the EXPECTED result stated before you run it. Writing the expectation first is what stops a test being retroactively satisfied by whatever happened — "a record appeared" is not the same claim as "a record appeared with these six fields carrying these values", and only the second can fail. COVER THE FOUR AREAS, AND KEEP THEM SEPARATE SO A GAP IS VISIBLE. Data: Lesson 3's list, one case each. Failure: one case per fault handler, each with the provocation named — if you cannot say…
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.
In this module: Module 15 · Testing an integration properly
- 1What "tested" means for an integration
- 2Testing without the other systemFree preview
- 3Choosing test data that would fail
- 4Testing the failure paths
- 5Testing idempotency explicitly
- 6End-to-end with the business
- 7What breaks: the UAT that proved nothing
- 8Lab briefing · A test plan somebody would sign