gcc/libstdc++-v3/testsuite
Benjamin Kosnik b8f971fc25 char_traits.cc: Move to ...
2001-02-16  Benjamin Kosnik  <bkoz@redhat.com>

	* testsuite/21_strings/char_traits.cc: Move to ...
	* testsuite/21_strings/char_traits_requirements.cc: ..here.
	* testsuite/21_strings/char_traits-int_type.cc: Move to ...
	* testsuite/21_strings/char_traits_typedefs.cc: ..here.

From-SVN: r39784
2001-02-16 23:58:28 +00:00
..
17_intro
18_support
20_util
21_strings char_traits.cc: Move to ... 2001-02-16 23:58:28 +00:00
22_locale Preliminary named locales. 2001-01-30 09:18:51 +00:00
23_containers
24_iterators
25_algorithms
26_numerics
27_io ios_base_members_static.cc: Swap order of tests. 2001-02-05 22:08:47 +00:00
config default.exp: New file. 2001-02-05 02:48:17 +00:00
ext
lib libstdc++.exp (dg-test): Lift, temporarily, out of dejagnu/dg.exp. 2001-02-15 03:57:39 +00:00
libstdc++.tests
debug_assert.h
Makefile.am Makefile.am: New file. 2001-02-10 00:58:16 +00:00
printnow.c
README README: Add more comment. 2001-01-28 15:13:08 +00:00

We're in the process of converting the existing testsuite machinery to
use the new style DejaGnu framework.  Eventually, we'll abandon
../mkcheck.in in favor of this new testsuite framework.  

  Basically, a testcase contains dg-keywords (see dg.exp) indicating
what to do and what kinds of behaviour are to be expected.  New
testcases should be written with the new style DejaGnu framework in mind.

  The V3 testing framework supports additional keywords for the purpose
of easing the job of writing testcases.  All V3-keywords are of the
form @xxx@.  Currently supported keywords include:

  @require@ <files>
      The existence of <files> is essential for the test to complete
      successfully.  For example, a testcase foo.C using bar.baz as
      input file could say
	    // @require@ bar.baz
      The special variable % stands for the rootname, e.g. the
      file-name without its `.C' extension.  Example of use (taken
      verbatim from 27_io/filebuf.cc)
	   // @require@ %-*.tst %-*.txt

  @diff@ <first-list> <second-list>
      After the testcase compiles and ran successfully, diff
      <first-list> against <second-list>, these lists should have the
      same length.  The test fails if diff returns non-zero a pair of
      files.

-- Gaby