Imported Upstream version 1.72.0

[platform/upstream/boost.git] / libs / test / doc / adv_scenarios / single_header_customizations.qbk

diff --git a/libs/test/doc/adv_scenarios/single_header_customizations.qbk b/libs/test/doc/adv_scenarios/single_header_customizations.qbk
index 68c8714..f6f5c79 100644 (file)
--- a/libs/test/doc/adv_scenarios/single_header_customizations.qbk
+++ b/libs/test/doc/adv_scenarios/single_header_customizations.qbk
@@ -1,11 +1,11 @@
 [/
- / 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)
  /]
 
-[section:single_header_customizations Header-only variant customizations] 
+[section:single_header_customizations Header-only variant customizations]
 
 [section:multiple_translation_units Header-only with multiple translation units]
 It is possible to use the header-only variant of the __UTF__ even if the test module has multiple translation
@@ -43,7 +43,7 @@ An example might be the following:
 
 [section:entry_point Customizing the module's entry point]
 
-In this usage variant and in the translation unit containing the definition of __BOOST_TEST_MODULE__, 
+In this usage variant and in the translation unit containing the definition of __BOOST_TEST_MODULE__,
 you need to define the macros __BOOST_TEST_NO_MAIN__ and
 __BOOST_TEST_ALTERNATIVE_INIT_API__ (their values are irrelevant) prior to including any of the framework's headers.
 Next, you have to define your custom entry point, and invoke the default [link
@@ -56,7 +56,7 @@ In the above example, a custom entry point was selected because the test module,
 needs to obtain also the information about environment variables.
 
 [note The above example also illustrates that it makes sense to define both __BOOST_TEST_MODULE__ and
-__BOOST_TEST_NO_MAIN__. This way, no `main` is generated by the framework, but the name specified by __BOOST_TEST_MODULE__ 
+__BOOST_TEST_NO_MAIN__. This way, no `main` is generated by the framework, but the name specified by __BOOST_TEST_MODULE__
 is assigned to the [link boost_test.tests_organization.test_tree.master_test_suite Master test suite].]
 
 [note The reason for defining __BOOST_TEST_ALTERNATIVE_INIT_API__ is described [link
@@ -78,7 +78,7 @@ boost_test.adv_scenarios.test_module_runner_overview test runner] will use it to
 boost_test.tests_organization.test_tree.master_test_suite master test suite]. Therefore the default name ("Master Test
 Suite") is used.]
 
-For reporting errors that may occur during the initialization, 
+For reporting errors that may occur during the initialization,
 
 * either you return `false` (valid only for the new API only, see __BOOST_TEST_ALTERNATIVE_INIT_API__)
 * or you raise an exception such as `std::runtime_error` or [classref boost::unit_test::framework::setup_error]