Test Driven Development - is it worth it?
-
Hello, I have been looking into Test Driven Development lately, where the Unit Tests are designed and created first, and then production code is constructed to fulfill the unit test contracts. I am sold on the value of Unit Testing, however I am not yet convinced that true Test Driven Development offers significant return for the time spent in adjusting development practices. It would be great if some other professionals who have used TDD could share some of their experiences, good or bad, and share whether or not they found TDD to be a truly beneficial practice, with the understanding that I am asking specifically about TDD and not ordinary Unit Testing. I understand there's no magic bullet and I'm not expecting that, just looking for the best practice that makes the most sense for our development procedures.
"We are men of action; lies do not become us."
-
Hello, I have been looking into Test Driven Development lately, where the Unit Tests are designed and created first, and then production code is constructed to fulfill the unit test contracts. I am sold on the value of Unit Testing, however I am not yet convinced that true Test Driven Development offers significant return for the time spent in adjusting development practices. It would be great if some other professionals who have used TDD could share some of their experiences, good or bad, and share whether or not they found TDD to be a truly beneficial practice, with the understanding that I am asking specifically about TDD and not ordinary Unit Testing. I understand there's no magic bullet and I'm not expecting that, just looking for the best practice that makes the most sense for our development procedures.
"We are men of action; lies do not become us."
I've yet to work anywhere that implemented true TDD. The desire is there but time constraints, business needs and a constantly shifting playing-field usually mean a compromise is struck such that tests are created after the code is written to satisfy management, if time allows. Not saying it is right or wrong, just how it is.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
I've yet to work anywhere that implemented true TDD. The desire is there but time constraints, business needs and a constantly shifting playing-field usually mean a compromise is struck such that tests are created after the code is written to satisfy management, if time allows. Not saying it is right or wrong, just how it is.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
Hello, I have been looking into Test Driven Development lately, where the Unit Tests are designed and created first, and then production code is constructed to fulfill the unit test contracts. I am sold on the value of Unit Testing, however I am not yet convinced that true Test Driven Development offers significant return for the time spent in adjusting development practices. It would be great if some other professionals who have used TDD could share some of their experiences, good or bad, and share whether or not they found TDD to be a truly beneficial practice, with the understanding that I am asking specifically about TDD and not ordinary Unit Testing. I understand there's no magic bullet and I'm not expecting that, just looking for the best practice that makes the most sense for our development procedures.
"We are men of action; lies do not become us."
Very often clients like it if you can boast of, say. 85% test coverage.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it. My latest tip/trick Visit the Hindi forum here.