anchor.diff:  
   The *run* script is generated at configure time and it sets:
   
  -* **LD_PRELOAD* and *LD_LIBRARY_PATH* - preload ```libopenscap_testing.so```
  +* *LD_PRELOAD* and *LD_LIBRARY_PATH* - preload ```libopenscap_testing.so```
   * *OVAL_PROBE_DIR* - path to probes
   * *OSCAP_SCHEMA_PATH* - path to XCCDF, OVAL, CPE, ... schemas. (required
   for valudation)
  
positive.code: 
  * *OSCAP_FULL_VALIDATION=1* - validate all exported documents (slower)
  * *SEXP_VALIDATE_DISABLE=1* - do not validate SEXP expressions (faster)
  * *OSCAP_DEBUG_FILE="foo"* - name for debug files
  * *OSCAP_DEBUG_LEVEL=2* - set verbosity in debug logs
  ** ```1``` for Errors
  ** ```2``` for Errors & Warnings
  ** ```3``` for Errors & Warnings & Info messages
  
  
  
  
negative.code: 
  === Debugging
  Developers and users who intend to help find and fix possible bugs in OpenSCAP
  or possible bugs in their security policies have these possibilities:
  
  ==== Verbose mode
  The verbose mode provides user additional information about process of system
  scanning. The mode is useful for diagnostics of SCAP content evaluation
  and also for debugging. It produces a detailed report log with various messages.
  The mode is available for ```xccdf eval```, ```oval eval```, ```oval collect```
  and ```oval analyse``` modules.
  There is no need to special compilation, the feature is available for all
  OpenSCAP users.
  
  To turn the verbose mode on, run ```oscap``` with both those two options:
  
  * ```--verbose VERBOSITY_LEVEL``` - Turn on verbose mode at specified
  verbosity level.
  * ```--verbose-log-file FILE``` - Provide name of a log file that the log
  will be written into.
  
  The ```VERBOSITY_LEVEL``` can be one of:
  
  1. *DEVEL* - the most detailed information for developers and bug hunters
  2. *INFO* - reports content processing and system scanning
  3. *WARNING* - possible failures which OpenSCAP can recover from
  4. *ERROR* - shows only serious errors
  
  If you omit one of those two options, verbose mode can't be turned on
  and you will get an error message.
  
  This is an example describing how to run OpenSCAP in verbose mode:
  
  ----
  $ oscap oval eval --results results.xml --verbose INFO --verbose-log-file log.txt oval.xml
  ----
  
  Then see the log using eg.:
  
  ----
  $ less log.txt
  ----
  
  Each message contains identifier and name of the process and thread which produced
  the message, then its verbosity level, and also source file, line and function
  describing specific place of its origin.
  
  ==== Debug mode
  Debug mode is useful for programmers. You need to build OpenSCAP from source code
  with a custom configuration to enable the debug mode. Use this command:
  
  ------------------------------------
  $ ./configure --enable-debug && make
  