Chris Harbert: Building the Testing Pyramid
summary
Timeline: JUnit in 1997, Selenium in 2004 and the pyramid popularized by Mike Cohn; recommends classifying tests so you write two end-to-end tests for the password reset happy and sad paths, a few API-level integration tests, and many unit tests for validators using mocks. Unit tests run in about 50 milliseconds, integration tests hit real endpoints, end-to-end checks the email link via Selenium, and static tools like Dependabot scan libraries; the pyramid is an outcome, not a target.
AI-written summary · about
chapters (8)
- 0:00Testing pyramid intro
- 2:15History and purpose
- 8:41Test types explained
- 16:52Misunderstandings
- 20:01Practical user story tests
- 33:27Why different tests
- 37:01Pyramid in modern architectures
- 38:45Q&A
related talks
35mDemystifying the test pyramid
28mEgad! How Do We Start Writing Better Tests?
06mIgnites - The Test Automation Pyramid
57mInverting Test Pyramid - A First Hand Experience Report
30mTesting Pyramid Makes Little Sense, What We Can Use Instead
20mThe Road to Continuous Testing
49mThe Security Testing Pyramid for Developers
35mScalable Testing Strategies