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 benefits. Even if you’re trying to follow Design by Extension, the next guy is just [...]
Archive for category Unit testing
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 the interface in order to mock this class in our tests.” “Oh no you don’t, [...]
Unit testing smells
Jun 12
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 large bodies of code created by a transient group of people over a reasonable period [...]