Sensitivity, Precision, and When to Test in Prod
summary
Argues for choosing tests by the value they buy: Assistments runs end‑to‑end Cypress tests across dev, test and run full suite against production to catch environment‑specific misconfigurations that CI misses, measured as saved person‑minutes per release; cuddle.cards keeps fast contributor onboarding by using mock database and Redis so tests are easy to seed and run in CI. Shows a real bug where a last‑card Jack plus a seven locks the game, fixes it with a Cypress fixture and the test immediately prevents regressions.
AI-written summary · about
chapters (10)
- 0:00Introduction to testing
- 1:06Speaker background
- 2:26Defining testing value
- 3:53Architecture and risk
- 5:58Data science risk framework
- 7:34Case study: Assistments
- 14:37Case study: Cuddle
- 17:10Mocking and trade-offs
- 21:40Testing demo and bug fix
- 26:55Conclusion
related talks
20mIntegration Testing with Cypress
13mDon't Get Lost in the Trees: An Intro to Cypress
35mSleeping better at night
35mCypress Tales: Effective E2E Testing
56mCypress: Where Automated Acceptance Testing Isn’t Just for QA Anymore
31mHow Simple Cypress Tests Recouped Thousands of Company Dollars
38mFrontend Tests: what nobody said to you
22mIncreasing our test stability and reliability with Cypress