Lines Matching full:test
18 in safe mode with a limited scope. In limited mode, cpu-hotplug test is
20 hotplug test is run on 2% of hotplug capable memory instead of 10%.
23 userspace may wish to use the `Test Harness`_. Tests that need to be
24 run in kernel space may wish to use a `Test Module`_.
61 Kselftest supports "summary" option to make it easier to understand the test
62 results. Please find the detailed individual test results for each test in
74 single test to run, or a list of tests to run.
156 The `-c` option can be used to run all the tests from a test collection, or
212 TEST_PROGS are for test shell scripts. Please ensure shell script has
220 test.
227 * If a test needs specific kernel config options enabled, add a config file in
228 the test directory to enable them.
232 Test Module
237 test module. We can tie the module into the kselftest framework by
238 using a shell script test runner. ``kselftest/module.sh`` is designed
248 Here we show the typical steps to create a test module and tie it into
251 1. Create the test module
253 2. Create the test script that will run (load/unload) the module
258 4. Add test script to makefile e.g. ``tools/testing/selftests/lib/Makefile``
274 A bare bones test module might look like this:
304 Example test script
314 Test Harness
318 test harness is for userspace testing, for kernel space testing see `Test
335 :functions: TH_LOG TEST TEST_SIGNAL FIXTURE FIXTURE_DATA FIXTURE_SETUP