Fantastic Bugs And Where To Find Them by Iris Schaffer (Eng) | JSConfAM19
summary
Frontend testing wins are concrete not vague: a prop rename hides an address button until TypeScript or prop validation catches it, a missing Google Maps session token explodes API cost by ~900% until an integration test asserts the session persists, a loading flag left true shows an eternal spinner until rendering tests cover error paths, a missing slash in a landing URL breaks purchases so Cypress end-to-end tests run post-deploy, snapshot files balloon to 1788 lines so visual regression screenshots replace noisy snapshots and the in‑house tool improves confidence.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:43The bug finding pyramid
- 1:44Frontend testing
- 2:10Ground rules
- 3:20User addresses
- 4:25Filtering or updating
- 6:30A loader
- 9:55Breaking the bank
- 14:12Broken purchase flow
- 18:08Budget bug
- 18:33Snapshot tests
related talks
34mFantastic Bugs and Where to Find Them
38mFrontend Tests: what nobody said to you
30mIt's a (testing) trap! - Common end-to-end pitfalls and how to solve them
39mTesting, Testing, 1, 2, NaN
29mBlink and you’ll miss it: Stories from discovering most annoying bugs and test flakes
26mModern Testing Practices in Frontend Applications
19mIt's a (Testing) Trap! - Common Testing Pitfalls and How to Solve Them
57mGaining Confidence with Cypress Tests