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

About the Authors

Viktor Farcic is a software architect. He has coded using a plethora of languages, starting with Pascal (yes, he is old), Basic (before it got the Visual prefix), ASP (before it got the .Net suffix) and moving on to C, C++, Perl, Python, ASP.Net, Visual Basic, C#, JavaScript, and so on. He has never worked with Fortran. His current favorites are Scala and JavaScript, even though he works extensively on Java. While writing this book, he got sidetracked and fell in love with Polymer and GoLang.

His big passions are test-driven development (TDD), behavior-driven development (BDD), Continuous Integration, Delivery, and Deployment (CI/CD).

He often speaks at community gatherings and conferences and helps different organizations with his coaching and training sessions. He enjoys constant change and loves working with teams eager to enhance their software craftsmanship skills.

He loves sharing his experiences on his blog, http://TechnologyConversations.com.

I would like to thank a lot of people who have supported me during the writing of this book. The people at Everis and Defie (companies I worked with earlier) provided all the support and encouragement I needed. The technical reviewers, Alvaro Garcia, Esko Luontola, Jeff Deskins, and Muhammad Ali, did a great job by constantly challenging my views, my assumptions, and the quality of the code featured throughout the examples. Alvaro provided even more help by writing the Legacy Code chapter. His experience and expertise in the subject were an invaluable help. The Packt Publishing team was very forthcoming, professional, and always available to provide guidance and support. Finally, I'd like to give a special thanks to my daughter, Sara, and wife, Eva. With weekdays at my job and nights and weekends dedicated to this book, they had to endure months without the support and love they deserve. This book is dedicated to "my girls".

Alex Garcia started coding in C++ but later moved to Java. He is also interested in Groovy, Scala, and JavaScript. He has been working as a system administrator and also as a programmer and consultant.

He states that in the software industry, the final product quality is the key to success. He truly believes that delivering bad code always means unsatisfied customers. He is a big fan of Agile practices.

He is always interested in learning new languages, paradigms, and frameworks. When the computer is turned off, he likes to walk around sunny Barcelona and likes to practice sports.

I did enjoy writing this book and I want to thank those people who made this possible. First of all, thanks to the staff at Packt Publishing for giving me this opportunity and the guidance along this difficult journey. Thanks to the technical reviewers, Alvaro Garcia, Esko Luontola, Jeff Deskins, and Muhammad Ali, for the tips and corrections; they added great value with their comments. Thank you, Viktor Farcic, for sharing this experience with me. It has been a pleasure to be your mate during this adventure. And finally, special thanks to my parents, my brother, and my girlfriend for being there whenever I need them. This book is dedicated with love to all of them.

Previous Section
Next Chapter