![Testing a book's code: Overall conclusions](/content/images/size/w600/image/fetch/w_2000,h_2000,c_fill,f_jpg,q_auto:good,fl_progressive:steep,g_auto/https-3a-2f-2fsubstack-post-media.s3.amazonaws.com-2fpublic-2fimages-2f535dffec-3303-40c6-a101-440465f3e6e7_1346x362.jpg)
Newsletter
Testing a book's code: Overall conclusions
MP 84: Final takeaways from a detailed look at testing.
Newsletter
MP 84: Final takeaways from a detailed look at testing.
Newsletter
MP 83: Testing a simple but nontrivial Django project, from a reader's perspective.
Newsletter
MP 82: Testing complex HTML output, and output that varies based on API calls.
Newsletter
MP 80: Modifying files and making assertions about images.
Newsletter
MP 79: Testing code that might not seem testable at first.
Newsletter
MP #77: Using parametrization to efficiently write a large batch of tests.
Newsletter
MP 76: Testing code for a book is different than testing a standard programming project, but brings up many relevant issues.
Newsletter
MP 72: What exactly are units, and how do we test them?
Newsletter
MP 45: Unit tests are easy to write, but they're not always the best place to start.