| ATF-TEST-PROGRAM(1) | General Commands Manual | ATF-TEST-PROGRAM(1) |
atf-test-program —
common interface to ATF test programs
atf-test-program |
[-r resfile]
[-s srcdir]
[-v var1=value1 [..
-v varN=valueN]]
test_case |
atf-test-program |
-l |
Test programs written using the ATF libraries all share a common
user interface, which is what this manual page describes.
NOTE: There is
no binary known as atf-test-program;
what is described
in this manual page is the command-line interface
exposed by
the atf-c, atf-c++ and atf-sh bindings.
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 -r flag. Optionally,
the test case name can be suffixed by ‘:cleanup’, in which
case the cleanup routine of the test case will be executed instead of the
test case body; see atf-test-case(4). Note that the test
case is executed without
isolation, 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 interface. The recommended
runtime engine is kyua(1). You should only execute test
cases by hand for debugging purposes.
In the second synopsis 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 kyua(1) to know how to execute the test cases of a given test program.
The following options are available:
-l-r
resfile-s
srcdir-v
var=value| March 2, 2014 | Debian |