Glenn Adams <> changed:

           What    |Removed                     |Added
           Priority|P2                          |P3
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #2 from Glenn Adams <> ---
I agree with Jeremias on this, and further, that something else needs to be
done to better report the failing test without having to do something special
(i.e., switching a DEBUG boolean).

I reported this problem just after JUnit 4 was adopted, and I seem to recall
that Mehdi was going to look into a better solution. FWIW, when I encounter
this problem, I've been using Eclipse to catch the assert, which then allows
one to discover the culprit by walking up the stack a few levels.

In any case, I'm reopening this (as P3) as I'd like to see a better, long-term

You are receiving this mail because:
You are the assignee for the bug.

Reply via email to