ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <stev...@iseran.com>
Subject Re: junit behavior in ant 1.5 vs 1.3
Date Sat, 22 Feb 2003 00:14:43 GMT
what, you mean it is coming from someone in a place of learning and
therefore perhaps more up to date with what is state-of-the art in computer
science ?

Some of my apps do chuck out stuff in the unit tests, but that is solely a
consequence of the log4j settings, and nobody cares about them. The key
point about unit tests is that the interpretation and the analysis should be
automated.

you might think the text is there for analysis on failures, but my
best-practise for a failure is 'refine the test' -add new tests and drill
down to find the problem through improved unit tests, not classic single
step debugging or the like. Why? Because more and better tests add more long
term value than time spent in a debugger.

----- Original Message -----
From: "Mike Ayers" <mayers@NEVIKNETWORKS.com>
To: "Ant Users List" <user@ant.apache.org>
Sent: Friday, February 21, 2003 14:55
Subject: RE: junit behavior in ant 1.5 vs 1.3



> From: M. Erik Husby [mailto:mhusby@genome.wi.mit.edu]
> Sent: Friday, February 21, 2003 10:48 AM

> Of course this is not the JUnit mailing list and so this is a
> little off topic. But I can't
> help wondering why your unit tests are writing anything to
> System.out at all.

It should surprise nobody that this comment came from a ".edu" address...


/|/|ike

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org



Mime
View raw message