re: The Testing Introduction I Wish I Had VIEW POST


Great introduction. I would add two - often underrated - items to your Why Testing Matters section:

  • Unit and integration tests promote modular software design. Designing for testability makes code easier to understand and maintain.

  • Tests can serve as an additional documentation, especially to help other developers familiarize themselves with the code. Tests define what the software is supposed to do and what not.


These are good points and I thank you for bringing them up here! Especially the point about tests serving as extra documentation. I had planned to include a "tests make your code's aims explicit" section but that header felt too wishy-washy to me and I removed it. But if I'd framed it as documentation I likely would have kept it since it gets more to the point of how it adds value.

Code of Conduct Report abuse