ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Stirling" <scottstirl...@rcn.com>
Subject RE: [PATCH] JUnit optional task - stack trace filtering
Date Sat, 08 Dec 2001 03:25:21 GMT
> -----Original Message-----
> From: Steve Loughran [mailto:steve_l@iseran.com]

> What would the effect of this change be on automated tests systems?
> Filtering needs to be off by default so anything which tries to interpret
> the trace now wont break.

I take it you mean the Jakarta build systems?  It doesn't affect the functionality of things
like haltonfailure or haltonerror, or
anything else except the format of reports.  And it does not filter out lines with junit.framework.AssertionFailedError,
nor does it
filter with the BriefJUnitResultResultFormatter, which is what's currently used in the Ant
build.  I never use the brief formatter,
so I didn't change it.  I could though (should have).

I'm glad you asked, because I just ran the Ant unit tests and found a compiler error that
needs to be fixed in the
JUnitTestRunnerTest because I changed the constructor signature for JUnitTestRunner.

I just made the same filtering modification to the brief formatter and fixed the JUnit test
case and am going to resubmit a new
patchfile in a minute.

Best,

Scott Stirling
Framingham, MA

>
> -steve


--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message