anchor.diff:  There are several command line flags that can be specified to customize how `test161` runs tests.
   
   * `-dry-run` (`-r`): Show the tests that would be run, but don't run them.
  +* `-explain` (`-x`): Show test detail, such as name, descriptions, `sys161 configuration`, commands, and expected output.
   * `-sequential` (`-s`): By default the output of all tests are interleaved, which can be hard to debug.
   Specify this option to run tests one at a time.
   * `-no-dependencies` (`-n`): Run the given tests without also running their dependencies. In test files, you can specify a
  
positive.code: 
  == Configuration
  
  In order to run `test161`, it needs to know about which <<tests>>, 
  <<targets>>, and <<commands>> it can run, and what to expect from  each command.
  Additionally, `test161` needs to know where to find your root directory for
  testing and your repository for submission. This information is specified in your
  `.test161.conf` file, which can be located in your `$HOME` directory, or whichever
  directory you plan to run `test161` in. If you run `test161 run` without a config
  file set up, an example will be displayed on screen.  You can redirect this output
  to `.test161.conf` and edit it accordingly.
  
  [source,bash]
  ----
  test161 run > ~/.test161.conf
  vim ~/.test161.conf
  ----
  
  == Usage
  
  
negative.code: conf:
    cpus: 8
    ram: 1M
    disk1: # disabled by default, but should be enabled when you want swap disk
      sectors: min(2 * ram, 8000) # 8000 is a minimum due to a current sys161 bug
      rpm: 7200
      nodoom: true
  