-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thomas Fitzsimmons wrote: > Hi, [...] > 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[0] 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 xdoclet). 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! [0] http://testng.org/doc/ - -- Arnaud Vandyck ,= ,-_-. =. ((_/)o o(\_)) `-'(. .)`-' \_/ 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 iD8DBQFEHok24vzFZu62tMIRAmOoAJ9VI7oH+83wQ+FPJhvQjDfPNK+KFACbB5DS w3SFrZtDNCcjPNGEzJlDQLE= =7YEE -----END PGP SIGNATURE-----
