Click on a thumbnail to go to Google Books.
Loading... Test-Driven Development: A Practical Guide (edition 2003)by David Astels
Work InformationTest-Driven Development: A Practical Guide by David Astels
None Loading...
Sign up for LibraryThing to find out whether you'll like this book. No current Talk conversations about this book. Astels provides a good guide to test-driven development (TDD). The bulk of the book works through an example of developing a Swing-based GUI application using TDD. The book is quite Java-centric, but there's several sections at the end on unit testing tools for non-Java languages, and the general concepts should apply to any language. It was also nice to see how to apply TDD to a GUI, which is something I didn't understand before reading the book. If you're interested in trying out TDD, but you don't really know how to proceed, this is a good place to start. no reviews | add a review
Test-Driven Development: A Practical Guide presents TDD from the perspective of the working programmer: real projects, real challenges, real solutions, ...real code. Dave Astels explains TDD through a start-to-finish project written in Java and using JUnit. He introduces powerful TDD tools and techniques; shows how to utilize refactoring, mock objects, and "programming by intention"; even introduces TDD frameworks for C++, C#/.NET, Python, VB6, Ruby, and Smalltalk. Invaluable for anyone who wants to write better code... and have more fun doing it! No library descriptions found. |
Current DiscussionsNone
Google Books — Loading... GenresMelvil Decimal System (DDC)005Information Computing and Information Computer programming, programs, data, securityLC ClassificationRatingAverage:
Is this you?Become a LibraryThing Author. |
Test-driven development builds on the principle that developers should write tests before they write code. The tests determine the code that needs to be written. As a side effect, this results in a suite of programmer tests. However, the book stresses that TDD primarily exists as a development methodology, not a testing methodology. The test suite produced by this methodology should not be considered a replacement for through testing by those who have testing as their primary goal.
My detailed impressions of the book and test-driven development.
test-driven development: A Practical Guide provides a good introduction to test-driven development. It contains many useful insights and practical tips. However, I suspect that you can find more focused, up-to-date introductions to the topic than the one found in this book. ( )