public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Dalibor Topic <robilad@yahoo.com>
To: Mark Wielaard <mark@klomp.org>, Andrew Haley <aph@cambridge.redhat.com>
Cc: Brian Jones <cbj@gnu.org>, Stephen Crawley <crawley@dstc.edu.au>,
	John Leuner <jewel@pixie.co.za>, Alex Lau <alex@dentonlive.com>,
	kissme-general@lists.sourceforge.net,
	mauve-discuss@sources.redhat.com
Subject: Re: [Kissme-general] Re: Should I or not submit changes?
Date: Thu, 18 Jul 2002 07:07:00 -0000	[thread overview]
Message-ID: <20020718140743.27339.qmail@web10005.mail.yahoo.com> (raw)
In-Reply-To: <1026999108.6501.80.camel@elsschot>


--- Mark Wielaard <mark@klomp.org> wrote:
> Hi,
> 
> On Wed, 2002-07-17 at 16:13, Andrew Haley wrote:
> > If mauve wasn't such a pain to use and hack on I
> certainly would have
> > contributed more to it.  Dejagnu, although
> horrible in its own special
> > way, at least allows individual tests to be
> developed and used without
> > needing the framework.
> 
> I was thinking of having very simple support for
> "output comparison"
> tests. You write a bla/test.java class with a normal
> static main method
> that just prints to System.out.println and there is
> a bla/test.out file
> that contains the correct output of the test. The
> only drawback is that
> when people explicitly use Testlet.check() it is
> much more clear what it
> is they are precisely testing.

Kaffe's regression testing suite relies mostly on
output comparison. While it's a great way to create
tests in a minute, it's not that great in the end.

Sometimes the output depends on the locale you are in,
so people get erraneous failures. Sometimes people
will include toString() output in the expected
results, which is quite painful when you test for
exceptions. Unless you want to match Sun's messages
literally, of course.

In my opinion, explicit check methods that verify
single properties are more useful, as it is easier to
extract context information about failures, most
importantly which test failed. That is really hard if
something messes up your tests output beyound the
region matching capabilities of diff.

best regards,

dalibor topic

__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com

  parent reply	other threads:[~2002-07-18 14:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1026843874.3494.68.camel@bapli>
2002-07-16 17:48 ` Stephen Crawley
2002-07-16 20:05   ` Brian Jones
2002-07-17  2:32     ` Dalibor Topic
2002-07-18  6:21       ` Mark Wielaard
2002-07-18  8:06         ` Dalibor Topic
2002-07-19  3:51         ` Chris Gray
2002-07-18  6:35       ` Brian Jones
2002-07-17  7:13     ` Andrew Haley
2002-07-18  6:32       ` Mark Wielaard
2002-07-18  6:56         ` Andrew Haley
2002-07-18  7:07         ` Dalibor Topic [this message]
2002-07-17  8:33   ` Alex Lau
2002-07-17  8:49     ` Stephen Crawley
2002-07-17 12:15       ` Alex Lau
2002-07-17  9:02     ` Dalibor Topic
2002-07-18  6:26     ` John Leuner
2002-07-18  6:00   ` Mark Wielaard

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=20020718140743.27339.qmail@web10005.mail.yahoo.com \
    --to=robilad@yahoo.com \
    --cc=alex@dentonlive.com \
    --cc=aph@cambridge.redhat.com \
    --cc=cbj@gnu.org \
    --cc=crawley@dstc.edu.au \
    --cc=jewel@pixie.co.za \
    --cc=kissme-general@lists.sourceforge.net \
    --cc=mark@klomp.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).