3 ms·

I agree that unit testing is a waste if the project requirements change quickly. Unit tests can take ages to write and if the project requirements are changing

I agree that unit testing is a waste if the project requirements change quickly. Unit tests can take ages to write and if the project requirements are changing constantly, then you keep having to update them and it slows down development and kills productivity - I've seen this happen many times in previous companies. Unit tests only make sense for components of a system which are BOTH critical and stable. I think that integration tests are often way more useful for most projects.

stcredzero 10y ago
Unit tests can take ages to write and if the project requirements are changing constantly, then you keep having to update them and it slows down development and kills productivity - I've seen this happen many times in previous companies. In some environments, refactorings to the code will also refactor the tests. Doing test first is only a win in the situation where you don't have to duplicate work, and only if management wouldn't otherwise give you the time to write tests after the fact. Unfortunately, the former is less common, and the latter is more common.