3 ms·
While I can't prove it, my intuition tells me that when I do TDD, my designs are much more flexible and my code is much more reliable. Stuff that I would have b
by kristiandupont 18y ago
While I can't prove it, my intuition tells me that when I do TDD, my designs are much more flexible and my code is much more reliable. Stuff that I would have buried in one class is often split into smaller classes. This gives some overhead, yes, but the tests are well worth the effort.
>"If you must do testing..."
Are you suggesting that tests are bad in general?
- ardit33 18y agono. Testing has it's place, in important functionality, high level features, or if you are dealing with 3rd party, outsourcing companies, and integrating their code (make sure their stuff works as specified). TDD by definition is build the test first, and then develop, which is implies, test everything. Most of the code people write is not really test worthy.
- aaronblohowiak 18y ago"TDD by definition is build the test first, and then develop, which is implies, test everything." That is errant. You can create high-level tests for new functionality, and then implement the myriad of implementation details to fulfill that test. Until all of our languages and libraries have 100% test coverage, you must decide to draw the line short somewhere. Disclaimer: I am not a TDD aficionado, and we don't practice it at the dayjob.