atf-test-program(1) [netbsd man page]
ATF-TEST-PROGRAM(1) BSD General Commands Manual ATF-TEST-PROGRAM(1) NAME
atf-test-program -- common interface to ATF test programs SYNOPSIS
atf-test-program [-r resfile] [-s srcdir] [-v var1=value1 [.. -v varN=valueN]] test_case atf-test-program -l DESCRIPTION
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 other- wise 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, refer to atf-run(1), which is the preferred way to run test cases. 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 atf-run(1) to know how to execute the test cases of a given test program. The following options are available: -l Lists available test cases alongside a brief description for each of them. -r resfile Specifies the file that will receive the test case result. If not specified, the test case prints its results to stdout. If the result of a test case needs to be parsed by another program, you must use this option to redirect the result to a file and then read the resulting file from the other program. Note: do not try to process the stdout of the test case because your program may break in the future. -s srcdir The path to the directory where the test program is located. This is needed in all cases, except when the test program is being executed from the current directory. The test program will use this path to locate any helper data files or utilities. -v var=value Sets the configuration variable var to the value value. SEE ALSO
atf-run(1), atf(7) BSD
February 6, 2011 BSD
Check Out this Related Man Page
ATF-REPORT(1) BSD General Commands Manual ATF-REPORT(1) NAME
atf-report -- transforms the output of atf-run to different formats SYNOPSIS
atf-report [-o fmt1:path1 [.. -o fmtN:pathN]] atf-report -h DESCRIPTION
atf-report reads the output of atf-run and transforms it to different formats. Some of these are user-friendly and others are machine- parseable, which opens a wide range of possibilities to analyze the results of a test suite's execution. See Output formats below for more details on which these formats are. In the first synopsis form, atf-report reads the output of atf-run through its standard input and, if no -o options are given, prints a user- friendly report on its standard output using the 'ticker' format. If -o options are provided (more than one are allowed), they specify the complete list of reports to generate. They are all generated simultaneously, and for obvious reasons, two reports cannot be written to the same file. Note that the default output is suppressed when -o is provided. In the second synopsis form, atf-report will print information about all supported options and their purpose. The following options are available: -h Shows a short summary of all available options and their purpose. -o fmt:path Adds a new output format. fmt is one of the formats described later on in Output formats. path specifies where the report will be written to. Depending on the chosen format, this may refer to a single file or to a directory. For those formats that write to a single file, specifying a '-' as the path will redirect the report to the standard output. Output formats The following output formats are allowed: csv A machine-parseable Comma-Separated Values (CSV) file. This file contains the results for all test cases and test programs. Test cases are logged using the following syntax: tc, duration, test-program, test-case, result[, reason] The 'result' field for test cases is always one of 'passed', 'skipped' or 'failed'. The last two are always followed by a reason. Test programs are logged with the following syntax: tp, duration, test-program, result[, reason] In this case, the 'result' can be one of: 'passed', which denotes test programs that ran without any failure; 'failed', which refers to test programs in which one or more test cases failed; or 'bogus', which mentions those test programs that failed to exe- cute by some reason. The reason field is only available in the last case. The time required to execute each test case and test program is also provided. You should not rely on the order of the entries in the resulting output. ticker A user-friendly report that shows the progress of the test suite's execution as it operates. This type of report should always be redirected to a virtual terminal, not a file, as it may use control sequences that will make the output unreadable in regular files. xml A report contained in a single XML file. Ideal for later processing with xsltproc(1) to generate nice HTML reports. EXAMPLES
The most simple way of running a test suite is to pipe the output of atf-run through atf-report without any additional flags. This will use the default output format, which is suitable to most users: atf-run | atf-report In some situations, it may be interesting to get a machine-parseable file aside from the standard report. This can be done as follows: atf-run | atf-report -o csv:testsuite.csv -o ticker:- Or if the standard report is not desired, thus achieving completely silent operation: atf-run | atf-report -o csv:testsuite.csv SEE ALSO
atf-run(1), atf(7) BSD
December 16, 2011 BSD