도서 정보
도서 상세설명
1: Why Should I Care for Test-driven Development?
Why TDD?
Testing
Mocking
Executable documentation
No debugging
Summary
2: Tools, Frameworks, and Environments
Git
Virtual machines
Build tools
The integrated development environment
Unit testing frameworks
Hamcrest and AssertJ
Code coverage tools
Mocking frameworks
User interface testing
The behavior-driven development
Summary
3: Red-Green-Refactor – from Failure through Success until Perfection
Setting up the environment with Gradle and JUnit
The red-green-refactor process
The Tic-Tac-Toe game requirements
Developing Tic-Tac-Toe
Code coverage
More exercises
Summary
4: Unit Testing – Focusing on What You Do and Not on What Has Been Done
Unit testing
Unit testing with TDD
TestNG
Remote controlled ship requirements
Developing the remote-controlled ship
Summary
5: Design – If It's Not Testable, It's Not Designed Well
Why should we care about design?
Connect4
Test the last implementation of Connect4
The TDD implementation of Connect4
Summary
6: Mocking – Removing External Dependencies
Mocking
Mockito
The Tic-Tac-Toe v2 requirements
Developing Tic-Tac-Toe v2
Integration tests
Summary
7: BDD – Working Together with the Whole Team
Different specifications
Behavior-driven development
The Books Store BDD story
JBehave
Summary
8: Refactoring Legacy Code – Making it Young Again
Legacy code
The Kata exercise
Summary
9: Feature Toggles – Deploying Partially Done Features to Production
Continuous Integration, Delivery, and Deployment
Feature Toggles
A Feature Toggle example
Summary
10: Putting It All Together
TDD in a nutshell
Best practices
This is just the beginning
This does not have to be the end
Appendix A: Index