Have you ever seen or even developed a long, complex setup method in JUnit? Maybe it was because the production code was violating the Law of Demeter. Here's another Robert Martin Craftsman style entry.
Over time, how do you maintain a maximum 10 minute build? This is an important agile practice for continuous integration. This entry describes an Ant task designed to run standard JUnit tests concurrently.
Should a failing unit test break the build? Elliotte Rusty Harold recently discussed why he doesn't think so. Ever heard of test categorization? Well, there's a new test category in town - the todo test category[...]
There are some practical reasons for testing private methods (and inspecting private fields on occasion). This entry discusses these reasons and why using reflection instead of just changing the access scope of the method itself is the way to go.
Rarely do I disagree with Uncle Bob. I’ve learned a lot from reading his writings over the years. He recently blogged about mock objects in response to a blog from Cedric Beust...
Suppose I'm focused on specifying the behavior of a particular method. How do I know if I've specified everything? I'd like to share a checklist of things I think about to help accomplish this...
What does it mean when you perform a correct refactoring, but your tests break? This blog entry describes some decoupling tips to deodorize this code (or test) smell.
This entry discusses a controversial, yet practical technique for refactoring test methods into a concise specification of test cases for a production class method.
