Stefan Bodewig wrote:
In accordance with section 4.6 of the antlibs subproject charter, an
antlib needs a PMC majority to be accepted as a "proper" antlib.
Majority means at least 3 +1s and more +1s than -1s (section 4.7).
Each Antlib also needs at least three committers with at least one PMC
member among them. If you vote in favor of the promotion, please
indicate whether you want to become a committer on the antlib.
This is the vote for the antunit antlib that can be found in the
sandbox/antlibs/antunit subdirectory. This lib provides an antunit
task that runs build files as unit tests as well as a bunch of
assertion tasks and a simple listener in the style of the plain JUnit
formatter.
The concept of build files as unit tests was inspired by seeing Steve
and Matt use it in Ant's core - where the JUnit testcase only became
the driver and all assertions happened in the build file itself.
And now I'm looking at what you did in AntUnit and trying to think how
you apply the same pattern to testing in and of distributed applications:
http://cvs.sourceforge.net/viewcvs.py/*checkout*/deployment/deployment/doc/testing/test-components.doc
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
