From: David Daney <ddaney@avtrex.com>
To: Thomas Fitzsimmons <fitzsim@redhat.com>
Cc: classpath@gnu.org, mauve-discuss@sources.redhat.com
Subject: Re: Mauve wishlist
Date: Fri, 17 Mar 2006 21:06:00 -0000 [thread overview]
Message-ID: <441B24D8.30304@avtrex.com> (raw)
In-Reply-To: <1142613140.3805.20.camel@rh-ibm-t41>
Thomas Fitzsimmons wrote:
> Hi,
>
> Anthony Balkissoon has expressed interest in improving Mauve so we'd
> like to know what would be the best things to work on.
>
> Here are two items on my list:
>
> - A web reporting facility that generates JAPI-style bar graphs.
> Ideally the graphs would represent a code-coverage analysis but I have
> no idea how feasible that is using free tools.
>
> - A framework for testing VM invocations and the tools' command-line
> interfaces -- in other words, a framework that can exec commands. This
> may be best done as an independent module, separate from Mauve.
>
> 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 would like to see a way to partition the different tests. Sometimes
mauve will not build for gcj (and probably other compilers as well)
because just a single file has some problem. It would be nice to still
be able to run the majority of the tests in this situation.
I also thought about running different groups of tests in their own
ClassLoader, but cannot really think of a good reason right now to do it.
David Daney
next prev parent reply other threads:[~2006-03-17 21:06 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 [this message]
2006-03-18 8:15 ` Michael Koch
2006-03-17 22:34 ` Audrius Meskauskas
2006-03-20 10:53 ` Arnaud Vandyck
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=441B24D8.30304@avtrex.com \
--to=ddaney@avtrex.com \
--cc=classpath@gnu.org \
--cc=fitzsim@redhat.com \
--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).