4 ms·
TDD/unit tests are great in some cases: - when testing algorithmic logic - for rapid feedback - for setting up good context (e.g. a pool that is full) - hel
by henrik_w 6y ago
TDD/unit tests are great in some cases:
- when testing algorithmic logic
- for rapid feedback
- for setting up good context (e.g. a pool that is full)
- helps get well-tested parts for when using integration tests
- to make sure your design is decoupled
More here: https://henrikwarne.com/2014/09/04/a-response-to-why-most-unit-testing-is-waste/ https://henrikwarne.com/2014/09/04/a-response-to-why-most-un...
- wry_discontent 6y agoTDD is most useful to me for algorithmic logic. I tend to pull a lot of that stuff out of my code, because it's not related to my domain. TDD is a lifesaver for random one off algorithmic problems. You can either write it in 5 minutes, and spend the next 2 weeks fixing random bugs in your `includeRange` implementation, or you can spend 20 minutes to TDD the function and be done forever.