A More Fluid Pyramid
summary
Argues the pyramid should be fluid not prescriptive and shows concrete tradeoffs: an identical user-flow as an end-to-end with Cypress, a shallow unit render, and a deeper react testing library integration test land at different places; replacing clicks with helper functions or test fixtures moves tests down the scale and speeds them up; frames testing by speed/cost/proximity to user, invokes Noah Sussman’s bug-filter and Swiss-cheese metaphors, and quotes George Box.
AI-written summary · about
chapters (20)
- 0:00Start
- 0:58Test Pyramid
- 4:22Explainers
- 6:17What Layers Should Be in the Pyramid
- 7:16Integration Tests
- 9:10Visual Testing
- 10:29Exploratory Testing
- 11:03How Does the Test Pyramid Change for Microservices
- 14:09Shallow Render
- 14:51React Testing Library
- 17:27Where in the Test Pyramid Are the Biggest Risks Addressed
- 19:43Agile Testing Quadrants
- 20:43What about Unknown Issues
- 21:55How I Use the Pyramid
- 23:18Visual Smoke Test
- 24:16Api Tests
- 24:37React Testing Library Tests
- 26:01User Journey Tests
- 26:12Create an Account
- 28:09Test Fixture
related talks
30mTesting Pyramid Makes Little Sense, What We Can Use Instead
35mDemystifying the test pyramid
46mThe Secrets of the Pyramids
17mYet again an upside down test pyramid – what can we do about it?
38mFlipping the Testing Pyramid
49mAn Easy Way to Automate Complex UI
23mI see your point, but… (Part 2)
39mMastering UI tests