From: Chris Abbey <jikes@cabbey.net>
To: Mauve News Group <mauve-discuss@sources.redhat.com>
Subject: Re: virtual machine tests
Date: Wed, 27 Oct 2004 03:37:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0410261735450.15652-100000@tweedle.cabbey.net> (raw)
In-Reply-To: <m3sm81dqko.fsf@localhost.localdomain>
Today, Tom Tromey wrote:
> My current plan is to make a new Mauve module called "vm", and put
> tests there. Of the many test frameworks we have at the moment, I
> find jacks is the easiest to work with (and most appropriate for this
> kind of testing), so I think I will just copy that framework and use
> it. Eventually I'd like to move the verifier tests here as well.
There are a handfull of tests in Jacks now that could probably move
over to this new section. (look for the jvm constraint for the ones I'm
thinking of.)
--
Never make a technical decision based upon the politics of the situation.
Never make a political decision based upon technical issues.
The only place these realms meet is in the mind of the unenlightened.
-- Geoffrey James, The Zen of Programming
prev parent reply other threads:[~2004-10-27 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 23:10 Tom Tromey
2004-10-26 23:32 ` Dalibor Topic
2004-10-27 3:37 ` Chris Abbey [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=Pine.LNX.4.33.0410261735450.15652-100000@tweedle.cabbey.net \
--to=jikes@cabbey.net \
--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).