3 ms·
I can see how you don't really need unit tests when using statically typed languages, but they are still handy. TDD is not only about unit testing, it's also ab
by brodo 13y ago
I can see how you don't really need unit tests when using statically typed languages, but they are still handy. TDD is not only about unit testing, it's also about integration testing and acceptance testing. In my experience, integration testing is a lot more valuable than unit testing because you may make certain assumptions about the libraries you use which are not true. With your own code that's less of a problem.
- kushti 13y agoTDD is test-centric development, i.e when you write test first then code. Unit tests are needed, other tests are needed too, the question is it worth to make testing the core of development process. From my practice, no
- sirmarksalot 13y agoSo there's a hard-core "always test first" fringe, but very few people are really advocating testing all your getters and setters. Heck, I think my code coverage is probably something like 1% (most of the code base is dumb construction of view models from CMS content), though I can't speak for other programmers. The practical approach is to test the complicated stuff, and design your code so that you can test it if you need to. This leads to better modularity and easier reusability across the board.