Test-driven development : by example / Kent Beck.
Material type: TextSeries: The Addison-Wesley signature seriesPublication details: Boston : Addison-Wesley, c2003.Description: xix, 220 p. : ill. ; 24 cmISBN:- 0321146530 (alk. paper)
Item type | Current library | Call number | Copy number | Status | Date due | Barcode | |
---|---|---|---|---|---|---|---|
Standard Loan | Thurles Library Main Collection | 005.14 BEC (Browse shelf(Opens below)) | 1 | Available | R13360KRCT | ||
Standard Loan | Thurles Library Main Collection | 005.14 BEC (Browse shelf(Opens below)) | 1 | Available | R13361KRCT | ||
Standard Loan | Thurles Library Main Collection | 005.14 BEC (Browse shelf(Opens below)) | 1 | Available | R13356KRCT | ||
Standard Loan | Thurles Library Main Collection | 005.14 BEC (Browse shelf(Opens below)) | 1 | Available | R13353KRCT |
Enhanced descriptions from Syndetics:
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 provided by Syndetics
- Preface (p. ix)
- Acknowledgments (p. xv)
- Introduction (p. xvii)
- Part I The Money Example (p. 1)
- Chapter 1 Multi-Currency Money (p. 3)
- Chapter 2 Degenerate Objects (p. 11)
- Chapter 3 Equality for All (p. 15)
- Chapter 4 Privacy (p. 19)
- Chapter 5 Franc-ly Speaking (p. 23)
- Chapter 6 Equality for All, Redux (p. 27)
- Chapter 7 Apples and Oranges (p. 33)
- Chapter 8 Makin' Objects (p. 35)
- Chapter 9 Times We're Livin' In (p. 39)
- Chapter 10 Interesting Times (p. 45)
- Chapter 11 The Root of All Evil (p. 51)
- Chapter 12 Addition, Finally (p. 55)
- Chapter 13 Make It (p. 61)
- Chapter 14 Change (p. 67)
- Chapter 15 Mixed Currencies (p. 73)
- Chapter 16 Abstraction, Finally (p. 77)
- Chapter 17 Money Retrospective (p. 81)
- Part II The xUnit Example (p. 89)
- Chapter 18 First Steps to xUnit (p. 91)
- Chapter 19 Set the Table (p. 97)
- Chapter 20 Cleaning Up After (p. 101)
- Chapter 21 Counting (p. 105)
- Chapter 22 Dealing with Failure (p. 109)
- Chapter 23 How Suite It Is (p. 113)
- Chapter 24 xUnit Retrospective (p. 119)
- Part III Patterns for Test-Driven Development (p. 121)
- Chapter 25 Test-Driven Development Patterns (p. 123)
- Chapter 26 Red Bar Patterns (p. 133)
- Chapter 27 Testing Patterns (p. 143)
- Chapter 28 Green Bar Patterns (p. 151)
- Chapter 29 xUnit Patterns (p. 157)
- Chapter 30 Design Patterns (p. 165)
- Chapter 31 Refactoring (p. 181)
- Chapter 32 Mastering TDD (p. 193)
- Appendix I Influence Diagrams (p. 207)
- Appendix II Fibonacci (p. 211)
- Afterword (p. 215)
- Index (p. 217)
Excerpt provided by Syndetics
Author notes provided by Syndetics
Kent Beck consistently challenges software engineering dogma, promoting ideas like patterns, test-driven development, and Extreme Programming. Currently affiliated with Three Rivers Institute and Agitar Software, he is the author of many Addison-Wesley titles.