Test  programs written using the ATF libraries all share a common
user interface, which is what this manual page describes.  In the
first synopsis form, the test program will execute  the  provided
test  case  and  print its results to the standard output, unless
otherwise stated by the flag.  Optionally, the test case name can
be suffixed by in which case the cleanup routine of the test case
will be executed instead of the test case body; see Note that the
test case is so it can and probably will create and modify  files
in  the current directory.  To execute test cases in a controller
manner, you need a runtime engine that understands the ATF inter‐
face.  The recommended runtime engine is You should only  execute
test  cases by hand for debugging purposes.  In the second synop‐
sis form, the test program will list  all  available  test  cases
alongside  their meta‐data properties in a format that is machine
parseable.  This list is processed by to know how to execute  the
test  cases  of  a given test program.  The following options are
available: Lists available test cases alongside a brief  descrip‐
tion  for each of them.  Specifies the file that will receive the
test case result.  If not specified, the test case prints its re‐
sults to stdout.  If the result of a test case needs to be parsed
by another program, you must use this option to redirect the  re‐
sult  to  a  file and then read the resulting file from the other
program.  Note: because your program may  break  in  the  future.
The  path  to  the  directory  where the test program is located.
This is needed in all cases, except when the test program is  be‐
ing  executed  from the current directory.  The test program will
use this path to locate any helper data files or utilities.  Sets
the configuration variable to the value