From: Dalibor Topic <robilad@kaffe.org>
To: David Gilbert <david.gilbert@object-refinery.com>
Cc: mauve-discuss@sourceware.org,
mauve-patches <mauve-patches@sources.redhat.com>
Subject: Re: Running Mauve tests with JUnit
Date: Wed, 08 Mar 2006 19:07:00 -0000 [thread overview]
Message-ID: <1141848446.4929.16.camel@localhost> (raw)
In-Reply-To: <440EDA60.10802@object-refinery.com>
On Wed, 2006-03-08 at 13:21 +0000, David Gilbert wrote:
> Hi Dalibor,
>
> I had meant to keep this on the Mauve lists, but I'll reply to the
> Classpath list also...
>
Sorry about the cross-posting :/ I've taken the classpath list out
again.
> I hadn't seen Graydon's bridge class, thanks for the link (and I should
> do more research next time). Looking over it, it has the advantage that
> it doesn't require any existing Mauve testlets to be modified (and we
> have a lot of testlets), but the disadvantage that it doesn't buy you
> much in terms of integration with IDEs (you still have to generate the
> test list ['classes'] file, for instance, which is the major stumbling
> block that people seem to have when trying to run Mauve).
OK, thanks for the explanation. I wasn't familiar with Graydon's code
either, just remembered it was sitting in my mail box.
> By modifying the Mauve testlets in the way that I proposed, you can (for
> example) run a single test in Eclipse just by selecting the source file
> and clicking 'Run as --> JUnit test'. I figured that was the sort of
> thing people were expecting.
That sounds very cool.
Would it be possible to make that work without having to modify the
existing tests, by (just trowing random ideas here) using a proxy to
delegate to the junit Test runner, and having Testlet implement both the
junit.Test interface and the Testlet interface?
(I assume that a Junit test is recognized by an IDE by looking whether a
class implements the junit.Test interface? Or do IDEs look for a class
extending TestCase/TestSuite? I don't use IDEs much, so I hope the
questions are not too stupid.)
> Agreed. I didn't have much trouble getting the tests to compile against
> the freenet code (a basic GPLed implementation of the JUnit API for
> those that don't know what it is) but didn't get any meaningful output
> from running the tests against it yet. I don't think that will be too
> hard to resolve.
Great, thanks for looking at that code. Sounds like it should be good
enough for the basic needs.
cheers,
dalibor topic
prev parent reply other threads:[~2006-03-08 19:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 17:05 David Gilbert
2006-03-08 10:40 ` David Gilbert
2006-03-08 11:08 ` Michael Koch
[not found] ` <20060308120721.GA7569@pogo.kaffe.org>
2006-03-08 13:21 ` David Gilbert
2006-03-08 19:07 ` Dalibor Topic [this message]
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=1141848446.4929.16.camel@localhost \
--to=robilad@kaffe.org \
--cc=david.gilbert@object-refinery.com \
--cc=mauve-discuss@sourceware.org \
--cc=mauve-patches@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).