Antunit depends on HEAD. So theoretically antunit
can't be used in the wild until 1.7 is released (let's
assume "in the wild" means released components only).
Do we want to play by these rules ourselves and wait
to integrate antunit tests into Ant core until after
1.7's release, or can we go ahead and start
adding/migrating au tests?
Secondly, whenever we do integrate antunit tests into
core, a simplistic approach would be to add a new
directory, e.g. src/au-testcases whose structure might
mirror src/etc/testcases, and invoke the antunit task
from the core build in one way or another (unimportant
ATM IMO). I am thinking we might want something like:
<property name="au.tests.dir"
location="src/au-testcases" />
<au:antunit xmlns:au="antlib:org.apache.ant.antunit">
<fileset dir="${au.tests.dir}"
includes="**/*.xml"
excludes="**/*-support.xml" />
<...listener... />
</au:antunit>
I excluded *-support.xml because I thought there might
be a need for support xml files (hopefully that was
obvious), and I selected a straightforward convention.
What modifications to this strategy do others
advocate?
Finally, I think it will be best for antunit if as
many as possible of our existing junit testcases are
(eventually) ported to antunit. This should expose
any missing generic functionality IMHO.
-Matt
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
