The Effective Development - End (What) End
summary
Title claim: automated smoke tests covering a few critical journeys give the best ROI for developer end-to-end work. Concrete strategy: write a single 3am main critical user journey plus a small set of 8pm root-feature multi-action tests, run them during development to catch assembly/configuration bugs. Tools mentioned: Cypress and Testim (Testim turns a 20‑minute manual script into ~20 seconds). Example pain: 50 tests broke and cost minutes; smoke suite stays small, faster, less fragile, and cheaper to maintain.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 4:15The challenges of testing
- 10:48Debugging and test gaps
- 15:09Automated E2E testing
- 17:35Understanding smoke tests
- 22:40Tools and summary
related talks
27mTest Effective Development - End 2 (What) End?
41mEnd-2-end testing without the pain
56mThe End Game
22mTest Effective Development
58mTesting Strategy - New Model, Better Outcomes
20mPanel Discussion on Testing
16mEnd the Test Engineer role: how cross functionality leads to a better engineering
42mEffective Developer Testing: taking it to the next level