Absolutely. I did this in one organization, starting with two unit tests. By the end of the week I had figured out how to add six more, and kept adding on. My work group picked up on what I was doing, and before long, the rest of the organization noticed that we had by far the best record in avoiding breaking the baseline of any group. They came over to learn. ?Within a year most of the organization was doing it as well.?
We do TDD because it gives us clearly better results. As long as your co-workers can see you attaining those results, whether it is in higher productivity or better quality, they will be faced with a choice: either you are smarter than they, or you have found a technique that works, and which they can learn. Guess which they would prefer to believe?
- Russ
This may not seem like a real answer. Save it and come back after all else fails.
Forget about all that stuff and start doing TDD. Do it by yourself. Do it with a partner if you can. Stop trying to make anybody else do anything.
You seem to be describing a situation in which neither the docs nor the manager want to use TDD, so focus on what you can control.
Maybe in six months someone will ask you about what you are doing that makes your code so good.
Charlie
On Apr 13, 2016 7:53 AM, "
poojawandile@...?[testdrivendevelopment]" <
testdrivendevelopment@...> wrote:
?
HI,
I am anticipating following challenges in TDD adoption. Any suggestion how to deal with such situations?
The list is long :-). Thanks,?
- 1.? ? ??You have a very experienced, senior and technically sound developer who has designed and developed solutions in a traditional way. This person has not completely bought in to the idea of TDD. How will you motivate such people??
- 2.??????The program that you are working on is complex, for that matter every program is complex, has dependencies on other systems/program/modules/components, how and where do you start with TDD? Developer fear making change/refactor as they believe any such attempt can break existing working system. They don't want to mess with something that is working.?
- 3.? ? ??Your team has traditionally worked in a test after situation, first write code and then write unit test cases. Time and again their mind first think of implementation logic since it has been trained that way for a long time, how do you make them unlearn this habit??
- 4.??????TDD will take time initially. The estimation of your project was done when TDD was not in picture. Now that you have to use TDD, how would you now negotiate with your manager and business for this extra time??
- 5.??????Why is singleton not considered a good design pattern. what are Technical challenges in using TDD in web applications.?
W
An
-----------------
Author,?Getting Started with Apache Maven <>
Author, HttpUnit <> and SimpleStub <>
Come read my webnovel,?Take a Lemon?<>,?
and listen to the Misfile radio play <>!
