Testing in Production
summary
Claims that testing in production with feature flags and automation reduces bugs and speeds releases are supported by concrete tooling and workflow: use Split or LaunchDarkly to target a small set of internal users, run Robot Framework/Puppeteer/Jest/Protractor suites on Jenkins or Circle CI on a schedule, alert failures via PagerDuty or Slack, and deploy with a production canary rollout. Create predictable test user naming and hard‑coded test‑entity isolation; outcome is higher confidence, fewer post‑release fixes, and faster developer velocity.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:05What is testing in production
- 2:30Introduction
- 3:52Problems with staging environments
- 7:35Risks
- 8:30Feature Flagging
- 10:05Split Feature Flag
- 11:45Automation Framework
- 13:12Testing Tools
- 14:48Test Entities
- 16:00Write Your Test
- 17:51Canaries
- 20:39Nonproduction tests
