Interface Quality

Tests should be fast to write. Let’s say we have a little piece of code. It’s very likely to be correct. The consequences of the code when it is small are tiny if it is wrong.

We don’t care that the business doesn’t care. Writing that code might take ten seconds, but writing the test for the code will take eight hours. Do we write the tests? Well, there’s a dogmatic answer: We have a hundred percent coverage, and we’re proud of it.

I would say test writing is a trade-off. The test helps us test the interface that we are exposing. Tests are offering you a form of feedback that you won’t likely get otherwise, which is the quality of the interface used to invoke some logic.