Cross-cloud workflow: Marketing Cloud → Sales Cloud → Service Cloud → Field Service.
Example: Customer responds to marketing email → Pardot creates Lead → converts to Opportunity → won → Service Cloud onboarding → Field Service installation.
Test scenarios:
Per cloud:
- Pardot: form submission → Prospect → Lead.
- Sales: Lead → Opportunity → Closed Won.
- Service: Opportunity → onboarding Case.
- Field Service: Case → Work Order → completed.
Cross-cloud handoffs:
- Lead converts → Opportunity (Sales) → Account/Contact updates.
- Closed Won → Service Cloud created Case automatically?
- Onboarding Case complete → Work Order in Field Service.
Data flow validation:
- Customer info propagates across.
- No data loss.
- Consistent.
Test approach:
- End-to-end manual: walk through scenarios.
- Automated end-to-end: Provar / Selenium across clouds.
- API tests: programmatic verification.
- Per-cloud tests: isolation.
Multi-environment:
- All clouds in test environment.
- All clouds in production.
- Sync between sandboxes can be tricky.
Common pitfalls:
- Each cloud tested in isolation — handoffs missed.
- Inconsistent test data across clouds.
- Timing issues in async handoffs.
Senior QA insight: cross-cloud tests reveal architectural seams. Often the most-bug-prone areas.
The senior framing: integration is where bugs hide.