[v3] Refined test instrument for container tests

Stephen M. Webb stephen.webb@bregmasoft.com
Wed Jan 9 11:50:00 GMT 2002


On January 9, 2002 02:13 pm, Benjamin Kosnik wrote:
> > I moved my countable class out of list_modifiers.cc and into its
> > own header so I can reuse it in additional testsuite entries.
>
> Which other testsuite entries would you like to use it with?
> Something like this is probably a good idea, to reduce the
> duplication in some of the testsuite code.

Um, in particular the ones sitting on my hard drive undergoing 
refinement.  I've slowly been working on a bunch of 23_containers tests 
like the list_* ones.

> What do you think about a testsuite/util, or some sub-directory
> differently named, for this and the timer code?

I think it's a good idea, since at least for the timer code we may need 
a linkable library and we might want to avoid littering the testsuite 
directory with proliferating source files.  We would also need a 
separate test suite for the test suite support code to avoid GIGO.

I'm not sure if the timer stuff, which is benchmarking, should be 
lumped together with the testsuite, which is validation.  The testsuite 
verifies the library is correct, the benchmarking assumes correctness 
and documents efficiency.  Perhaps the whole benchmarking thing should 
be a separate directory heirarchy off libstdc++-v3?

__
Stephen M. Webb



More information about the Libstdc++ mailing list