Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Get Your Hands Dirty on Clean Architecture

You're reading from   Get Your Hands Dirty on Clean Architecture Build 'clean' applications with code examples in Java

Arrow left icon
Product type Paperback
Published in Jul 2023
Publisher Packt
ISBN-13 9781805128373
Length 168 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Tom Hombergs Tom Hombergs
Author Profile Icon Tom Hombergs
Tom Hombergs
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Preface 1. Chapter 1: Maintainability 2. Chapter 2: What’s Wrong with Layers? FREE CHAPTER 3. Chapter 3: Inverting Dependencies 4. Chapter 4: Organizing Code 5. Chapter 5: Implementing a Use Case 6. Chapter 6: Implementing a Web Adapter 7. Chapter 7: Implementing a Persistence Adapter 8. Chapter 8: Testing Architecture Elements 9. Chapter 9: Mapping between Boundaries 10. Chapter 10: Assembling the Application 11. Chapter 11: Taking Shortcuts Consciously 12. Chapter 12: Enforcing Architecture Boundaries 13. Chapter 13: Managing Multiple Bounded Contexts 14. Chapter 14: A Component-Based Approach to Software Architecture 15. Chapter 15: Deciding on an Architecture Style 16. Index 17. Other Books You May Enjoy

How much testing is enough?

A question many project teams I’ve been part of couldn’t answer is how much testing we should do. Is it enough if our tests cover 80% of our lines of code? Should it be higher than that?

Line coverage is a bad metric to measure test success. Any goal other than 100% is completely meaningless because important parts of the code base might not be covered at all.6 And even at 100%, we still can’t be sure that every bug has been squashed.

6 Test coverage: if you want to read more about 100% test coverage, have a look at my article with the tongue-in-cheek title Why you should enforce 100% code coverage at https://reflectoring.io/100-percent-test-coverage/.

I suggest measuring test success by how comfortable we feel shipping the software. If we trust the tests enough to ship after having executed them, we’re good. The more often we ship, the more trust we have in our tests. If we only ship twice a year, no one will...

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 €18.99/month. Cancel anytime