Imported Upstream version 1.72.0

[platform/upstream/boost.git] / libs / test / doc / test_organization / test_cases.qbk

diff --git a/libs/test/doc/test_organization/test_cases.qbk b/libs/test/doc/test_organization/test_cases.qbk
index 1b944ec..f0e9aa9 100644 (file)
--- a/libs/test/doc/test_organization/test_cases.qbk
+++ b/libs/test/doc/test_organization/test_cases.qbk
@@ -1,5 +1,5 @@
 [/
- / Copyright (c) 2003 Boost.Test contributors 
+ / Copyright (c) 2003 Boost.Test contributors
  /
  / Distributed under the Boost Software License, Version 1.0. (See accompanying
  / file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
@@ -7,12 +7,12 @@
 
 
 [section:test_cases Test cases]
-A test case is a unit of execution that is run by the [link test_runner test runner]. It contains instructions and 
-[link boost_test.testing_tools.boost_test_universal_macro assertions], and its execution is monitored by the __UTF__. 
-Information about the execution is recorded, and a log/report is produced. 
+A test case is a unit of execution that is run by the [link test_runner test runner]. It contains instructions and
+[link boost_test.testing_tools.boost_test_universal_macro assertions], and its execution is monitored by the __UTF__.
+Information about the execution is recorded, and a log/report is produced.
 
-The test runner should be informed of the test case in order to run it: the test case should be *registered* for its 
-inclusion into the /test tree/. 
+The test runner should be informed of the test case in order to run it: the test case should be *registered* for its
+inclusion into the /test tree/.
 
 The __UTF__ covers the following test case scenarios:
 
@@ -21,13 +21,13 @@ The __UTF__ covers the following test case scenarios:
   each call with a different parameter being handled by the test runner.
 * *test cases on template*: the scenario is to test the same template implementation against several type.
 
-The test case have a different *declaration* APIs for each of the above scenarios. Preferred APIs will declare the test case 
+The test case have a different *declaration* APIs for each of the above scenarios. Preferred APIs will declare the test case
 and register it automatically in a test tree without a necessity to perform manual registration.
 
 [h4 Manual registration]
-While automatic registration is preferred test case declaration API, it is also possible to declare tests manually. 
-For this APIs, __UTF__ opted for a least intrusive design based on ['generic callback] approach, which signatures 
-depends on the king of test case being declared. 
+While automatic registration is preferred test case declaration API, it is also possible to declare tests manually.
+For this APIs, __UTF__ opted for a least intrusive design based on ['generic callback] approach, which signatures
+depends on the king of test case being declared.
 
 The single test module may mix both automated and manual test case
 registration. In other words, within the same test module you can have both test cases implemented remotely and
@@ -41,22 +41,22 @@ and it's never going to be executed, even though it's present in test file. ]
 You need to be sure you exhausted all possible ways to employ automatic registration APIs first before you opt
 to use manual registration. Specifically:
 
-* If you need optionally include/exclude some of the test cases, consider using 
+* If you need optionally include/exclude some of the test cases, consider using
   __decorator_enabled__ / __decorator_disabled__ / __decorator_enable_if__ decorators instead
-* If you need to register some parametrized test cases based on some data, consider 
+* If you need to register some parametrized test cases based on some data, consider
   [link boost_test.tests_organization.test_cases.test_case_generation data-driven] test cases instead
-* If you need to specify complicated test unit dependencies, you can use __decorator_depends_on__ 
+* If you need to specify complicated test unit dependencies, you can use __decorator_depends_on__
   decorator instead
-* if you need to share the logic between the test units consider using 
+* if you need to share the logic between the test units consider using
   [link boost_test.tests_organization.fixtures fixtures] instead
 
 [/ ############################################# ]
 [include nullary_tests.qbk]
 
-[/ ############################################# ] 
+[/ ############################################# ]
 [include parametric_test_case_generation.qbk]
 
-[/ ############################################# ] 
+[/ ############################################# ]
 [include typed_parametrized_tests.qbk]
 
 [/ ############################################# ]