On 09/30/10 15:51, Frank Schönheit wrote:
Well, this "the trick is ..." part is exactly why I think that
issueing a statement like "from now on, we do tests for our code"
won't work - this is a complex topic, with a lot of "tricks" to know,
so "Just Do It!" is an approach which simply doesn't work. But okay,
that's a different story.
I beg to differ: If code is not testable, it is not good and needs to
be changed.
You didn't get my point. Writing *good* and *useful* tests needs
education, for most, if not all of us. "Just do it!" won't give you
those tests, but just a pile of frustrated developers.
So, the learning which is needed here (and the "is needed here" is the
part which some of those saying "just do it!" miss) will be on a long
and hard road.
I didn't mean to say we should not take this road. I just wanted to say
(and this was probably the wrong forum here) that words are easy, while
doings are more difficult.
The assumption behind "write new tests" was that people are learning
while doing. At least for me, that's always worked out best. It was
not meant to imply that writing those tests, especially the first ones,
is easy.
If you have difficulties getting started, just talk to me, and I'm sure
we get any initial blockers out of the way. (Admittedly, I seem to be
unable to write nice getting-started tutorials...)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
