.xml already exists. This is used for fix/build/test cycles prior to committing changes to the repository. - Both features may be made confifurable and/or optional, as they may not be needed by everybody. - I started implementing only my features, as it first looked like beside Stefan Bodewig nobody is interested in this. It looks like I was wrong, great. =A0 =A0 TODO - provide a specialiced classloader to extend the classpath at runtime differently for every junit task. - in addition to the XML output provide ASCII output. - I am not 100% happy with the XML structure, but it is fine right now. - Docu =A0 =A0 As long as it JUnit is not part of ant, I will collect patches and submit them to the list. =A0 Let me know, what you think. - tom =A0 =A0 ------ =_NextPart_001_01BFE041.ED98BFD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi All,

I am quite new in ANT/JUnit programming but I = think it is a=20 great idea to have Unit Testing framework (JUnit), which runs = automatically=20 using ANT.

So I have a suggestion concerning Thomas’s = realization of=20 JUnitTask. I think it will be very helpful to derive JUnitTask from MatchingTask (not = from Task).=20 It will give us the possibility to specify what files we are going to = test.

For example: we have a bunch of test classes, lets = say=20 _t*.class. Using MatchingTask it is possible to perform recursive, = automated ANT=20 TEST through the entire tree of classes.

Is this idea worth to work out or is it already = implemented=20 in some other way?

Thanks,

Konstantin.

-----Original Message-----
From: Thomas Haas=20 [mailto:thomas.haas@softwired-inc.com]
Sent: Wednesday, = April 19,=20 2000 4:09 PM
To: = ant-dev@jakarta.apache.org
Subject: JUnit=20 task and friends

Upon request a snapshot of the = current JUnit task=20 is provided.

Except Path.java everything resides = in the=20 optional package for now. The development got stuck due to the = current=20 discussion about the future design of ant. The JUnit task needs a = proposal to=20 replace Exec with a more extensible and reusable version offering = various=20 other feattures (see OExec.java).

NOTE

- This version writes the output to=20 RUNNING-TEST-<testname>.xml. The file is renamed to=20 TEST-<testname>.xml on success and ERROR-<testname>.xml = on=20 failure. This has been done to be compatible with our old, makefile = based=20 build system and will be obsolete, once the backends are converted to = XML.

- Tests are not run if a file=20 TEST-<testname>.xml already exists. This is used for = fix/build/test=20 cycles prior to committing changes to the repository.

- Both features may be made = confifurable and/or=20 optional, as they may not be needed by everybody.

- I started implementing only my = features, as it=20 first looked like beside Stefan Bodewig nobody is interested in this. = It looks=20 like I was wrong, great.

TODO

- provide a specialiced classloader = to extend the=20 classpath at runtime differently for every junit task.

- in addition to the XML output = provide ASCII=20 output.

- I am not 100% happy with the XML = structure, but=20 it is fine right now.

- Docu

As long as it JUnit is not part of = ant, I will=20 collect patches and submit them to the list.

Let me know, what you think.
- tom

------ =_NextPart_001_01BFE041.ED98BFD0--