Stefan Bodewig wrote:
3. enhancements to junit
-a method "isFailure" on the assertion failure classes, for
checking (through reflection in ant) for failures vs errors.
Yes, that would be handy. But they shouldn't have dropped the
difference between errors and failures in the first place.
Whatever you think of the decision to drop that distinction (personally
I am on the fence about it), the job of the task is to provide a wrapper
for the tool the way it is intended to be used, so for junit4 that means
report output should not differentiate between the two.
I *did* include differentiation in the patch I did in Ant head. But that
is only because the existing junit3-based reporting framework counts
failures and errors separately, and it would be confusing for one or the
other column to always be zero.
-J.
--
[EMAIL PROTECTED] x22801 netbeans.org ant.apache.org
http://google.com/search?q=e%5E%28pi*i%29%2B1
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
