| Main index | Section 1 | Options |
The JUnit output is static and self-contained, so it can easily be plugged into any continuous integration system, like Jenkins.
The following subcommand options are recognized:
| | |
| Specifies the file into which to store the JUnit report. | |
| | |
|
Specifies the results file to operate on.
Defaults to
'LATEST',
which causes
kyua report-junit
to automatically load the latest results file from the current test suite.
The following values are accepted: | |
| 'LATEST' | |
| Requests the load of the latest results file available for the test suite rooted at the current directory. | |
| Directory | |
| Requests the load of the latest results file available for the test suite rooted at the given directory. | |
| Test suite name | |
| Requests the load of the latest results file available for the given test suite. | |
| Results identifier | |
| Requests the load of a specific results file. | |
| Explicit file name (aka everything else) | |
| Load the specified results file. | |
See Results files for more details.
Results files support identifier-based lookups and also path name lookups. The differences between the two are described below.
The default naming scheme for the results files provides simple support for identifier-based lookups and historical recording of test suite runs. Each results file is given an identifier derived from the test suite that generated it and the time the test suite was run. Kyua can later look up results files by these fields.
The identifier follows this pattern:
<test_suite>.<YYYYMMDD>-<HHMMSS>-<uuuuuu>
where 'test_suite' is the path to the root of the test suite that was run with all slashes replaced by underscores and 'YYYYMMDD-HHMMSS-uuuuuu' is a timestamp with microsecond resolution.
When using the default naming scheme, results files are stored in the ~/.kyua/store/ subdirectory and each file holds a name of the form:
~/.kyua/store/results.<identifier>.db
Results files are simple SQLite databases with the schema described in the /usr/share/kyua/store/schema_v?.sql files. For details on the schema, please refer to the heavily commented SQL file.
Additional exit codes may be returned as described in kyua(1).
kyua test -k /usr/tests/Kyuafile
the two executions will generate two different files with names like:
~/.kyua/store/results.usr_tests.20140731-150500-196784.db ~/.kyua/store/results.usr_tests.20140731-151730-997451.db
Taking advantage of the default naming scheme, the following commands would all generate a report for the results of the latest execution of the test suite:
cd /usr/tests && kyua report-junit cd /usr/tests && kyua report-junit --results-file=LATEST kyua report-junit --results-file=/usr/tests kyua report-junit --results-file=usr_tests kyua report-junit --results-file=usr_tests.20140731-151730-997451
But it is also possible to explicitly load data for older runs or from explicitly-named files:
kyua report-junit \
--results-file=usr_tests.20140731-150500-196784
kyua report-junit \
--results-file=~/.kyua/store/results.usr_tests.20140731-150500-196784.db
| KYUA-REPORT-JUNIT (1) | October 13, 2014 |
| Main index | Section 1 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
| “ | One of the advantages of using UNIX to teach an operating systems course is the sources and documentation will easily fit into a student's briefcase. | ” |
| — John Lions | ||