Category Archives: Unit testing

The “single implementation” paradox – redux

Following on from , my colleague, Adrian, has given the issue some thought and written an excellent post explaining his position. His conclusion is that we should simply not be marking classes as final because it really doesn’t bring any … Continue reading

Posted in Design, Unit testing | Leave a comment

The “single implementation” paradox

We got into a bit of a debate at work recently. It went a bit like this: “Gah! Why do we have this interface when there is only a single implementation?” (The stock answer to this goes:) “Because we need … Continue reading

Posted in Design, Unit testing | 2 Comments

Unit testing smells

At work, we focus quite heavily on TDD and, therefore, unit testing (although our TDD extends to other levels, such as writing automated acceptance tests for a story before beginning development of the story). As is always the case with … Continue reading

Posted in Java, Unit testing | Leave a comment