bump version to 12.2.2-pve1

[ceph.git] / ceph / src / boost / libs / test / doc / test_output / test_tools_support.qbk

[/
 / Copyright (c) 2015 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:test_tools_support_for_logging Tools supports for logging]


[/ -------------------------------------------------------------------------------------------------- ]
[section:testing_tool_output_disable Logging user defined types]

Most of the [link boost_test.testing_tools testing tools] print values of their
arguments to the output stream in some form of log statement. If arguments type does not support
``
  operator<<(std::ostream&, ArgumentType const&);
``
interface you will get a compilation error. You can either implement above interface or prohibit
the [link boost_test.testing_tools testing tools] from logging argument values for
specified type. To do so, use following statement on file level before first test case that
includes statement failing to compile:

``
  BOOST_TEST_DONT_PRINT_LOG_VALUE(ArgumentType)
``

[bt_example example32..BOOST_TEST_DONT_PRINT_LOG_VALUE usage..run-fail]

[endsect] [/section:testing_tool_output_disable]

[/ -------------------------------------------------------------------------------------------------- ]
[section:test_output_macro_message Custom messages]
The macro __BOOST_TEST_MESSAGE__ is intended to be used for the purpose of injecting an additional message into the
__UTF__ test log. These messages are not intended to indicate any error or warning conditions, but rather as
information/status notifications. The macro signature is as follows:

  __BOOST_TEST_MESSAGE__(test_message);

The test_message argument can be as simple as C string literal or any custom expression that you can produce with in a
manner similar to standard `std::iostream` operation.

[important Messages generated by this tool do not appear in test log output with default value of the active log level
   threshold. For these messages to appear the active log level threshold has to be set to a value below or equal
   to "message".
]

[bt_example example21..__BOOST_TEST_MESSAGE__ usage..run]

[endsect] [/section:test_output_macro_message]

[/ -------------------------------------------------------------------------------------------------- ]

[include checkpoints.qbk]
[include contexts.qbk]
[include logging_floating_point.qbk]

[endsect] [/ Tools supports for logging]