Re: generating type tests

[Stan Cox <scox@redhat.com>]

I think this reworking implements the contract we discussed in the
meeting.  gen-type-funit-tests.py builds funit-type-expect.c with type
annotations of the form:
// Test: <name to be given to a "suite" (one test in expect parlance)>
// Name: <variable name>
// Value: <initial value of variable>
// Type: <type as specified in a source program>
// EType: <expanded type as if the typedef were expanded>
gen-type-expect-tests.py builds TestTypeEntry*.java from, for example
funit-type-expect.c, using the type annotations.  Multiple files can be
given so types can be specified standalone outside of the
gen-type-funit-tests.py framework.  This will result in
TestTypeEntry*.java having the form:
    public void testScalar () {
        Expect [] expect  = {...}
      ExpectTest expectTest = new ExpectTest("funit-type-entry");
      expectTest.compareEqual(expect, "testScalar ");
    }
    // testArray/testStruct/testEnum, all generated by 
    // gen-type-funit-tests.py
    public void testAlpha () {
        Expect [] expect  = {
            new Expect("char_var","char"),
        }
      ExpectTest expectTest = new ExpectTest("x");
      expectTest.compareEqual(expect, "testScalar ");
    }
testAlpha is generated from x.c via:
gen-type-expect-tests.py -type funit-type-entry.c x.c
from this x.c:
// Test: Alpha
static char char_var = 176;
// Name: char_var
// Value: 176
// Type: char
main (int argc, char **argv)
{}

The "Type" testing passes for those types currently being generated by
gen-type-funit*. Here is a run of TestRunner done with the assistance of
some makefile surgery.
Running testScalar(frysk.debuginfo.TestTypeEntry)
PASS
Running testArray(frysk.debuginfo.TestTypeEntry)
PASS
Running testStruct(frysk.debuginfo.TestTypeEntry)
PASS
Running testEnum(frysk.debuginfo.TestTypeEntry)
PASS

Time: 0.21

OK (4 tests)