anchor.diff:  
   
   ==== test_init function
  -The function expects that you provide it with a name of a test log file.
  -All tests which will be run after `test_init` using `test_run` function
  -will report results into this log file:
  -[[app-listing]]
  -[source,bash]
  -----
  -test_init test_foo.log
  -----
  -
  -NOTE: The specified log file will contain output of both `stdout` and `stderr`
  -of every test executed by the `test_run` function.
  +This function does nothing. Logging is done by the CTest and the log from
  +testing can be found at `build/Testing/Temporary/LastTest.log`.
   
   
   ==== test_run function
   The function is responsible for executing a test script file or a function and
  -logging its result into the log file created by the `test_init` function.
  +logging its result into the log file.
   [[app-listing]]
   [source,bash]
   ----
   test_run "DESCRIPTION" TEST_FUNCTION|$srcdir/TEST_SCRIPT_FILE ARG [ARG...]
   ----
  -The `$srcdir` variable contains the path to the directory with the test script.
  +
  +NOTE: The `$srcdir` variable contains the path to the directory with the test
  +script. It is defined in the link:../../tests/CMakeLists.txt[tests/CMakeLists.txt]
  +as `srcdir=${CMAKE_CURRENT_SOURCE_DIR}`. The reason is backward compatibility
  +as originally tests were executed by the GNU automake.
  +
   The `test_run` function reports the following results into the log file:
   
   * *PASS* when script/function returns *0*,
  
positive.code: This might happen if your test covers a part of the OpenSCAP which has no tests
  at all. In this case you would need to add a new directory with suitable name
  into the link:../../tests[tests] directory structure and create/update
  Makefiles.
  
  To have an example also for this scenario, let's suppose we want to add the
  `foo` subdirectory into the link:../../tests[tests] directory. We need to:
  
  . Create the `foo` subdirectory in the link:../../tests[tests] directory.
  . Add a new entry for `foo` subdirectory into the `SUBDIRS` variable in
    the link:../../tests/Makefile.am[tests/Makefile.am].
  . Create `Makefile.am` inside the `tests/foo` directory and list all
    your test scripts inside that directory in the `TESTS` variable.
  
  Please see the GNU automake
  link:https://www.gnu.org/software/automake/manual/html_node/Tests.html[
  documentation about test suites] for more details.
  
  
  === Common test library
  When writing tests for OpenSCAP you should use the common test library which is
  located at link:../../tests/test_common.sh.in[tests/test_common.sh.in].
  
  NOTE: The `configure` script will generate the `tests/test_common.sh` file from
  the link:../../tests/test_common.sh.in[tests/test_common.sh.in] adding
  configuration specific settings.
  
  You will need to source the `tests/test_common.sh` in your test scripts to use
  the functions which it provides. When sourcing the file, you need to specify
  a relative path to it from the directory with your test script. For example,
  when your test script will be in the `tests/foo` directory:
  [[app-listing]]
  [source,bash]
  ----
  
negative.code: where to put the test for your pull request and if you are not sure don't be
  affraid to ask in the pull request, someone will definitely help you with that.
  
  NOTE: OpenSCAP project uses the **CMake** buildsystem which has built-in
  testing support through the
  link:https://gitlab.kitware.com/cmake/community/wikis/doc/ctest/Testing-With-CTest[CTest]
  testing tool.
  
  
  == Preparing test environment and running tests
  