aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/tools/testing/selftests/kselftest_harness.h
diff options
context:
space:
mode:
authorShuah Khan <shuahkh@osg.samsung.com>2017-08-23 18:46:00 -0600
committerShuah Khan <shuahkh@osg.samsung.com>2017-08-25 10:17:12 -0600
commit1f87c7c15d77350c4ab1c14d9ab8df2a1f1010d1 (patch)
tree653c116da19cec81e8d9f24b7d3636ed1a7e0aaa /tools/testing/selftests/kselftest_harness.h
parentselftests: change lib.mk RUN_TESTS to take test list as an argument (diff)
downloadwireguard-linux-1f87c7c15d77350c4ab1c14d9ab8df2a1f1010d1.tar.xz
wireguard-linux-1f87c7c15d77350c4ab1c14d9ab8df2a1f1010d1.zip
selftests: lib.mk: change RUN_TESTS to print messages in TAP13 format
Change common RUN_TESTS to print messages in user friendly TAP13 format. This change add TAP13 header at the start of RUN_TESTS target run, and prints the resulting pass/fail messages with test number information in the TAP 13 format for each test in the run tests list. This change covers test scripts as well as test programs. Test programs have an option to use ksft_ API, however test scripts won't be able to. With this change, test scripts can print TAP13 format output without any changes to individual scripts. Test programs can provide TAP13 format output as needed as some tests already do. Tests that haven't been converted will benefit from this change. Tests that are converted benefit from the test counts for all the tests in each test directory. Running firmware tests: make --silent -C tools/testing/selftests/firmware/ run_tests Before the change: modprobe: ERROR: could not insert 'test_firmware': Operation not permitted ./fw_filesystem.sh: /sys/devices/virtual/misc/test_firmware not present You must have the following enabled in your kernel: CONFIG_TEST_FIRMWARE=y selftests: fw_filesystem.sh [FAIL] modprobe: ERROR: could not insert 'test_firmware': Operation not permitted selftests: fw_fallback.sh [FAIL] After the change: TAP version 13 selftests: fw_filesystem.sh ======================================== modprobe: ERROR: could not insert 'test_firmware': Operation not permitted ./fw_filesystem.sh: /sys/devices/virtual/misc/test_firmware not present You must have the following enabled in your kernel: CONFIG_TEST_FIRMWARE=y not ok 1..1 selftests: fw_filesystem.sh [FAIL] selftests: fw_fallback.sh ======================================== modprobe: ERROR: could not insert 'test_firmware': Operation not permitted not ok 1..2 selftests: fw_fallback.sh [FAIL] Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
Diffstat (limited to 'tools/testing/selftests/kselftest_harness.h')
0 files changed, 0 insertions, 0 deletions