#No such thing as overkill software#

Unit tests are easy to write and you want to write a lot of them. * well defined | * tests a larger feature So when writing unit tests there are a couple of sweet spots to think about when writing tests: unit test dirty hybrids integration test There is nothing wrong with using many testing frameworks and most of them are compatible with each other. This is why there are so many testing tools available as there are different types of tests. However you have to remind yourself that their scope are vastly different from unit tests. There is a confusion among a lot of developers who seem to think it is a good idea to treat all the different types of tests the same way, which leads to some dirty hybrids.Д®ven though TDD focuses on unit testing you will still find yourself writing functional, integration and performance tests. This is supposed to be fixed by using mocking frameworks (to test interactions isolated to one class only) and specification frameworks (to test features and specified requirements). Unit testing overkill is reached when you start writing other types of tests as if they were unit tests. There are several ways to overdo testing in general that defeats the purpose of TDD, BDD, ADD and whatever driven approach you use. You reach unit testing 'overkill' quickly and you might have reached it already. So when do you reach unit-testing overkill? A common setup would be the use unit-testing framework with mocking framework if the developers of the project don't want to roll their own mocks.

#No such thing as overkill software#

Some open-source software projects do use several testing frameworks.

Is it okay to use many testing frameworks at once?