public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Stephen Crawley <crawley@dstc.edu.au>
To: yan.georget@koalog.com
Cc: mauve-discuss@sources.redhat.com
Subject: Re: Mauve Code Coverage
Date: Thu, 26 Jun 2003 01:04:00 -0000	[thread overview]
Message-ID: <200306260028.h5Q0SUSa026353@piglet.dstc.edu.au> (raw)
In-Reply-To: Message from Yan Georget <yan.georget@koalog.com>  of "Wed, 25 Jun 2003 19:49:22 +0200." <200306251949.22868.yan.georget@koalog.com>


> Anyway, my email concerns code coverage. Do you compute the code coverage of 
> your test suites?

AFAIK, no we don't.

> At Koalog, we have developped a powerful code coverage computation tool 
> (http://www.koalog.com/php/kover.php). 
> You can download an evaluation version. 
> If you like it, and since you are an open-source project, we could grant you 
> the right to use it with no restrictions.
> 
> Let me know what you think.

I think this is a good idea in principle.  But a better idea would be
for you to run the coverage tool on Mauve/Classpath/some VM and post the
results.  If you could set something up to do this automatically, that
would be even better!

Another point is that coverage testing will only really help if people
volunteer to write good test cases to fill in the gaps.

Finally, coverage testing won't tell us about test cases that are incorrect;
e.g. ones that test for implementation specific behavior, or ones that don't
work against various Sun JDK's.  In other words, Mauve's limitations are not
just restricted to coverage.

-- Steve


  reply	other threads:[~2003-06-26  1:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 18:32 Yan Georget
2003-06-26  1:04 ` Stephen Crawley [this message]
2003-06-26  8:53   ` Yan Georget
2003-06-26 11:20     ` Brian Jones
2003-06-26 15:14     ` Stephen Crawley
2003-06-26 17:36       ` Yan Georget
2003-06-26 21:11         ` Tom Tromey
2003-06-26 23:42           ` Stephen Crawley
2003-06-26 14:43 ` Mark Wielaard
     [not found] ` <200306261718.08841.yan.georget@koalog.com>
     [not found]   ` <1056642476.3658.109.camel@elsschot>
2003-06-26 16:13     ` Yan Georget
2003-06-26 23:07       ` Dalibor Topic

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=200306260028.h5Q0SUSa026353@piglet.dstc.edu.au \
    --to=crawley@dstc.edu.au \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=yan.georget@koalog.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).