... As such, testing should always be written concurrently while writing the implementation code. Alas, due to space constraints, this book won't contain much testing information.
This is definitely not the first time, I encounter this. Quite contrary I believe most of the books I read in which the author(s) enfavour test-driven development, may introduce or perhaps even include a whole chapter on testing, but little is shown in the rest of the book, and that really sends a bad signal.
So, people should do as the author says, but not as the author do throughout? No wonder, people just quite doesn't seem to get it.
Since there is little litterature, which use test-driven development, it seems unlikely that developer will catch up to this idea in the long run, as a means to provide quality.
On the other hand, Groovy in Action, use assertations in every example they show. This is a great kudoo to code quality.
Would developers learn test-driven development, because we say so, or will they learn to use assertations, because we have used them?
Instructing people affects their behaviour, and it seems to me that instructors fail to support test-driven development even though they appear to endorse it. I believe this will lead to a decline in the actual usability of tests in the next few years.
What do you think?
0 comments:
Post a Comment