[Pharo-project] Good reference on time on unit testing?
bschwab at anest.ufl.edu
Sun Feb 27 14:12:07 CET 2011
Understood. But, doing it correctly, how much of your time do you spend on the test writing/maintenance side? I found some blog posts, but I was hoping for some peer-reviewed papers that go on the record.
I am trying to make the point you are making, and it will go over better if I can point to literature and some numbers that I suspect will be seen as sobering. Tests ARE being "written after" in this case, but assuming they change to a proper process, they still need to understand that tests take thought and work.
From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Peter Hugosson-Miller [oldmanlink at gmail.com]
Sent: Sunday, February 27, 2011 2:58 AM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] Good reference on time on unit testing?
Couldn't have said it better myself!
On 27 feb 2011, at 08:27, laurent laffont <laurent.laffont at gmail.com<mailto:laurent.laffont at gmail.com>> wrote:
On Sun, Feb 27, 2011 at 4:52 AM, Schwab,Wilhelm K <<mailto:bschwab at anest.ufl.edu>bschwab at anest.ufl.edu<mailto:bschwab at anest.ufl.edu>> wrote:
Can anyone recommend a good reference on the amount of time one should expect to spend writing tests? I will have to be the messenger (will be wearing running shoes just in case...), but I want the message to come from a solid source.
If you develop the TDD way (which I always do at work) then I would say this question is not valid. Your production code will be there because of tests. In legacy system, new and refactored code will be there because of tests.
IMHO the questions "how much time should I spend writing tests?" or "how many tests should I write ?" are raised when tests are written after. And sadly tests often become a burden in this case and doesn't support the pressure of releases / last minute changes / ... (I've done it this way almost 10 years ago, not good :)
In TDD the question is "which stories / scenarios do we have to implement ?". It's more a Product owner / customer point of view.
The best book on TDD I've read is Dave Astels TDD: a practical guide (Indeed, this one has really changed my mind on how testing should be done, and other books I've read since don't).
More information about the Pharo-project