As I proved at the end of last post, it was feasible testing classes that depended on IUrlWriter using a behaviour-testing style but getting an NullReferenceException when the test fails is far from ideal feedback.
No one would believe that, in this blog, throwing a bunch of unit tests to explore or verify some simple behaviour makes a post deserving a “Unit Testing” tag, right? ;-p
I (and the rest of my team) do a lot of code review. And when “code” is mentioned, unit tests are included.
I have mentioned before that one of the things that makes unit testing hard is the change of the domain of the problem, taking aside the fact that very few programming courses (if any) place any stress on how to properly test code, not even thinking about software as a whole.