anchor.diff:  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.
  +`CMakeLists.txt` files.
   
   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.
  +. Use the link:https://cmake.org/cmake/help/latest/command/add_subdirectory.html[add_subdirectory]
  +  command from the link:../../tests/CMakeLists.txt[tests/CMakeLists.txt]
  +  to add the `foo` subdirectory to the CMake buildsystem.
  +. Create `CMakeLists.txt` inside the `tests/foo` directory and use the
  +  `add_oscap_test` function (defined in the
  +  link:../../tests/CMakeLists.txt[tests/CMakeLists.txt]) to add all your test
  +  scripts from the `foo` directory.
  +
  +Please see the
  +link:https://gitlab.kitware.com/cmake/community/wikis/doc/ctest/Testing-With-CTest[
  +CTest documentation] 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
  +NOTE: The `cmake` command 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:
  +the functions which it provides:
   [[app-listing]]
   [source,bash]
   ----
  
positive.code: 
  set -o pipefail
  
  . ../test_common.sh
  
  test1
  test2
  ...
  ----
  
  
  ==== Global variables exported by test library
  
negative.code: 
  
  ==== test_exit function
  The function is responsible for cleaning-up the testing environment. You can
  call it without arguments or with one argument -- a script/function which will
  do additional clean-up tasks.
  