TDD and management

Question

My manager begins to get very annoyed that I devote time to developing tests (he sees testing as what you do after writing the software). Him I convince him otherwise?

Answer 1

You cannot win in a similar situation. Until he took the blue (tdd) pill, he did not recognize. The only thing you can do is either leave for a better job or do it your own way. And as you do the latter, explain to him how TDD is the best approach and gives him examples. But I would say his path or highway.

Answer 2

Tell him that you will save time by writing tests now, since the testing and debugging phases are potentially shorter since you have already discovered many of the errors.

Answer 3

He sees clearly that testing must be done. Doing this after writing the code takes as much time as before writing the code. If he likes, you can skip the test recording and use the time to write errors.

If he doesn’t think you should do the testing, then either change your mind or quit.

Answer 4

The key is to understand your point of view of managers. You must step back and ask what the values ​​of the manager are and what his pain indicates. If you do not know what exactly they value.

Answer 5

Show him or give him these links that will help him understand TDD in a clear way.

http://agilepainrelief.com/notesfromatooluser/2008/10/advantages-of-tdd.html

http://www.agiledata.org/essays/tdd.html#TraditionalTesting

Answer 6

For clients who were resistant to my repeated testing, I try to explain things in these terms: Writing tests in front costs me minutes in advance, but saves me hours near the concert. And from time to time it costs me hours in advance, but saves me days near the concert.

Some of the links provided in other answers are also excellent. If the boss is still resisting after this proof and argument have been shown ... I would have polished my resume. Your ability and desire to write code correctly should put you in a good position to pick up less terrible work.

Answer 7

Another route might be to show how running tests ahead of time somehow changes the design. Based on tests, this casts doubt on the parts of the design and, ultimately, it will be a good way, and that it should check how much time is required for maintenance and support, as part of this is done to improve these areas. Just do not forget to recall some principles, such as How to make friends and influence people who may also be applicable here.