I like TDD, it's pretty useful in many cases, but... you may be starting this the wrong way around. Your question is "should I use this testing technique?". A

I like TDD, it's pretty useful in many cases, but... you may be starting this the wrong way around. Your question is "should I use this testing technique?". A better question to start with is "what am I trying to achieve with testing?" Once you know your goal you can find a relevant testing technique to achieve it. Your goals will likely be different for different parts of your product and codebase. Notice this means different organizations and products (or same product at different times in its lifecycle) will have different forms of testing, because they have different goals and resources. To help with the decision process of choosing testing goals I've come up with a model, of different goals and the kinds of testing that are useful for each. I'm going to be giving this as a talk at PyCon in May, but have an essay version written up: https://codewithoutrules.com/2017/03/26/why-how-test-software/ https://codewithoutrules.com/2017/03/26/why-how-test-softwar... Since choice of testing strategy is situation-specific it's very hard to give a general answer without understanding the specifics - ping me (itamar at codewithoutrules dot com) if you'd like to talk over your specific situation.