UAT Validation in Production
summary
UAT in production requires formal approvals and concrete safeguards: teams fill multiple forms, get security forum signoff and an information‑security manager approval, and must clear test data after use. One case uses live pensions data only after heavy compliance checks; another deploys an analytics feature to early adopters using ring-fenced licenses as a soft launch, which yields real insights. GDPR allows one-way anonymization for masked data. Never shorten test scope; quality is non‑negotiable.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:43Sarahs background
- 5:20Business change
- 7:50UAT
- 8:36User Experience
- 10:15Testing Quality
- 10:54Getting Program Managers Attention
- 11:25What could go wrong
- 12:09Testing without testing
- 12:41Reputation
- 13:15Risks
- 14:10Context
- 16:09Filling out forms
- 16:49Security Plan
- 17:48Business Secured
- 18:20Testing
- 19:53Testing Reports
- 22:06GDPR
- 23:50Takeaways
related talks
48mWhat is UAT and, more importantly, what it isn’t
22mUser Acceptance Testing (UAT),one of the most stressful stages of quality assurance
01mUAT, one of the most stressful stages of quality assurance
46mTesting With Production Data Is a Terrible Idea
34mTesting in Production
51mTesting in prod (without pain and humiliation)
36mDevising a Project Test Approach
31mTesting in Production