Sandboxes serve different testing purposes; strategy matters.
Tier strategy:
- Developer sandboxes: per-developer; rapid iteration; daily refresh.
- Integration: shared by team; weekly refresh.
- UAT: business user testing; less frequent refresh during UAT.
- Performance / staging: Full Sandbox; mirrors production.
- Hotfix: dedicated for emergency fixes.
Refresh discipline:
- Refreshing destroys in-flight work.
- Coordinate; communicate.
- Pre-refresh: export anything to preserve.
- Post-refresh: redeploy any custom data.
Source-control alignment:
- Each sandbox = a Git branch.
- Deploy from Git via CLI / DevOps platform.
- Avoid editing in sandbox UI; commit first.
Test data per sandbox:
- Dev: minimal sample data.
- Integration: test data factories.
- UAT: anonymised production-like.
- Performance: synthetic high-volume.
- Staging: production-mirror.
Cost considerations:
- Full Sandbox is expensive.
- Plan budget; right-size.
- Don't over-provision; don't under-provision.
Common pitfalls:
- One shared sandbox — collisions.
- Refreshing during testing — destroys progress.
- No test data strategy.
Senior insight: sandbox strategy is QA infrastructure. Plan deliberately.
The senior framing: right environment for right test type. Don't test in wrong sandbox.