UAT environment and test data readiness
Key Takeaway
Run UAT in a sandbox that matches production, pick a Partial Copy or Full Copy sandbox based on what the testing needs, and limit who can reach copied production data.
In user acceptance testing (UAT), end users test a project, such as an Agentforce Manufacturing rollout, in a sandbox or other test environment just before go-live, to confirm that it delivers what the business asked for. Getting the UAT environment and its test data ready is part of UAT prep. A sandbox that drifts from production or holds unrealistic data lets testers sign off while problems still appear after go-live.
What UAT is and where it fits
UAT checks that a project or enhancement works as intended. UAT comes after the technology team's own quality testing, as the last stage before go-live. Each test case ends in pass or fail. The overall result acts as a go or no-go decision for production.
A sandbox is an isolated copy of production, so testers get a risk-free place to work. A sandbox can hold a replica of production data, which means testing is realistic without touching business-critical processes and data.
Changes should follow a set promotion path, with validation at each stage:
- Development
- Integration
- UAT
- Production
Changes that pass all automated checks deploy to the UAT environment for business validation. They move to production only after UAT approval.