From: Arnaud Vandyck <avdyk@gnu.org>
To: classpath@gnu.org
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Mauve wishlist
Date: Mon, 20 Mar 2006 10:53:00 -0000 [thread overview]
Message-ID: <441E8937.4030205@gnu.org> (raw)
In-Reply-To: <1142613140.3805.20.camel@rh-ibm-t41>
-----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-----
next prev parent reply other threads:[~2006-03-20 10:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 16:27 Thomas Fitzsimmons
2006-03-17 21:06 ` David Daney
2006-03-18 8:15 ` Michael Koch
2006-03-17 22:34 ` Audrius Meskauskas
2006-03-20 10:53 ` Arnaud Vandyck [this message]
2006-03-20 16:51 ` Anthony Balkissoon
2006-03-21 16:58 ` David Gilbert
2006-03-21 22:24 ` Tom Tromey
2006-03-21 23:08 ` Bryce McKinlay
2006-03-22 11:12 ` David Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=441E8937.4030205@gnu.org \
--to=avdyk@gnu.org \
--cc=classpath@gnu.org \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).