Test! (Some OF) Your! Code!: How To Write...
summary
Starts by claiming the easiest wins come from pure functions, finding inputs and asserting outputs as documentation rather than perfect design. Builds a tiny command-builder example, writes failing tests to drive fixes, uses pytest.raises to capture expected errors, and watches a test catch a real typo during the demo. Recommends adding a CI code-coverage tool and notes a practical milestone of 10% coverage as meaningfully better than zero.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:42What this talk is not about
- 1:21What this talk is about
- 2:08Why don't we test?
- 3:47Where to start
- 4:54Let's test!
- 13:17You just saw me
- 14:07What next?
related talks
38mTesting for the Terrified: How to Write Tests, Conquer Guilt, and Level Up
21mDon't just test, my friend, test better
28mEgad! How Do We Start Writing Better Tests?
48mA Reflection on Software Testing
29mEgad! How Do We Start Writing (Better) Tests?
24mGo Write Tests using Pragmatic Best Practices
37mClean Test Code
17mWrite tests. Not too many. Mostly integration.