| ||||||||||||
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Visit the Amazon.co.uk Trade-In Store for more details. |
Frequently Bought Together
Product details
|
More About the Author
Product Description
Product Description
Quite simply, test-driven development is meant to eliminate fear in application development. While some fear is healthy (often viewed as a conscience that tells programmers to "be careful!"), the author believes that byproducts of fear include tentative, grumpy, and uncommunicative programmers who are unable to absorb constructive criticism. When programming teams buy into TDD, they immediately see positive results. They eliminate the fear involved in their jobs, and are better equipped to tackle the difficult challenges that face them. TDD eliminates tentative traits, it teaches programmers to communicate, and it encourages team members to seek out criticism However, even the author admits that grumpiness must be worked out individually! In short, the premise behind TDD is that code should be continually tested and refactored. Kent Beck teaches programmers by example, so they can painlessly and dramatically increase the quality of their work.
From the Back Cover
Clean code that works--now. This is the seeming contradiction that lies behind much of the pain of programming. Test-driven development replies to this contradiction with a paradox--test the program before you write it.
A new idea? Not at all. Since the dawn of computing, programmers have been specifying the inputs and outputs before programming precisely. Test-driven development takes this age-old idea, mixes it with modern languages and programming environments, and cooks up a tasty stew guaranteed to satisfy your appetite for clean code that works--now.
Developers face complex programming challenges every day, yet they are not always readily prepared to determine the best solution. More often than not, such difficult projects generate a great deal of stress and bad code. To garner the strength and courage needed to surmount seemingly Herculean tasks, programmers should look to test-driven development (TDD), a proven set of techniques that encourage simple designs and test suites that inspire confidence.
By driving development with automated tests and then eliminating duplication, any developer can write reliable, bug-free code no matter what its level of complexity. Moreover, TDD encourages programmers to learn quickly, communicate more clearly, and seek out constructive feedback.
Readers will learn to:
This book follows two TDD projects from start to finish, illustrating techniques programmers can use to easily and dramatically increase the quality of their work. The examples are followed by references to the featured TDD patterns and refactorings. With its emphasis on agile methods and fast development strategies, Test-Driven Development is sure to inspire readers to embrace these under-utilized but powerful techniques.
0321146530B10172002
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
Sell a Digital Version of This Book in the Kindle Store
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
19 of 19 people found the following review helpful:
4.0 out of 5 stars
Short and sweet,
By
This review is from: Test Driven Development (The Addison-Wesley Signature Series) (Paperback)
Many of the other reviews for this book have criticised it for it's length and "lack of content". However, I found the book very enjoyable for what it is: an introduction to test driven development. TDD can be (and was for me) quite an alien concept for many programmers trained in a traditional way, where testing is often an afterthought. Kent's first example of TDD, while fairly trivial, outlines all the key points in how to practice TDD properly. It also fills you with confidence and makes you think "yeah, I could probably do that".Perhaps you will feel differently, but I like the book simply because it is short. Huge computing textbooks that cram in too much information annoy me; I rarely have the time to read through such huge tomes or absorb everything they are trying to tell you in one sitting. I was able to read the first part of this book, and attain a reasonable understand of TDD in just over 2 hours. The book is not terribly expensive either, and sets the stage for further reading on TDD and agile methodologies in general. I would recommend this book if you are at all interested in TDD.
54 of 61 people found the following review helpful:
2.0 out of 5 stars
Denied 1 star only because it's an interesting idea,
This review is from: Test Driven Development (The Addison-Wesley Signature Series) (Paperback)
I'm going to list my 3 day old copy in the Used section after I've finished writing this review.This book is in 4 sections, each of which would be a magazine article for any other author: 1. A tiring, trivial example of TDD strung out over a staggering 80 pages in normal Kent-Beck-six-sentences-per-page style. There is very little new in this book and even less to help with doing it on a real project. But wait! Before I'm branded an unthinking curmudgeon it's not all bad; for those who have pondered the vexing issue of how to add a parameter to a method then tucked away on page 190 I found this pearl of wisdom: 1. If the method is an interface, add the parameter to it. Well what can I say...eureka? Thanks for that Kent, I'll raise it at my next developer meeting but tell'em I thought of it, they'll think me a genius. How Addison Wesley can put this book in the same class as Martin Fowler's stuff is a mystery, the Fowler books contain more information in the Preface.
2 of 2 people found the following review helpful:
2.0 out of 5 stars
Interesting book spoiled by over-simplistic example,
By
This review is from: Test Driven Development (The Addison-Wesley Signature Series) (Paperback)
This book could have been so much better. For me it was spoiled by the ludicrously unrealistic example which is carried throughout the book. While its always a good idea to set out the first steps in a basic example I found that half way through the book the example was still so ludicrously over-simplified and unrelated to reality that I was tempted to throw the book away.
The principles and theories that underpin test driven development are poorly served by this book because of a lack of real-world practical examples.
Share your thoughts with other customers: Create your own review
Would you like to see more reviews about this item?
|
Most Recent Customer Reviews |
Listmania!
|
|
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
