Tag Archive


It’s a bird, it’s a plane… it’s a super call?

Martin Fowler wrote about the Call Super smell. This occurs when you are allowed to override a method in a parent class, but you must (as opposed to can) call the parent implementation in your method.

Unnecessary dependencies are at least midly naughty

I really, really, shouldn’t bite, but… Cedric is asking about dependent test methods and if they are evil Well, they may not be evil, but they are at least mildly naughty.

Ant 1.6.2 <junitreport> doesn’t work on Java 1.4.1

Little warning for anyone else who stumbles across this problem: the stylesheet used for <junitreport> in Ant 1.6.2 does not work with Xalan 2.2. Unfortunately, this is the version that’s bundled inside the rt.jar in Java 1.4.1.

Ant 1.6.2 is out

Yep, Ant 1.6.2 has been released. And the forkmode option for JUnit is there!. I’m really happy.

What I don’t like about TestNG

Seeing all the comments today about using annotations to declare test cases reminded me that I never got around to writing about what I didn’t like about TestNG

Does JUnit need annotations?

Filippo Diotalevi wrote about a wishlist for a better JUnit and he mentioned Cedric’s pet idea of using annotations to identify test cases.

JUnit Architecture Redux

Looks like I’m talking about another post of Cedric’s It seems he doesn’t like JUnit’s test suites, and decided to write a new tool to solve his problem.

JUnit and data-driven tests

Here’s a technique I sometimes use when I’m doing test-driven development (which is my preferred coding technique). Let’s say I’ve got a bunch of test cases that are all basically the same, but they have slightly different inputs and slightly different outputs. A typical test case might look like this: