selftests: Introduce minimal shared logic for running tests
This adds a Make include file which most selftests can then include to get the run_tests logic. On its own this has the advantage of some reduction in repetition, and also means the pass/fail message is defined in fewer places. However the key advantage is it will allow us to implement install very simply in a subsequent patch. The default implementation just executes each program in $(TEST_PROGS). We use a variable to hold the default implementation of $(RUN_TESTS) because that gives us a clean way to override it if necessary, ie. using override. The mount, memory-hotplug and mqueue tests use that to provide a different implementation. Tests are not run via /bin/bash, so if they are scripts they must be executable, we add a+x to several. Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
Showing
File mode changed from 100644 to 100755
tools/testing/selftests/efivarfs/efivarfs.sh
100644 → 100755
File mode changed from 100644 to 100755
File mode changed from 100644 to 100755
File mode changed from 100644 to 100755
File mode changed from 100644 to 100755
tools/testing/selftests/net/run_afpackettests
100644 → 100755
File mode changed from 100644 to 100755
tools/testing/selftests/net/run_netsocktests
100644 → 100755
File mode changed from 100644 to 100755
tools/testing/selftests/sysctl/run_numerictests
100644 → 100755
File mode changed from 100644 to 100755
tools/testing/selftests/sysctl/run_stringtests
100644 → 100755
File mode changed from 100644 to 100755
tools/testing/selftests/vm/run_vmtests
100644 → 100755
File mode changed from 100644 to 100755
Please register or sign in to comment