Wait, before you write your next test...
summary
Advocates adding linters first: Prettier, ESLint and @ts-check with JSDoc to get IntelliSense and catch obvious bugs before tests. Use the Cypress code coverage plugin to instrument app code, where a single end-to-end run hits about 72% of lines and combining unit tests fills the rest to ~100%. Split long end-to-end flows into checkpoints by snapshotting the app state on window to resume later, limit individual tests to short runtimes and treat coverage as a guide not a pass/fail goal.
AI-written summary · about
chapters (8)
- 0:00Introduction and climate pledge
- 3:21Why testing feels like a drag
- 7:31Documenting code with types
- 12:27What should I test
- 16:13Code coverage as a guide
- 21:45How long should tests be
- 25:41Splitting long tests
- 29:00Final advice and thanks
related talks
47mEverything I know about writing quality software
30mTesting Tools and Their Friends
32mCypress.io – the State of the Art End-to-end Testing Tool
42mWait, I have to test the front end too?
38mFrontend Tests: what nobody said to you
17mWrite tests. Not too many. Mostly integration.
57mGaining Confidence with Cypress Tests
35mYou Could Lint More