ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <>
Subject Re: A consice ouput for failed JUint task
Date Mon, 04 Mar 2002 01:26:22 GMT

----- Original Message -----
From: "Yiu Wing" <>
To: "Ant Users List" <>
Sent: Sunday, March 03, 2002 3:46 PM
Subject: Re: A consice ouput for failed JUint task

> > An enhancement was made to reduce the stack trace to only the non-JUnit
> > classes.  It is part of the CVS codebase and nightly builds of 1.5alpha.
> >
> > Is that the output you want reduced?  If not, send us the output you're
> not
> > liking.
> Hi Erik,
> Thanks for the response.  Yeah, I've found the output too verbose and
> like it to be reducued.  I'm not very interested in the stack trace for
> JUint classes, probably most people aren't, either.  Sometimes I get quite
> fracstrated to figure out where exactly the test fails from the output.

name your test cases more meaningfully and do less per test. If you have
commonality in tests, refactor it out.

its much easier to deal with testUpdateToDBofOddNumber() failed than
testDB() failure

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message