...
Next time: Chapters 8 and 9.
Chapter 8 and 9
- Cliff discovered a useful tool! Mocking server for IDAs that need to talk to each other.
- There's also a python tool called beta-max which "caches" IDA responses (so you can write tests against responses)
Boundaries
- Wrapping 3rd party libraries: it can easily be overdone.
- Forking, and making minimal changes, can bite us, since it makes it more complicated to upgrade the library
- Could be a good place to get in the habit of wrapping
- Coverage of 3rd-party library — does it matter if it has low-percentage test coverage?
- If we wrapped 3rd-party libraries, having unit tests for the wrapper could prevent against 3rd-party libraries of unknown quality
- Difference between testing against 3rd-party libraries and services
Testing
- "What we talk about when we talk about testing" — "I'm sure there's a blog post called that out there"
- TDD
- Clean code: don't write more code than is sufficient to pass the test
- Relationship to red/green/refactor? — Similar, when you get down to first principles
- Sometimes DRY-ness in tests make them harder to understand (DRY = don't repeat yourself)
- DRY tests make it easier to do large refactoring
- DSLs for Testing
- Course DSL for creating courses in tests
- Using named-tuples for ddt --> makes tests more readable (could also use a dict)
10 and 11 next week