Test Driven Development
By Example
Pearson Education · Print & ebook · November 8, 2002
Quite simply, test-driven development is meant to eliminate fear in application development.
We earn from qualifying purchases.
- Who it’s for
- A practical case for continual testing and refactoring—and for making feedback less frightening.
- Themes
- Test-driven development, Continuous testing and refactoring, Communication in programming teams
- Genres
- Testing & QA, Programming Basics
Nearest books
Matched by what the books are about, then ordered by what their readers also loved.
Domain-driven DesignEric Evans49% match
Clean CodeRobert C. Martin54% matchShares Programming Basics
Head First Design PatternsEric Freeman, Elisabeth Robson47% match
RefactoringMartin Fowler55% matchShares Testing & QA
Go Programming Language, theAlan Donovan, Brian Kernighan45% matchShares Programming Basics
Patterns of Enterprise Application ArchitectureMartin Fowler46% match
Agile Software Development, Principles, Patterns, and PracticesRobert C. Martin52% match
Clean Coder, theRobert Martin, Robert C. Martin53% matchShares Testing & QA
For younger readers: Python for Kids
Start with three books, and this one can be the first.
Members get a new edition every morning: a route out from their books to essays, research and talks, with the reason for each.
Start with this bookAbout this book
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.
Continue reading
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.
Code Without Fear
A practical case for continual testing and refactoring—and for making feedback less frightening.
Come here for
- See how tests and refactoring can steady difficult programming work.
- Explore the links between code quality, communication, and criticism.
Expect
- Examples that teach TDD through practice.
- An honest note that grumpiness remains an individual problem.
Where it sits
| Testing & QA | 95% |
|---|---|
| Programming Basics | 37% |
Percentages are BookFrontier’s reading of the book.
Publisher categories
- Software Development
- Testing & QA
- Authors
- Kent Beck
- Publisher
- Pearson Education
- Published
- November 8, 2002
- Format
- Print & ebook
- Theme
- Test-driven development · Continuous testing and refactoring · Communication in programming teams
- Reading lane
- Software Development