Test Effective Development - End 2 (What) End?
summary
Claim: automated developer end-to-end smoke tests give the highest ROI by catching critical assembly and config failures with minimal test count. Strategy: write one 3am main path for the absolute critical user journey and a few longer 8pm root-feature multi-action tests per top-level menu. Tools recommended: Cypress IO or testimio (example: same flow took ~20 minutes in Cypress vs ~20 seconds in Testim). Result: fewer fragile tests, faster feedback, cheaper bug fixes.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:19Agenda
- 0:32Who am I
- 1:41What we do
- 2:20Test Right Sleep Tight
- 2:52Disclaimer
- 4:02Cost Effective Testing
- 4:26The Circle of Doom
- 8:09What Can Counter Unexpected Bugs
- 8:24A New Approach
- 9:34Be Specific
- 10:07Test Effective Development
- 10:37Where Do Bugs Hide
- 14:57Solution
- 15:09Benefits
- 15:28Downsides
- 17:22Smoke Tests
- 18:24Few Happy Critical
- 18:45Bug Taxonomy
- 19:08Main Critical User Journey
- 19:46Root Features User Journeys
- 21:36MultiAction Tests
- 22:25Tools
- 24:53Smoke Test Benefits
- 25:40Summary
- 25:53Free Quiz
related talks
27mThe Effective Development - End (What) End
22mTest Effective Development
41mEnd-2-end testing without the pain
56mThe End Game
20mPanel Discussion on Testing
58mTesting Strategy - New Model, Better Outcomes
46mSoftware Devs in Test Automation - Dream or Reality in Agile Software Dev?
01h 05mMicrotesting