anchor.diff:  
   === Plugging your new test into the test library
   You need to plug your test into the test library so it will be run automatically
  -everytime `make check` is run. To do this, you need to add all the test files
  -into the `Makefile.am`. The `Makefile.am` which you need to modify is located
  -in the same directory as your test files.
  +everytime `make test` is run. To do this, you need to add your test script
  +into the `CMakeLists.txt`. The `CMakeLists.txt` which you need to modify is
  +located in the same directory as your test script.
   
   We will demonstrate this on our example with the SCE test. We have prepared our
   test script, the XML document file with custom rules and various check scripts
   for testing. We placed all our test files into the
   link:../../tests/sce[tests/sce] directory. Now we will modify the
  -link:../../tests/sce/Makefile.am[tests/sce/Makefile.am] and we will add all our
  -test files into the `EXTRA_DIST` variable and our test script into the `TESTS`
  -variable which will make sure that our test will be executed by the `make check`:
  +link:../../tests/sce/CMakeLists.txt[tests/sce/CMakeLists.txt] and we will add
  +our test script file using the `add_oscap_test` function which will make sure
  +that our test will be executed by the `make test`:
   [[app-listing]]
   [subs=+quotes]
   ----
  -...
  -
  -TESTS = *test_sce.sh* \
  -		...
  -
  -...
  -
  -EXTRA_DIST = *test_sce.sh \
  -		sce_xccdf.xml \
  -		bash_passer.sh \
  -		python_passer.py \
  -		python_is16.py \
  -		lua_passer.lua \*
  -		...
  +if(ENABLE_SCE)
  +	...
  +	*add_oscap_test("test_sce.sh")*
  +	...
  +endif()
   ----
   
   
   === Running your new test
   To run your new test you first need to compile the OpenSCAP library. See the
   *Compilation* section in the link:../../README.md[README.md] for more details.
  -Also you don't need to run all the tests, only tests in a directory where you
  -have added your new test. To do so, first change directory to the directory
  -with your test and then run `make check` from there, for example:
  -[[app-listing]]
  -[source,bash]
  -----
  -$ cd tests/sce
  -$ make check
  -----
  -
  -Log file with your test results can be located under the name which is set
  -using the `test_init` function in your test script. In our example,
  -in the link:../../tests/sce/test_sce.sh[tests/sce/test_sce.sh] test script,
  -the log file is set as `test_sce.log`.
  -
  -NOTE: Our Jenkins runs `make distcheck` instead of `make check` so please make
  -sure that your test works for both of these modes. More details about the GNU
  -Build System build tree and source tree can be found in the
  -link:https://www.gnu.org/software/automake/manual/html_node/Checking-the-Distribution.html[GNU automake documentation].
  -
  +Also you don't need to run all the tests using `make test`, you can run only
  +the specific test(s). To do so, you need to be in the build directory and
  +run `ctest -R` from there, for example:
  +[[app-listing]]
  +[source,bash]
  +----
  +$ cd build/
  +$ ctest -R sce/test_sce.sh
  +$ less Testing/Temporary/LastTest.log
  +----
  +
  +Results from testing will be printed on the stdout and detailed log file with
  +your test results can be found in the `Testing/Temporary/LastTest.log` file.
  +
  
positive.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 **GNU automake** which has built-in
  link:https://www.gnu.org/software/automake/manual/html_node/Tests.html[support
  for test suites].
  
  
  == Preparing test environment and running tests
  
negative.code: 
  
  ==== test_init 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.
  [[app-listing]]
  [source,bash]
  ----
  test_run "DESCRIPTION" TEST_FUNCTION|$srcdir/TEST_SCRIPT_FILE ARG [ARG...]
  ----
  
  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*,
  