Multi-org integrations: data flowing between separate Salesforce orgs.
Test scenarios:
- Outbound from Source org: change in Source triggers sync to Target.
- Inbound to Target org: data arrives correctly.
- Identity federation: SSO works across orgs.
- Consistency: same data eventually in both.
- Conflict resolution: simultaneous updates handled.
- Failure modes: source down, target down, network issue.
Setup:
- Test sandbox per org.
- Same identity / SSO setup.
- Test integration backbone (Mulesoft) configured.
Approach:
- Trigger source change.
- Verify event published.
- Verify Mulesoft processes.
- Verify target updates.
- Check timing (eventual consistency).
- Check edge cases.
Tools:
- Postman for API tests.
- Apex tests on each side.
- End-to-end with manual coordination.
Common pitfalls:
- Testing one direction only.
- No conflict tests.
- Network resilience untested.
Senior insight: cross-org tests require multi-org coordination. More complex than single-org.
The senior framing: multi-org architectures need multi-org testing.