Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Test-Driven Java Development, Second Edition

You're reading from   Test-Driven Java Development, Second Edition Invoke TDD principles for end-to-end application development

Arrow left icon
Product type Paperback
Published in Mar 2018
Publisher Packt
ISBN-13 9781788836111
Length 324 pages
Edition 2nd Edition
Languages
Arrow right icon
Authors (2):
Arrow left icon
Viktor Farcic Viktor Farcic
Author Profile Icon Viktor Farcic
Viktor Farcic
 Garcia Garcia
Author Profile Icon Garcia
Garcia
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Title Page
Packt Upsell
Contributors
Preface
1. Why Should I Care for Test-Driven Development? 2. Tools, Frameworks, and Environments FREE CHAPTER 3. Red-Green-Refactor – From Failure Through Success until Perfection 4. Unit Testing – Focusing on What You Do and Not on What Has Been Done 5. Design – If It's Not Testable, It's Not Designed Well 6. Mocking – Removing External Dependencies 7. TDD and Functional Programming – A Perfect Match 8. BDD – Working Together with the Whole Team 9. Refactoring Legacy Code – Making It Young Again 10. Feature Toggles – Deploying Partially Done Features to Production 11. Putting It All Together 12. Leverage TDD by Implementing Continuous Delivery 1. Other Books You May Enjoy Index

Possible improvements


In this section and the following subsections, we are going to tackle some of the problems described in Alice's story. Because the code we inherited from the example is already implemented, we can't apply TDD here. Instead, we are going to set the basis and prepare the ground for future developments where applying TDD will become very useful.

Although there are always many things that can be improved, the pain points being addressed are code merging issues, lots of manual testing, manual releases, and the length of time taken to develop changes or new features.

For the first two, we are going to increase the test coverage of the application and implement CI. A Jenkins server is going to be configured to address the third issue, manual releases. And finally, the last issue, which is the long time to market (TTM), is going to be mitigated by implementing the rest of the solutions.

Increasing test coverage

Among the metrics for measuring code quality, there is one that is...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at AU $19.99/month. Cancel anytime
Visually different images