In JUnit 4.1, if an assertion failure occurs in a tear-down method it will mask any failure that occurred in the test case itself. There is no real work-around for this problem other than commenting out the assertion in the tear-down method.
... until the collector arrives ...
This "blog" is really just a scratchpad of mine. There is not much of general interest here. Most of the content is scribbled down "live" as I discover things I want to remember. I rarely go back to correct mistakes in older entries. You have been warned :)
