Test Driven Development: By Example

✍ Scribed by Beck, Kent

• Publisher: Addison-Wesley Professional; Pearson Education (US)
• Year: 2002
• Tongue: English
• Leaves: 241
• Series: A Kent Beck Signature Book;The Addison-Wesley Signature Series
• Category: Library

✦ Synopsis

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.

✦ Table of Contents

Cover......Page 1
Contents......Page 8
Preface......Page 10
Acknowledgments......Page 16
Introduction......Page 18
PART I: The Money Example......Page 22
Chapter 1: Multi-Currency Money......Page 24
Chapter 2: Degenerate Objects......Page 32
Chapter 3: Equality for All......Page 36
Chapter 4: Privacy......Page 40
Chapter 5: Franc-ly Speaking......Page 44
Chapter 6: Equality for All, Redux......Page 48
Chapter 7: Apples and Oranges......Page 54
Chapter 8: Makin’ Objects......Page 56
Chapter 9: Times We’re Livin’ In......Page 60
Chapter 10: Interesting Times......Page 66
Chapter 11: The Root of All Evil......Page 72
Chapter 12: Addition, Finally......Page 76
Chapter 13: Make It......Page 82
Chapter 14: Change......Page 88
Chapter 15: Mixed Currencies......Page 94
Chapter 16: Abstraction, Finally......Page 98
Chapter 17: Money Retrospective......Page 102
PART II: The xUnit Example......Page 110
Chapter 18: First Steps to xUnit......Page 112
Chapter 19: Set the Table......Page 118
Chapter 20: Cleaning Up After......Page 122
Chapter 21: Counting......Page 126
Chapter 22: Dealing with Failure......Page 130
Chapter 23: How Suite It Is......Page 134
Chapter 24: xUnit Retrospective......Page 140
PART III: Patterns for Test-Driven Development......Page 142
Chapter 25: Test-Driven Development Patterns......Page 144
Chapter 26: Red Bar Patterns......Page 154
Chapter 27: Testing Patterns......Page 164
Chapter 28: Green Bar Patterns......Page 172
Chapter 29: xUnit Patterns......Page 178
Chapter 30: Design Patterns......Page 186
Chapter 31: Refactoring......Page 202
Chapter 32: Mastering TDD......Page 214
Appendix I: Influence Diagrams......Page 228
Appendix II: Fibonacci......Page 232
Afterword......Page 236
D......Page 238
M......Page 239
T......Page 240
X–Z......Page 241

✦ Subjects

Computer Science;Programming;Science;Technology;Software;Technical;Nonfiction;Coding;Computers;Engineering;Reference