From Fedora Project Wiki
Will's notes (to be integrated into main page)
Control Files
The control file, when interpreted, starts by importing all the symbols from the autotest_lib.client.bin.util
module.[1] This means the control files can use any function defined in common_lib.utils
or bin.base_utils
, among others[2].
Test Results
The result of the test is the exit code of the command. Usually retrieved like so:
self.results = utils.system_output(cmd, retain_output=True)
Further test-level info can be returned by using test.write_test_keyval(dict)
:
extrainfo = dict() for line in self.results.stdout: if line.startswith("kernel version "): extrainfo['kernelver'] = line.split()[3] ... self.write_test_keyval(extrainfo)
- For per-iteration data (performance numbers, etc) there are three methods:
- Just attr:
test.write_attr_keyval(attr_dict)
- Just perf:
test.write_perf_keyval(perf_dict)
- Both:
test.write_iteration_keyval(attr_dict, perf_dict)
- Just attr:
Test Directories
test
objects have the following attributes available[3]:
outputdir eg. results/<job>/<testname.tag> resultsdir eg. results/<job>/<testname.tag>/results profdir eg. results/<job>/<testname.tag>/profiling debugdir eg. results/<job>/<testname.tag>/debug bindir eg. tests/<test> src eg. tests/<test>/src tmpdir eg. tmp/<tempname>_<testname.tag>