100% Code Coverage

If you write unit tests and don’t cover all business logic in your project, you are doing it wrong.

Each untested line of code may contain a bug. Only full coverage can provide confidence in your code.

"But all the unit tests passed!" #programming pic.twitter.com/8fRToLZdh9

— Jordan Hall 💻 (@DivineOmega) December 9, 2016

Integration tests may help to increase this important metric because they cover more lines of code at once.

However, they are harder to write, so don’t waste your time.

Much, much harder.

2 unit tests. 0 integration tests. pic.twitter.com/FpForNhhyi

— DEV Community (@ThePracticalDev) March 25, 2017

If somebody tells you that some issues may only be discovered in integration testing, don’t believe them!

2 unit tests. 0 integration tests pic.twitter.com/V2Z9F4G1sJ

— DEV Community (@ThePracticalDev) January 14, 2016

You don’t need integration tests.

Two unit tests, no integration tests. pic.twitter.com/RHWRvzsxnc

— Tim Bray (@timbray) January 20, 2017

Your code will always be used in the way you expected it to be used.

Have other examples? Share links in comments!

And don’t take this too serious.

Subscribe to all blog posts via RSS