In the coding world, whether you are an expert or a beginner, there are some scenarios where code seems to be weird. You can't avoid a feeling that something is wrong with the code when reading it. You even occasionally wonder why the previous programmer implemented a specific method or a class in such a bad manner. This is because the same functionality can be implemented in a vast number of different ways, each of them being unique. With this big number of possibilities, which is the best one? The answer is that all of them are valid as they all achieve the goal. However, it is true that some considerations should be taken into account while finding better solutions. This is where design becomes important.
Test-Driven Java Development
Test-Driven Java Development
Overview of this book
Table of Contents (17 chapters)
Test-Driven Java Development
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
Why Should I Care for Test-driven Development?
Tools, Frameworks, and Environments
Red-Green-Refactor – from Failure through Success until Perfection
Unit Testing – Focusing on What You Do and Not on What Has Been Done
Design – If It's Not Testable, It's Not Designed Well
Mocking – Removing External Dependencies
BDD – Working Together with the Whole Team
Refactoring Legacy Code – Making it Young Again
Feature Toggles – Deploying Partially Done Features to Production
Putting It All Together
Index
Customer Reviews