JUnit Pocket Guide: Quick Look-up and Advice (英語) ペーパーバック – 2004/10/3
Kindle 端末は必要ありません。無料 Kindle アプリのいずれかをダウンロードすると、スマートフォン、タブレットPCで Kindle 本をお読みいただけます。
Kent Beck is the founder and director of Three Rivers Institute (TRI). He has pioneered patterns for software development, the XUnit family of test frameworks, the HotDraw drawing editor framework, CRC cards, refactoring, and most recently eXtreme Programming (XP). He is the author of Extreme Programming Explained, Planning Extreme Programming, and The Smalltalk Best Practice Patterns. He lives on 20 acres in rural southern Oregon with his wife, five children, four dogs, two sheep, and a variable number of domestic fowl.
|星5つ 11% (11%)||11%|
|星4つ 41% (41%)||41%|
|星3つ 15% (15%)||15%|
|星2つ 16% (16%)||16%|
|星1つ 17% (17%)||17%|
Odd that the table of contents is at the back of the book.
Veloce ed essenziale.
Ovviamente da solo non basta, se non per un "pronti, partenza, via!".
Ottimo per una lettura in metro...
The high points are that in addition to being a straightforward intro to JUnit, written by a developer of the package itself, it also covers testing philosophy and strategies. Plus integration with the Eclipse IDE and ANT build infrastructure, two things critical in our shop.
The primary quibble is that it was written when the latest version was JUnit 3.8, and 4.0 introduces a significant albeit easy-to-adapt-to syntactical change (annotations) to mark test methods. The concepts are still the same, the mechanics a bit different. The book could use an update, though there is a potential mitigation at the end of the volume: a link to the publisher's site, where you can spend a few more dollars for rights to DRM-free copies with access to all future revisions.
Another nice thing would be a bit more information on the extension packages. There's a short list of them, but no description of their purpose. JUnit itself is pretty barebones, and I'm coming from a Perl background where the analagous starting point is Test::More with a zillion handy add-on modules that do more interesting things. JUnit must underpin a similar ecology.
All in all, just what I needed to more properly orient orient myself to this handy widget.
I decided to buy a book on JUnit, but was unsure which one, so decided to buy this as a starter, and later get a more thorough book.
The material in the book is fine, but I found I had no real insight after reading it. In other words, I wasn't sure how to use JUnit for my compiler project. I've decided that I want to make some tests fail and some pass, rather than make each pass, but I'm still wondering how to do this while my error handling and printing diagnostics are changing as the project goes on. In other words, if the program is in a state of flux, how can I write hard-coded tests?
This review is positive because I feel I can't blame the author for my lack of insight. On the other hand, I don't remember reading any motivating examples in the book. I think if there was a bit of extra material, I might have worked out how to make JUnit work for my app. So, I've taken away one star. Overall, a happy customer given the cheap cost of the book.
While the book more or less meets those goals, the writing is terse and mostly fails to provide the illuminating insights I was hoping for. I was also disappointed that the book is not well-structured to use as a reference, and is somewhat out of date with JUnit 4.x at this point. After reading this I moved on to "JUnit in Action", which I highly recommend.
Overall, I'm not disappointed that I got the book given the reasonable price and minimal investment in time reading it. It does serve as a quick introduction to and motivation for using JUnit. However, if you intend to put JUnit into practice, you can easily skip this book and go directly to one of the many excellent and more comprehensive books on JUnit--this book won't be enough and offers nothing indispensable.
The book is just poorly organized. It lacks a logical flow. It is just snippets of information. You could argue that a pocket guide can't be expected to give a completely in depth coverage of a topic. However the author finds room to talk about the history of how he and his buddies conceived the idea for the framework on a flight. There is plenty of usage of "I" and "Me" in the book as he brags about his achievements and his testing philosophy. Most of the examples are only a few lines of code, as opposed to a complete java class. You have to figure out yourself which classes have to be imported etc. Ok, so that forces you to think for yourself. But it defeats the purpose of buying a guide.
The author is the father of the JUnit and related frameworks. But this book is just off the mark.