This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] testsuite/gcc.test-framework to check test directives

On Thu, Jan 27, 2005 at 11:39:05AM +0000, Joseph S. Myers wrote:
> On Wed, 26 Jan 2005, Janis Johnson wrote:
> > > Would the framework for testing the testsuite infrastructure obsolete the 
> > > present tests gcc.misc-tests/dg-*?
> > 
> > I hadn't realized those tests were there; does anyone use them?
> I don't know if they are used, but there is or was a wish to get rid of 
> gcc.misc-tests and those tests seem like something that should be subsumed 
> in a general framework for testing whether a test harness produces the 
> expected results.

Several of the dg-* tests were very out-of-date and I've fixed them.
They've been renamed to include the expected result in the test name,
like the generated tests.  In some cases I split them apart to make it
easier to verify that particular directives got the right results.  The
awk script now recognizes a few more exceptions, and prints a
familiar-looking summary at the end:

		=== Test Framework Summary ===
# of expected passes		2487
# of unexpected failures	0

I'll submit the modified tests after deciding on a few key things:

  - Where should these tests go?  testsuite/gcc.test-framework was the
    original proposal, but they could just as easily be a subdirectory
    of gcc.dg, which now has quite a few subdirectories.

  - Any objections to the name gcc.test-framework?

  - Any objections to enabling these tests with an environment variable?

I'll just fake it if I don't hear from anyone.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]