From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2624 invoked by alias); 4 Dec 2007 15:26:57 -0000 Received: (qmail 2596 invoked by uid 22791); 4 Dec 2007 15:26:56 -0000 X-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 04 Dec 2007 15:26:52 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.1) with ESMTP id lB4FQoiJ002280 for ; Tue, 4 Dec 2007 10:26:50 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lB4FQnXQ005264 for ; Tue, 4 Dec 2007 10:26:49 -0500 Received: from [172.16.57.153] (multics.rdu.redhat.com [172.16.57.153]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id lB4FQnrf029674 for ; Tue, 4 Dec 2007 10:26:49 -0500 Subject: Re: [SCM] master: Emit one test per variable. From: Stan Cox To: Frysk List In-Reply-To: <4755699A.5070809@redhat.com> References: <20071204004717.621.qmail@sourceware.org> <4755699A.5070809@redhat.com> Content-Type: text/plain Date: Tue, 04 Dec 2007 15:26:00 -0000 Message-Id: <1196781616.10805.56.camel@multics.rdu.redhat.com> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 (2.10.3-4.fc7) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q4/txt/msg00206.txt.bz2 > Wicked, we can now see exactly what variable tests are being run here; > and easily re-run just the ones that fail. > Andrew "python /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 /frysk-core/frysk/pkglibdir/gen-type-funit-tests.py. This generates /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 /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