Index: docs/html/test.html =================================================================== RCS file: /cvs/gcc/gcc/libstdc++-v3/docs/html/test.html,v retrieving revision 1.1 diff -u -r1.1 test.html --- docs/html/test.html 20 May 2003 22:25:09 -0000 1.1 +++ docs/html/test.html 21 May 2003 09:59:10 -0000 @@ -50,7 +50,7 @@ the C++ standard, and each containing test files or subdirectories of test files that test for that particular part of the standard. -
+
17_intro @@ -97,7 +97,7 @@ was named accordingly. For instance, to test items related to21.3.6.1 - basic_string::find [lib.string::find]
in the standard, the following was used: -+
21_strings/find.cc@@ -142,11 +142,11 @@ This test case expects some kind of interactive input in order to finish or pass. At the moment, the interactive tests are not run by default. Instead, they are run by hand, like: +g++ 27_io/objects/char/3_xin.cc cat 27_io/objects/char/3_xin.in | a.out-
You can check the status of the build without installing it using the dejagnu harness, much like the rest of the gcc tools.
--
make checkin the libbuilddir directory. +
make check+
in the libbuilddir directory.
or
-make check-target-libstdc++-v3in the - gccbuilddir directory. +
make check-target-libstdc++-v3+
in the gccbuilddir directory.
These commands are equivalent and will create a 'testsuite' @@ -476,7 +476,7 @@
In addition, there are some testing options that are mostly of interest to library maintainers and system integrators. As such, these tests may not work on all cpu and host combinations, and must - be executed in the libbuilddir directory.
These options + be executed in the libbuilddir directory. These options include, but are not necessarily limited to, the following: @@ -530,25 +530,38 @@
The V3 testing framework supports, or will eventually support,
additional keywords for the purpose of easing the job of writing
-test cases. All V3-keywords are of the form @xxx@. Currently plans
-for supported keywords include:
+test cases. All V3-keywords are of the form @xxx@
.
+Currently plans for supported keywords include:
@require@ <files>
+ The existence of <files> is essential for the test to complete successfully. For example, a test case foo.C using bar.baz as input file could say - // @require@ bar.baz +
++ // @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@
+ // @require@ %-*.tst %-*.txt+
@diff@ <first-list> <second-list>
After the test case compiles and ran successfully, diff
-