mirror/gcc
2
0
Fork 0
mirror of git://gcc.gnu.org/git/gcc.git synced 2024-12-18 10:39:09 +08:00
Code Issues Packages Projects Releases Wiki Activity
0ba434e0f8
gcc/libstdc++-v3/testsuite
History
Gabriel Dos Reis 0ba434e0f8 default.exp: New file. 
* testsuite/config/default.exp: New file.
        * testsuite/config: New directory.

From-SVN: r39447
2001-02-05 02:48:17 +00:00
..
17_intro 17_intro: Prepare testcases for new style DejaGnu framework. 2001-01-19 02:52:27 +00:00
18_support
20_util auto_ptr.cc (test07): Remove test that tries to copy-initialize an auto_ptr<Base> from an... 2000-12-10 06:23:50 -05:00
21_strings inserters_extractors.cc: Remove explicit reference to 'testsuite/'. 2001-01-26 23:31:57 +00:00
22_locale Preliminary named locales. 2001-01-30 09:18:51 +00:00
23_containers acinclude.m4, [...]: Change sourceware.cygnus.com and sources.redhat.com URLs for libstdc++ web... 2000-12-21 22:08:39 +00:00
24_iterators
25_algorithms acinclude.m4, [...]: Change sourceware.cygnus.com and sources.redhat.com URLs for libstdc++ web... 2000-12-21 22:08:39 +00:00
26_numerics
27_io *.cc: Remove explicit reference to 'testsuite/' in testcases. 2001-01-25 04:09:22 +00:00
config default.exp: New file. 2001-02-05 02:48:17 +00:00
ext
lib README: Add more comment. 2001-01-28 15:13:08 +00:00
libstdc++.tests tests.exp: New file. 2001-01-20 05:09:08 +00:00
debug_assert.h
printnow.c
README README: Add more comment. 2001-01-28 15:13:08 +00:00

README 

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