ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Magesh Umasankar" <>
Subject [SUBMIT][PATCH]RE: "Test Skeleton Generator" follow up
Date Tue, 12 Jun 2001 21:22:31 GMT
Since this task hasn't been committed till now, I have just attached the newer version instead
of a diff.

I have made changes to the previously submitted code so that performance is increased.  Only
those class files that have no corresponding Test Skeleton fileor where the Skeleton file
is older than the class file will be parsed for modifications - much like how javac determines
which java files are to be included for compilation.

I have experienced significant time savings as a result of this patch.

I have also modified the documentation to reflect the change.


------------- Original Message --------------
"Chris Greenlee" <> wrote:
From:"Chris Greenlee" <>
Date:Tue, 12 Jun 2001 08:49:17 -0500
Subject: RE:  "Test Skeleton Generator" follow up

Actually, this seems like a very useful utility.  Not being a committer,
I have no say whether it goes into the product, but I wouldn't be upset
to see it added to the unit testing tasks within ant.

Chris Greenlee

> -----Original Message-----
> From: Magesh Umasankar []
> Sent: Friday, June 01, 2001 1:12 PM
> To:
> Subject: "Test Skeleton Generator" follow up
> I had submitted a task about a week back=20
> (
> 6330.html)
> Since nothing was mentioned about it, I was wondering if any=20
> of the committers think would be a useful task to maintain=20
> for 'people out there'.
> I use this task in the following way:
> The build compiles the Java source files first. This=20
> compilation task is followed by creation/updation of Unit=20
> Test Source Code. If new classes/new methods have been=20
> checked in without any matching unit test case code, the=20
> JUnitSkeletonGen task catches this and inserts skeleton test=20
> methods into the Unit Test files (which fail by default).=20
> This task is followed compilation of the Test cases, which is=20
> followed by execution of the test cases.
> Naturally, if a developer has checked in some code without=20
> relevant unit test cases, the tests will fail, letting the=20
> developer know that it needs to be 'fixed' by writing the Unit Test.
> Opinions?
> Thanks,
> Magesh
> _____________________________________________________
> Chat with your friends as soon as they come online. Get Rediff Bol at

Chat with your friends as soon as they come online. Get Rediff Bol at

View raw message