public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Stan Cox <scox@redhat.com>
To: Frysk List <frysk@sourceware.org>
Subject: Re: [SCM]  master: Emit one test per variable.
Date: Tue, 04 Dec 2007 15:26:00 -0000	[thread overview]
Message-ID: <1196781616.10805.56.camel@multics.rdu.redhat.com> (raw)
In-Reply-To: <4755699A.5070809@redhat.com>


> Wicked, we can now see exactly what variable tests are being run here; 
> and easily re-run just the ones that fail.
> Andrew


"python <SRCDIR>/frysk-core/frysk/debuginfo/gen-type-expect-tests.py
-help" gives a brief description of how to add a test.  I'll flesh that
out a bit.  There are two ways to add a test. 
1. The first method is make a test builtin using
<SRCDIR>/frysk-core/frysk/pkglibdir/gen-type-funit-tests.py.  This
generates <BLDDIR>/frysk-core/frysk/pkglibdir/funit-type-entry.c.  
2. A second simpler method to add a test is to use specially formatted
comments.  For example notice that
<SRCDIR>/frysk-core/frysk/pkglibdir/funit-class.cxx has comments which
tell gen-type-expect-tests.py what should be checked.  When
gen-type-expect-tests.py runs it knows to pick these up from
funit-class.cxx because that is described
in /debuginfo/TestTypeEntry.java-sh.

A shortcut to try out an added test passes is to do:
rm -frysk/pkglibdir/funit-type-entry.* frysk/debuginfo/*.java
make ./TestRunner
./TestRunner  frysk.debuginfo.TestTypeEntry


      reply	other threads:[~2007-12-04 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071204004717.621.qmail@sourceware.org>
2007-12-04 14:52 ` Andrew Cagney
2007-12-04 15:26   ` Stan Cox [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=1196781616.10805.56.camel@multics.rdu.redhat.com \
    --to=scox@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).