11 / 18 · Module 14 — External Automated Testing of Mule Integrations · filtered: cheatsheet← prev⊞ allnext →
14.3Why response-only testing is insufficient
Suppose Mule responds:
{
"success": true
}
But due to a defect:
BillingState → Phone
Phone → BillingState
The API response may still look perfect.
So:
HTTP 200
does not prove:
Salesforce state is correct
For important flows, verify both.