This is the mail archive of the
mailing list for the Mauve project.
Re: Mauve wishlist
- From: Arnaud Vandyck <avdyk at gnu dot org>
- To: classpath at gnu dot org
- Cc: mauve-discuss at sources dot redhat dot com
- Date: Mon, 20 Mar 2006 11:51:35 +0100
- Subject: Re: Mauve wishlist
- References: <1142613140.3805.20.camel@rh-ibm-t41>
-----BEGIN PGP SIGNED MESSAGE-----
Thomas Fitzsimmons wrote:
> There is also lots of room for improvement in how Mauve tests are
> selected and run. I'm hoping someone who better understands Mauve's
> design will elaborate.
I had a very quick look at TestNG and I think it could be a good
approach: no need to change the mauve test classes, just invoke the
tests with TestNG. There is an eclipse plugin that display the running
tests like JUnit.
TestNG use a tag feature like we have in mauve (JDK1.1, JDK1.2, ...) and
we can add other groups like swing, nio, etc. Those tags can be
annotations or javadoc comments (with @ and I think it's processed with
As I understood (but I did not read all the documentation), the very big
advantage Mauve can take in adopting TestNG (vs JUnit?) is that we
shouldn't have to re-write all the test cases!
,= ,-_-. =.
Java Trap: http://www.gnu.org/philosophy/java-trap.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----