Channels ▼

Developer's Reading List

, July 17, 2012 Windows Debugging, Web Apps, JavaScript, and Clojure Lead the List of New Titles
  • E-mail
  • Print

ATDD By Example

by Markus Gartner

Dr. Dobb's policy is not to review poor books. It is far more useful to provide information on what is worth reading than what is not. However, we are occasionally forced to review undesirable books as is the case here because of an outside factor. That factor here is that the book appears in the Kent Beck Signature series from Addison-Wesley and it has a foreword containing Beck's own recommendation. The Beck name has generally signaled books you could buy with complete assurance. However, this volume is not close to anything you could want or use. The errors are so pervasive that rather than dwell on them individually, I'll group them quickly.

Code: The code is nominally written in Java. However (see illustration above) it is so badly formatted that it is a constant struggle to read it. Moreover, there are multiple occasions where at a glance you can tell the code as printed will not compile.

Layout: The book is an introduction to acceptance test-driven development (ATDD). The author chooses to write it in three parts, with the curious sequence of: example 1, example 2, followed by principles of ATDD. He must have sensed this was a backwards way of doing things, as he suggests multiple ways of reading the book. As to reading it in the actual order, he observes, "You may also read the first two examples, and then head back to work to start a basic implementation. Once you reach a dead end, you may come back to read further material in Part III — although I wouldn't necessarily recommend reading this book in this order." [emphasis mine]

Language: The author is not a native speaker. The editors failed him badly by not correcting his pervasive misuse of the terms — especially this and that — which forces the reader to reread sentences to figure out which of two possible things the author is referring to. Likewise, the book is littered with sentences whose contorted syntax was left uncorrected.

I can only surmise that Kent Beck's imprimatur was given early in the process with the expectation that all these errors, which appear on every page, would be removed. They weren't. Not recommended.
— ALB






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.