|Think about Loose Coupling|
Adding Unit tests to the development cycleby Sifmole (Chaplain)
|on May 26, 2006 at 14:44 UTC||Need Help??|
Sifmole has asked for the
wisdom of the Perl Monks concerning the following question:
So, I have managed to convince ( it didn't take much, because they are smart ) my immediate managers that adding unit test creation to the development cycle is a good thing.
They do want to know an estimate though of how much such an addition would affect the development time for tasks. For instance, without writing tests a developer could complete a certain task in 5 days; how long would it likely take for them to complete the task if writing unit tests was included in the task requirements.
I understand that the benefits are more confidence in the quality of the resulting code, quicker QA cycle ( potentially, or maybe just more effective QA cycle ), ease of future maintenace ( because you can regression test easier for instance ), etc, etc.
But what is the change to the development time cycle? Are there any experiences or articles you can relate/refer me to? I guess a great answer for the next step up would be if it could be summarized as kind of an average percent change....
Also, consider that the dev group is experience in coding, smart, resourceful -- but not used to unit testing. How would the percentage change as they got more experienced with including unit tests in their development process?
I ask here because I know there are several monks who are big proponents of this, and I hope have experience to relate; and we are talking Perl for at least the first group to do this.
thanks in advance.