Testing loses its effectiveness if all programmers don't use them

Posted by Jeff O on Programmers See other posts from Programmers or by Jeff O
Published on 2012-04-12T15:14:15Z Indexed on 2012/04/12 17:41 UTC
Read the original article Hit count: 368

Let's assume you are convinced that the extra time spent unit testing has merit and improves production. Does that still hold up when everyone working on the same code doesn't use them? This question makes me wonder if fixing tests that everyone doesn't use is a waste of time. If you correct a test so the new code will pass, you're assuming the new code is correct. The person updating the test better have a firm understanding of the reasoning behind the code change and decide if the test or the new code needs to be fixed. This much inconsistency in a team when it comes to testing is probably an indication of other problems as well.

There is a certain amount of risk involved that someone else on the team will alter code that is covered by testing. Is this the point where testing becomes counter-productive?

© Programmers or respective owner

Related posts about unit-testing

Related posts about programming-practices