diff options
Diffstat (limited to 'libstdc++-v3/doc/html/manual/test.html')
| -rw-r--r-- | libstdc++-v3/doc/html/manual/test.html | 254 |
1 files changed, 198 insertions, 56 deletions
diff --git a/libstdc++-v3/doc/html/manual/test.html b/libstdc++-v3/doc/html/manual/test.html index 80988a4..ce8fa2a 100644 --- a/libstdc++-v3/doc/html/manual/test.html +++ b/libstdc++-v3/doc/html/manual/test.html @@ -1,18 +1,18 @@ <?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Test</title><meta name="generator" content="DocBook XSL Stylesheets V1.74.3" /><meta name="keywords" content=" ISO C++ , test , testsuite , performance , conformance , ABI , exception safety " /><meta name="keywords" content=" ISO C++ , library " /><link rel="home" href="../spine.html" title="The GNU C++ Library Documentation" /><link rel="up" href="appendix_porting.html" title="Appendix B. Porting and Maintenance" /><link rel="prev" href="internals.html" title="Porting to New Hardware or Operating Systems" /><link rel="next" href="abi.html" title="ABI Policy and Guidelines" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Test</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="internals.html">Prev</a> </td><th width="60%" align="center">Appendix B. +<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Test</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><meta name="keywords" content=" ISO C++ , test , testsuite , performance , conformance , ABI , exception safety " /><meta name="keywords" content=" ISO C++ , library " /><link rel="home" href="../spine.html" title="The GNU C++ Library Documentation" /><link rel="up" href="appendix_porting.html" title="Appendix B. Porting and Maintenance" /><link rel="prev" href="internals.html" title="Porting to New Hardware or Operating Systems" /><link rel="next" href="abi.html" title="ABI Policy and Guidelines" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Test</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="internals.html">Prev</a> </td><th width="60%" align="center">Appendix B. Porting and Maintenance -</th><td width="20%" align="right"> <a accesskey="n" href="abi.html">Next</a></td></tr></table><hr /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="manual.intro.setup.test"></a>Test</h2></div></div></div><p> +</th><td width="20%" align="right"> <a accesskey="n" href="abi.html">Next</a></td></tr></table><hr /></div><div class="sect1" title="Test"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="manual.intro.setup.test"></a>Test</h2></div></div></div><p> The libstdc++ testsuite includes testing for standard conformance, regressions, ABI, and performance. -</p><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="test.organization"></a>Organization</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="test.organization.layout"></a>Directory Layout</h4></div></div></div><p> +</p><div class="sect2" title="Organization"><div class="titlepage"><div><div><h3 class="title"><a id="test.organization"></a>Organization</h3></div></div></div><div class="sect3" title="Directory Layout"><div class="titlepage"><div><div><h4 class="title"><a id="test.organization.layout"></a>Directory Layout</h4></div></div></div><p> The directory <span class="emphasis"><em>libsrcdir/testsuite</em></span> contains the individual test cases organized in sub-directories corresponding to chapters of the C++ standard (detailed below), the dejagnu test harness support files, and sources to various testsuite utilities that are packaged in a separate testing library. -</p><p> +</p><p> All test cases for functionality required by the runtime components of the C++ standard (ISO 14882) are files within the following directories. @@ -27,6 +27,9 @@ regressions, ABI, and performance. 25_algorithms 26_numerics 27_io +28_regex +29_atomics +30_threads </pre><p> In addition, the following directories include test files: </p><pre class="programlisting"> @@ -35,7 +38,6 @@ backward Tests for backwards compatibility and deprecated features. demangle Tests for __cxa_demangle, the IA 64 C++ ABI demangler ext Tests for extensions. performance Tests for performance analysis, and performance regressions. -thread Tests for threads. </pre><p> Some directories don't have test files, but instead contain auxiliary information: @@ -74,38 +76,38 @@ util Files for libtestc++, utilities and testing routines. 21_strings/basic_string/find/wchar_t/3.cc </pre><p> All new tests should be written with the policy of one test - case, one file in mind. - </p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="test.organization.naming"></a>Naming Conventions</h4></div></div></div><p> + case, one file in mind. + </p></div><div class="sect3" title="Naming Conventions"><div class="titlepage"><div><div><h4 class="title"><a id="test.organization.naming"></a>Naming Conventions</h4></div></div></div><p> In addition, there are some special names and suffixes that are used within the testsuite to designate particular kinds of tests. - </p><div class="itemizedlist"><ul type="disc"><li><p> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> <span class="emphasis"><em>_xin.cc</em></span> </p><p> 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: - </p><pre class="programlisting"> + </p><pre class="programlisting"> g++ 27_io/objects/char/3_xin.cc cat 27_io/objects/char/3_xin.in | a.out - </pre></li><li><p> + </pre></li><li class="listitem"><p> <span class="emphasis"><em>.in</em></span> </p><p> This file contains the expected input for the corresponding <span class="emphasis"><em> _xin.cc</em></span> test case. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>_neg.cc</em></span> </p><p> This test case is expected to fail: it's a negative test. At the moment, these are almost always compile time errors. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>char</em></span> </p><p> This can either be a directory name or part of a longer file name, and indicates that this file, or the files within this directory are testing the <code class="code">char</code> instantiation of a template. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>wchar_t</em></span> </p><p> This can either be a directory name or part of a longer file @@ -114,14 +116,14 @@ cat 27_io/objects/char/3_xin.in | a.out a template. Some hosts do not support <code class="code">wchar_t</code> functionality, so for these targets, all of these tests will not be run. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>thread</em></span> </p><p> This can either be a directory name or part of a longer file name, and indicates that this file, or the files within this directory are testing situations where multiple threads are being used. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>performance</em></span> </p><p> This can either be an enclosing directory name or part of a @@ -129,7 +131,7 @@ cat 27_io/objects/char/3_xin.in | a.out analyze runtime performance, for performance regression testing, or for other optimization related analysis. At the moment, these test cases are not run by default. - </p></li></ul></div></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="test.run"></a>Running the Testsuite</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="test.run.basic"></a>Basic</h4></div></div></div><p> + </p></li></ul></div></div></div><div class="sect2" title="Running the Testsuite"><div class="titlepage"><div><div><h3 class="title"><a id="test.run"></a>Running the Testsuite</h3></div></div></div><div class="sect3" title="Basic"><div class="titlepage"><div><div><h4 class="title"><a id="test.run.basic"></a>Basic</h4></div></div></div><p> You can check the status of the build without installing it using the dejagnu harness, much like the rest of the gcc tools.</p><pre class="programlisting"> make check</pre><p>in the <span class="emphasis"><em>libbuilddir</em></span> directory.</p><p>or</p><pre class="programlisting"> make check-target-libstdc++-v3</pre><p>in the <span class="emphasis"><em>gccbuilddir</em></span> directory. @@ -149,7 +151,7 @@ cat 27_io/objects/char/3_xin.in | a.out archived on a daily basis on the <a class="ulink" href="http://gcc.gnu.org/ml/gcc-testresults/current" target="_top">gcc-testresults</a> mailing list. Please check either of these places for a similar combination of source version, operating system, and host CPU. - </p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="test.run.variations"></a>Variations</h4></div></div></div><p> + </p></div><div class="sect3" title="Variations"><div class="titlepage"><div><div><h4 class="title"><a id="test.run.variations"></a>Variations</h4></div></div></div><p> There are several options for running tests, including testing the regression tests, testing a subset of the regression tests, testing the performance tests, testing just compilation, testing @@ -185,7 +187,7 @@ make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=calmrisc32-sid" --target=xscale-elf (newlib/sim) make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=arm-sim" -</pre><p> +</pre><p> Also, here is an example of how to run the libstdc++ testsuite for a multilibed build directory with different ABI settings: </p><pre class="programlisting"> @@ -207,7 +209,7 @@ runtest --tool libstdc++ --srcdir=/path/to/gcc/libstdc++-v3/testsuite same name as files created by other testsuites (like the ones for GCC and G++), so you should not try to run all the testsuites in parallel from the same directory. - </p><p> + </p><p> 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 @@ -220,32 +222,32 @@ runtest --tool libstdc++ --srcdir=/path/to/gcc/libstdc++-v3/testsuite </pre><p> Five files are generated that determine what test files are run. These files are: - </p><div class="itemizedlist"><ul type="disc"><li><p> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> <span class="emphasis"><em>testsuite_files</em></span> - </p><p> + </p><p> This is a list of all the test cases that will be run. Each test case is on a separate line, given with an absolute path from the <span class="emphasis"><em>libsrcdir/testsuite</em></span> directory. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>testsuite_files_interactive</em></span> - </p><p> + </p><p> This is a list of all the interactive test cases, using the same format as the file list above. These tests are not run by default. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>testsuite_files_performance</em></span> - </p><p> + </p><p> This is a list of all the performance test cases, using the same format as the file list above. These tests are not run by default. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>testsuite_thread</em></span> - </p><p> + </p><p> This file indicates that the host system can run tests which involved multiple threads. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>testsuite_wchar_t</em></span> - </p><p> + </p><p> This file indicates that the host system can run the wchar_t tests, and corresponds to the macro definition <code class="code"> _GLIBCXX_USE_WCHAR_T</code> in the file c++config.h. @@ -254,7 +256,7 @@ runtest --tool libstdc++ --srcdir=/path/to/gcc/libstdc++-v3/testsuite </pre><p> The library ABI can be tested. This involves testing the shared library against an ABI-defining previous version of symbol - exports. + exports. </p><pre class="programlisting"> make check-compile </pre><p> @@ -275,7 +277,7 @@ runtest --tool libstdc++ --srcdir=/path/to/gcc/libstdc++-v3/testsuite We are interested in any strange failures of the testsuite; please email the main libstdc++ mailing list if you see something odd or have questions. - </p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="test.run.permutations"></a>Permutations</h4></div></div></div><p> + </p></div><div class="sect3" title="Permutations"><div class="titlepage"><div><div><h4 class="title"><a id="test.run.permutations"></a>Permutations</h4></div></div></div><p> To run the libstdc++ test suite under the <a class="link" href="debug_mode.html" title="Chapter 30. Debug Mode">debug mode</a>, edit <code class="filename">libstdc++-v3/scripts/testsuite_flags</code> to add the compile-time flag <code class="constant">-D_GLIBCXX_DEBUG</code> to the @@ -295,10 +297,10 @@ runtest --tool libstdc++ --srcdir=/path/to/gcc/libstdc++-v3/testsuite Or, just run the testsuites with <code class="constant">CXXFLAGS</code> set to <code class="constant">-D_GLIBCXX_DEBUG</code> or <code class="constant">-D_GLIBCXX_PARALLEL</code>. - </p></div></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="test.new_tests"></a>Writing a new test case</h3></div></div></div><p> + </p></div></div><div class="sect2" title="Writing a new test case"><div class="titlepage"><div><div><h3 class="title"><a id="test.new_tests"></a>Writing a new test case</h3></div></div></div><p> The first step in making a new test case is to choose the correct directory and file name, given the organization as previously - described. + described. </p><p> All files are copyright the FSF, and GPL'd: this is very important. The first copyright year should correspond to the date @@ -406,7 +408,7 @@ up in the normal.exp file. // { dg-options "-O0" { target *-*-* } } </pre><p> More examples can be found in the libstdc++-v3/testsuite/*/*.cc files. - </p></div><div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a id="test.harness"></a>Test Harness and Utilities</h3></div></div></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="test.harness.dejagnu"></a>Dejagnu Harness Details</h4></div></div></div><p> + </p></div><div class="sect2" title="Test Harness and Utilities"><div class="titlepage"><div><div><h3 class="title"><a id="test.harness"></a>Test Harness and Utilities</h3></div></div></div><div class="sect3" title="Dejagnu Harness Details"><div class="titlepage"><div><div><h4 class="title"><a id="test.harness.dejagnu"></a>Dejagnu Harness Details</h4></div></div></div><p> Underlying details of testing for conformance and regressions are abstracted via the GNU Dejagnu package. This is similar to the rest of GCC. @@ -433,7 +435,7 @@ callbacks loaded from the support library. </p><p>The <code class="code">config</code> directory is searched for any particular "target board" information unique to this library. This is currently unused and sets only default variables. -</p></div><div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a id="test.harness.utils"></a>Utilities</h4></div></div></div><p> +</p></div><div class="sect3" title="Utilities"><div class="titlepage"><div><div><h4 class="title"><a id="test.harness.utils"></a>Utilities</h4></div></div></div><p> </p><p> The testsuite directory also contains some files that implement functionality that is intended to make writing test cases easier, @@ -445,48 +447,188 @@ only default variables. during testing. </p><p> These files include the following functionality: - </p><div class="itemizedlist"><ul type="disc"><li><p> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> <span class="emphasis"><em>testsuite_abi.h</em></span>, <span class="emphasis"><em>testsuite_abi.cc</em></span>, <span class="emphasis"><em>testsuite_abi_check.cc</em></span> </p><p> - Creates the executable <span class="emphasis"><em>abi_check</em></span>. - Used to check correctness of symbol versioning, visibility of - exported symbols, and compatibility on symbols in the shared - library, for hosts that support this feature. More information - can be found in the ABI documentation <a class="link" href="abi.html" title="ABI Policy and Guidelines">here</a> - </p></li><li><p> + Creates the executable <span class="emphasis"><em>abi_check</em></span>. + Used to check correctness of symbol versioning, visibility of + exported symbols, and compatibility on symbols in the shared + library, for hosts that support this feature. More information + can be found in the ABI documentation <a class="link" href="abi.html" title="ABI Policy and Guidelines">here</a> + </p></li><li class="listitem"><p> <span class="emphasis"><em>testsuite_allocator.h</em></span>, <span class="emphasis"><em>testsuite_allocator.cc</em></span> </p><p> - Contains specialized allocators that keep track of construction - and destruction. Also, support for overriding global new and - delete operators, including verification that new and delete - are called during execution, and that allocation over max_size - fails. - </p></li><li><p> + Contains specialized allocators that keep track of construction + and destruction. Also, support for overriding global new and + delete operators, including verification that new and delete + are called during execution, and that allocation over max_size + fails. + </p></li><li class="listitem"><p> <span class="emphasis"><em>testsuite_character.h</em></span> </p><p> - Contains <code class="code">std::char_traits</code> and - <code class="code">std::codecvt</code> specializations for a user-defined - POD. - </p></li><li><p> + Contains <code class="code">std::char_traits</code> and + <code class="code">std::codecvt</code> specializations for a user-defined + POD. + </p></li><li class="listitem"><p> <span class="emphasis"><em>testsuite_hooks.h</em></span>, <span class="emphasis"><em>testsuite_hooks.cc</em></span> </p><p> A large number of utilities, including: - </p><div class="itemizedlist"><ul type="circle"><li><p>VERIFY</p></li><li><p>set_memory_limits</p></li><li><p>verify_demangle</p></li><li><p>run_tests_wrapped_locale</p></li><li><p>run_tests_wrapped_env</p></li><li><p>try_named_locale</p></li><li><p>try_mkfifo</p></li><li><p>func_callback</p></li><li><p>counter</p></li><li><p>copy_tracker</p></li><li><p>copy_constructor</p></li><li><p>assignment_operator</p></li><li><p>destructor</p></li><li><p>pod_char, pod_int and associated char_traits specializations</p></li></ul></div></li><li><p> + </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>VERIFY</p></li><li class="listitem"><p>set_memory_limits</p></li><li class="listitem"><p>verify_demangle</p></li><li class="listitem"><p>run_tests_wrapped_locale</p></li><li class="listitem"><p>run_tests_wrapped_env</p></li><li class="listitem"><p>try_named_locale</p></li><li class="listitem"><p>try_mkfifo</p></li><li class="listitem"><p>func_callback</p></li><li class="listitem"><p>counter</p></li><li class="listitem"><p>copy_tracker</p></li><li class="listitem"><p>copy_constructor</p></li><li class="listitem"><p>assignment_operator</p></li><li class="listitem"><p>destructor</p></li><li class="listitem"><p>pod_char, pod_int and associated char_traits specializations</p></li></ul></div></li><li class="listitem"><p> <span class="emphasis"><em>testsuite_io.h</em></span> </p><p> Error, exception, and constraint checking for <code class="code">std::streambuf, std::basic_stringbuf, std::basic_filebuf</code>. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>testsuite_iterators.h</em></span> </p><p> Wrappers for various iterators. - </p></li><li><p> + </p></li><li class="listitem"><p> <span class="emphasis"><em>testsuite_performance.h</em></span> </p><p> A number of class abstractions for performance counters, and reporting functions including: - </p><div class="itemizedlist"><ul type="circle"><li><p>time_counter</p></li><li><p>resource_counter</p></li><li><p>report_performance</p></li></ul></div></li></ul></div></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="internals.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="appendix_porting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="abi.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Porting to New Hardware or Operating Systems </td><td width="20%" align="center"><a accesskey="h" href="../spine.html">Home</a></td><td width="40%" align="right" valign="top"> ABI Policy and Guidelines</td></tr></table></div></body></html> + </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>time_counter</p></li><li class="listitem"><p>resource_counter</p></li><li class="listitem"><p>report_performance</p></li></ul></div></li></ul></div></div></div><div class="sect2" title="Special Topics"><div class="titlepage"><div><div><h3 class="title"><a id="test.special"></a>Special Topics</h3></div></div></div><div class="sect3" title="Qualifying Exception Safety Guarantees"><div class="titlepage"><div><div><h4 class="title"><a id="test.exception.safety"></a> + Qualifying Exception Safety Guarantees + <a id="id461124" class="indexterm"></a> +</h4></div></div></div><div class="sect4" title="Overview"><div class="titlepage"><div><div><h5 class="title"><a id="test.exception.safety.overview"></a>Overview</h5></div></div></div><p> + Testing is composed of running a particular test sequence, + and looking at what happens to the surrounding code when + exceptions are thrown. Each test is composed of measuring + initial state, executing a particular sequence of code under + some instrumented conditions, measuring a final state, and + then examining the differences between the two states. + </p><p> + Test sequences are composed of constructed code sequences + that exercise a particular function or member function, and + either confirm no exceptions were generated, or confirm the + consistency/coherency of the test subject in the event of a + thrown exception. + </p><p> + Random code paths can be constructed using the the basic test + sequences and instrumentation as above, only combined in a + random or pseudo-random way. + </p><p> To compute the code paths that throw, test instruments + are used that throw on allocation events + (<code class="classname">__gnu_cxx::throw_allocator_random</code> + and <code class="classname">__gnu_cxx::throw_allocator_limit</code>) + and copy, assignment, comparison, increment, swap, and + various operators + (<code class="classname">__gnu_cxx::throw_type_random</code> + and <code class="classname">__gnu_cxx::throw_type_limit</code>). Looping + through a given test sequence and conditionally throwing in + all instrumented places. Then, when the test sequence + completes without an exception being thrown, assume all + potential error paths have been exercised in a sequential + manner. + </p></div><div class="sect4" title="Existing tests"><div class="titlepage"><div><div><h5 class="title"><a id="test.exception.safety.status"></a> + Existing tests +</h5></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + Ad Hoc + </p><p> + For example, + <code class="filename">testsuite/23_containers/list/modifiers/3.cc</code>. + </p></li><li class="listitem"><p> + Policy Based Data Structures + </p><p> + For example, take the test + functor <code class="classname">rand_reg_test</code> in + in <code class="filename">testsuite/ext/pb_ds/regression/tree_no_data_map_rand.cc</code>. This uses <code class="classname">container_rand_regression_test</code> in +<code class="filename">testsuite/util/regression/rand/assoc/container_rand_regression_test.h</code>. + + </p><p> + Which has several tests for container member functions, +Includes control and test container objects. Configuration includes +random seed, iterations, number of distinct values, and the +probability that and exception will be thrown. Assumes instantiating +container uses an extension +allocator, <code class="classname">__gnu_cxx::throw_allocator_random</code>, +as the allocator type. + </p></li><li class="listitem"><p> + C++0x Container Requirements. + </p><p> + Coverage is currently limited to testing container + requirements for exception safety, + although <code class="classname">__gnu_cxx::throw_type</code> meets + the additional type requirements for testing numeric data + structures and instantiating algorithms. + </p><p> + Of particular interest is extending testing to algorithms and + then to parallel algorithms. Also io, and locales. + </p></li></ul></div></div><div class="sect4" title="C++0x Requirements Test Sequence Descriptions"><div class="titlepage"><div><div><h5 class="title"><a id="test.exception.safety.containers"></a> +C++0x Requirements Test Sequence Descriptions +</h5></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> + Basic + </p><p> + Basic consistency on exception propagation tests. For + each container, an object of that container is constructed, + a specific member function is exercised in + a <code class="literal">try</code> block, and then any thrown + exceptions lead to error checking in the appropriate + <code class="literal">catch</code> block. The container's use of + resources is compared to the container's use prior to the + test block. Resource monitoring is limited to allocations + made through the container's <span class="type">allocator_type</span>, + which should be sufficient for container data + structures. Included in these tests are member functions + are <span class="type">iterator</span> and <span class="type">const_iterator</span> + operations, <code class="function">pop_front</code>, <code class="function">pop_back</code>, <code class="function">push_front</code>, <code class="function">push_back</code>, <code class="function">insert</code>, <code class="function">erase</code>, <code class="function">swap</code>, <code class="function">clear</code>, + and <code class="function">rehash</code>. The container in question is + instantiated with two instrumented template arguments, + with <code class="classname">__gnu_cxx::throw_allocator_limit</code> + as the allocator type, and + with <code class="classname">__gnu_cxx::throw_type_limit</code> as + the value type. This allows the test to loop through + conditional throw points. + </p><p> + The general form is demonstrated in + <code class="filename">testsuite/23_containers/list/requirements/exception/basic.cc + </code>. The instantiating test object is <code class="classname">__gnu_test::basic_safety</code> and is detailed in <code class="filename">testsuite/util/exception/safety.h</code>. + </p></li><li class="listitem"><p> + Generation Prohibited + </p><p> + Exception generation tests. For each container, an object of + that container is constructed and all member functions + required to not throw exceptions are exercised. Included in + these tests are member functions + are <span class="type">iterator</span> and <span class="type">const_iterator</span> operations, <code class="function">erase</code>, <code class="function">pop_front</code>, <code class="function">pop_back</code>, <code class="function">swap</code>, + and <code class="function">clear</code>. The container in question is + instantiated with two instrumented template arguments, + with <code class="classname">__gnu_cxx::throw_allocator_random</code> + as the allocator type, and + with <code class="classname">__gnu_cxx::throw_type_random</code> as + the value type. This test does not loop, an instead is sudden + death: first error fails. + </p><p> + The general form is demonstrated in + <code class="filename">testsuite/23_containers/list/requirements/exception/generation_prohibited.cc + </code>. The instantiating test object is <code class="classname">__gnu_test::generation_prohibited</code> and is detailed in <code class="filename">testsuite/util/exception/safety.h</code>. + </p></li><li class="listitem"><p> + Propagation Consistent + </p><p> + Container rollback on exception propagation tests. For + each container, an object of that container is constructed, + a specific member function that requires rollback to a previous + known good state is exercised in + a <code class="literal">try</code> block, and then any thrown + exceptions lead to error checking in the appropriate + <code class="literal">catch</code> block. The container is compared to + the container's last known good state using such parameters + as size, contents, and iterator references. Included in these + tests are member functions + are <code class="function">push_front</code>, <code class="function">push_back</code>, <code class="function">insert</code>, + and <code class="function">rehash</code>. The container in question is + instantiated with two instrumented template arguments, + with <code class="classname">__gnu_cxx::throw_allocator_limit</code> + as the allocator type, and + with <code class="classname">__gnu_cxx::throw_type_limit</code> as + the value type. This allows the test to loop through + conditional throw points. + </p><p> + The general form demonstrated in + <code class="filename">testsuite/23_containers/list/requirements/exception/propagation_coherent.cc + </code>. The instantiating test object is <code class="classname">__gnu_test::propagation_coherent</code> and is detailed in <code class="filename">testsuite/util/exception/safety.h</code>. + </p></li></ul></div></div></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="internals.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="appendix_porting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="abi.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Porting to New Hardware or Operating Systems </td><td width="20%" align="center"><a accesskey="h" href="../spine.html">Home</a></td><td width="40%" align="right" valign="top"> ABI Policy and Guidelines</td></tr></table></div></body></html> |