Book Image

Test-Driven Java Development

Book Image

Test-Driven Java Development

Overview of this book

Related Content you might be interested in

Current Title:

Small book image
Test-Driven Java Development
Aug, 2015 | 284 pages
No titles found
Table of Contents (17 chapters)
Test-Driven Java Development
Test-Driven Java Development
Credits
Credits
About the Authors
About the Authors
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Why Should I Care for Test-driven Development?
Why Should I Care for Test-driven Development?
Why TDD?
Testing
Mocking
Executable documentation
No debugging
Summary
2
Tools, Frameworks, and Environments
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
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 – 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
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 – 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
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
Refactoring Legacy Code – Making it Young Again
Legacy code
The Kata exercise
Summary
9
Feature Toggles – Deploying Partially Done Features to Production
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
Putting It All Together
TDD in a nutshell
Best practices
This is just the beginning
This does not have to be the end
Index
Index

The Tic-Tac-Toe v2 requirements

The requirements of our Tic-Tac-Toe v2 application are simple. We should add a persistent storage so that players can continue playing the game at some later time. We'll use MongoDB for this purpose.

Note

Add MongoDB persistent storage to the application.

Previous Section
End of Section 4
Next Section