[Pharo-project] Good reference on time on unit testing?
bschwab at anest.ufl.edu
Sun Feb 27 17:47:14 CET 2011
I've asked the question three times because people seem to be trying to convince me (I'm on your side of this) rather than my audience.
Your idea of how much test code gets written would be a fine answer to have. One of the points I am going to make in the presentation is that tests are code too (yes, they apparently need to hear that). If expectations were realistic, I would not need numbers.
From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Yanni Chiu [yanni at rogers.com]
Sent: Sunday, February 27, 2011 11:19 AM
To: pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] Good reference on time on unit testing?
On 27/02/11 7:58 AM, Schwab,Wilhelm K wrote:
> I have no problem arguing that testing (if done well) can/will reduce
> overall development time; the question is how much of that time one
> should expect to devote to writing and maintaining unit and
> acceptance tests?
You've asked the question for the third time, so all the TDD
explanations seem to have missed the mark.
How about asking instead: how much test code do people write?
Maybe this way, both the TDD and the "how much time" viewpoints can be
accommodated (because volume of test code is roughly proportional to
time to write test code).
More information about the Pharo-project