Monthly Archives: June 2013

A Philosophy of Names

Reading a colleague’s unit tests recently and noticing some odd choices of test cases, like a test called “testConstructor” to confirm that no exceptions are thrown when you call the default constructor, it struck me that the choice of names

Posted in Clean Test Code

Annotations for EasyMock

Look at this: With JUnit, that’s all you have to do make a method behave as a test. It’s clear at first glance that this is a test. That one simple annotation makes the method take on all the characteristics

Posted in EasyMock, JUnit