Testing in Production
summary
Feature flags separate code deployment from release so code ships to production behind a toggle and is verified via three automated tests: flag on, flag off, and a full-flow validation that fakes flag state. Tests run in prod against objects marked is_test=true; canary rollouts and AA comparisons limit blast radius. Database migrations use the expand-contract pattern to stay backward compatible. Recommended tools: Split for flags, Robot Framework or Cypress for automation, CI schedulers (Jenkins/CircleCI) and PagerDuty for alerts.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:26Problems with staging
- 6:41Testing in production
- 8:24Feature flags explained
- 10:31Automating tests in prod
- 14:01Handling third-party integrations
- 15:45Database migrations safely
- 17:30Tools for testing in prod
- 19:57Overcoming fear of testing
- 23:12Benefits of testing in prod
- 25:59Why testing in prod matters
- 27:22Key takeaways
- 28:26Q&A session
