Testing: What's it all about?
summary
Explains test-driven development as writing a failing test first then making code pass using a concrete addOne example that starts with a base case, runs in jest and shows the cathartic green light when the tweak makes expect(...).toEqual(2) succeed. Distinguishes unit tests (micro, one assertion) from integration/end-to-end (broad, many assertions) and warns about flaky non-deterministic tests, unreadable specs, and repeating unit checks inside integration tests.
AI-written summary · about
chapters (7)
- 0:00Introduction to testing
- 1:05Personal testing journey
- 2:27Writing a basic test
- 5:59Why testing matters
- 7:23Testing jargon explained
- 9:27Common testing pitfalls
- 10:50Final tips and summary
related talks
01h 06mBeyond Test Driven Development
49mESSENTIALS - Canon Test-Driven Development
41mTesting that the code does what the code does
29mTest-Driven Development with Jest
21mTests That Help you Find Defects Faster
16mA unit test walks into a bar
39mThe Three Laws of Test Driven Development are Useful
45mWriting Tests That Don't Suck: TDD in JavaScript