MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 15 · Testing an integration properly

End-to-end with the business

Lesson 150 of 175 · 2 min

The test where A PERSON DOES SOMETHING REAL and confirms the result IN THEIR OWN SYSTEM. What only this catches. Every test so far has been yours: you supplied the input, you checked the target, and you were the one who decided what correct means. This one is different in exactly that respect — somebody from the business performs their real task in the source system, and then looks in the destination system for the result they expected. WHAT ONLY THIS CATCHES IS THE GAP BETWEEN WHAT YOU BUILT AND WHAT THEY MEANT. The integration works perfectly against the specification and the specification was a reading of a requirement written in a workshop three months ago. Nothing in a technical test can find a mapping that is correct and wrong — the right field populated with the wrong meaning, a status that maps to something the business would never call

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 15 · Testing an integration properly

  1. 1What "tested" means for an integration
  2. 2Testing without the other systemFree preview
  3. 3Choosing test data that would fail
  4. 4Testing the failure paths
  5. 5Testing idempotency explicitly
  6. 6End-to-end with the business
  7. 7What breaks: the UAT that proved nothing
  8. 8Lab briefing · A test plan somebody would sign