Re: libstdc++ testing using DejaGnu

[Phil Edwards]

On Tue, Oct 28, 2003 at 01:02:47PM -0600, George Kraft wrote:
> 1) What is the libstc++ testsuite code coverage?

*shrug*  Not all of it.


> What are the goals?

All of it.


> 2) Is there an easy way to build the tests so the binary images can be
> packaged up to run on other machines?

No, not really.  Since most of the library exists as template code, it's
the compilation and linking steps that are doing most of the testing.
Doing this wouldn't be impossible, but dejagnu isn't designed for it.

There are a growing number of binary compat tests, but I don't think
this method is one of them.


> 2b) In /usr/share/dejagnu/dg.exp I wanted to pass -keep-output to
> dg-test, but I could not figure it out so I hard coded it. :-)

I seem to remember doing something similar.  DejaGNU is remarkably
un-tweakable in places.  Anything described in the output of "runtest
--help" can be added to the RUNTESTFLAGS variable (passed either in the
environment, or on the 'make' command line), but I don't think this is
one of those things.


> 3) How can I get DejaGnu to run binary images that I have created above
> and not try to build the tests from source?

Rewrite large chunks of DejaGNU, both in the installation and in the
libstdc++ config files.

Sorry to sound flip, but DG just isn't that flexible.  I tried once to
/only/ build the tests, and /not/ run any of the resulting binaries,
and it was wasted effort.

-- 
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
    - Brian W. Kernighan