chapter 2: tools, frameworks, and environments · [ 8 ] chapter 4: unit testing – focusing on...

33
Chapter 2: Tools, Frameworks, and Environments

Upload: doancong

Post on 08-Sep-2018

234 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

Chapter 2: Tools, Frameworks, andEnvironments

Page 2: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 2 ]

Page 3: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 3 ]

Page 4: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 4 ]

Page 5: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 5 ]

Chapter 3: Red-Green-Refactor – FromFailure Through Success until Perfection

Page 6: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 6 ]

Page 7: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 7 ]

Page 8: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 8 ]

Chapter 4: Unit Testing – Focusing on WhatYou Do and Not on What Has Been Done

Page 9: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 9 ]

Page 10: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 10 ]

Page 11: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 11 ]

Page 12: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 12 ]

Page 13: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 13 ]

Chapter 5: Design – If It's Not Testable, It'sNot Designed Well

Page 14: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 14 ]

Chapter 6: Mocking – Removing ExternalDependencies

Page 15: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 15 ]

Page 16: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 16 ]

Chapter 8: BDD – Working Together with theWhole Team

Page 17: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 17 ]

Page 18: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 18 ]

>

Page 19: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 19 ]

Page 20: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 20 ]

Page 21: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 21 ]

Chapter 9: Refactoring Legacy Code –Making It Young Again

Page 22: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 22 ]

Page 23: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 23 ]

Page 24: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 24 ]

Page 25: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 25 ]

Chapter 10: Feature Toggles – DeployingPartially Done Features to Production

Page 26: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 26 ]

Page 27: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 27 ]

Page 28: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 28 ]

Chapter 12: Leverage TDD by ImplementingContinuous Delivery

Page 29: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 29 ]

Page 30: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 30 ]

Page 31: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 31 ]

Page 32: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 32 ]

Page 33: Chapter 2: Tools, Frameworks, and Environments · [ 8 ] Chapter 4: Unit Testing – Focusing on What You Do and Not on What Has Been Done

[ 33 ]