Re: Power of the G++ test suite

[Ben Scherrey <scherrey at gte dot net>]

I'd be willing to provide some test code for both the std C++ class lib
and ANSI compliant aspects of the language itself. BUT - to do this we
need some way of tracking/organizing these tests. Although I'm not
thrilled with the DeJaGNU product, I guess it would be the easiest for
us to integrate with egcs. If we could build an "outline" document or
database framework that references each item in the ANSI spec, then
associate test code samples with those items, we could see what areas
still need tests. I envision some sort of html mechanism that can be
publically updated. Any one have an idea on how to set this up?

	regards,

		Ben Scherrey	

Joe Buck wrote:
> 
> > FWIW I just check into it and Plum Hall charges $20K for their
> > testsuite!! 
>	<some snipped>
> I suspect that part of the reason they charge so much is that there are
> so few customers (only compiler vendors and a few others).  It's not
> exactly exciting work, so getting hackers to donate their time isn't
> as easy as for something cooler.
> 
> > but building a more public version of these test
> > cases would be a great benifit.
> 
> You can contribute tests to improve the existing test suites.  Any
> contributed tests should hopefully be non-overlapping with what is already
> there.
> 
> One type of test that shouldn't be hard for people out there to build and
> contribute is libstdc++ tests.  Write a program that exercises all of the
> methods of some standard class.  If the class is a template, the test
> can instantiate it for a builtin type as well as a class.