public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: Testing frysk.testbed.Funit*
Date: Tue, 31 Jul 2007 10:03:00 -0000	[thread overview]
Message-ID: <1185876171.3653.64.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <46AE081A.8070503@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

Hi Andrew,

On Mon, 2007-07-30 at 11:47 -0400, Andrew Cagney wrote:
> I'm looking at ways to more directly test the frysk.testbed.Funit* 
> classes (e.g., FunitExec, DetachedAckProcess) that wrap 
> PKGLIBDIR/funit-* utilities, but am finding that the most effective 
> route is to use frysk.proc's framework - duplicating the existing 
> frysk.proc tests exercising frysk.proc functionality that is effectively 
> testing that code.
> 
> I could duplicate the tests but it seems redundant.  Any thoughts on a 
> strategy?

I might be missing the exact cases you want to test. But can't you just
audit the current frysk.proc tests to see if they cover all relevant
cases already and if not add one or two tests to the existing proc tests
so all cases are covered? That way you will also extend the real proc
tests to handle more cases catching two birds with one stone (if that
isn't a terribly political incorrect saying).

Cheers,

Mark

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-31 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 15:47 Andrew Cagney
2007-07-31 10:03 ` Mark Wielaard [this message]
2007-07-31 15:57   ` Andrew Cagney
2007-08-02  8:12     ` 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=1185876171.3653.64.camel@dijkstra.wildebeest.org \
    --to=mark@klomp.org \
    --cc=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    /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).