Tests That Help you Find Defects Faster
summary
Calls out four concrete fixes: split tests that use "and" into separate cases and add a small connection test for DB access when both read and write fail, prefer Jest and Testing Library assertions like toHaveProperty and expect(fn).toThrow(message) so failures show the differing values, extract repeated setup into named helpers to keep tests small and avoid copy‑paste, and refuse DRY that creates shared mutable state so tests stay isolated dont over‑DRY tests.
AI-written summary · about
chapters (5)
related talks
41mTesting that the code does what the code does
30mIt's a (testing) trap! - Common end-to-end pitfalls and how to solve them
39mTesting, Testing, 1, 2, NaN
45mWriting Tests That Don't Suck: TDD in JavaScript
12mTesting: What's it all about?
26mTip Top Testing in JavaScript
40mUnselfish Testing
39mIdentifying and Testing Details That Matter Using Automated Tests