fdo-mirrors/libinput
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/libinput/libinput.git synced 2025-12-20 06:50:05 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc: drop leftovers of Check's selective test running

Browse source 
CK_RUN_CASE and CK_RUN_SUITE still work because we're still using check
underneath, but it's better to use the arguments.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
Peter Hutterer 2015-05-20 11:04:13 +10:00
parent f3947c0eb9
commit fcd1cbe5e5
1 changed files with 4 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/test-suite.dox
View file

@ -25,10 +25,10 @@ resulting `/dev/input/eventX` nodes. Some tests require temporary udev rules.
@section test-filtering Selective running of tests
Check enables tests to be grouped into suites and test cases, litest uses
test suites as a general feature-specific grouping (e.g. "touchpad:tap") and
instantiates one test case per device. The --list flag shows the list of
suites and tests.
litest's tests are grouped by test groups and devices. A test group is e.g.
"touchpad:tap" and incorporates all tapping-related tests for touchpads.
Each test function is (usually) run with one or more specific devices.
The `--list` commandline argument shows the list of suites and tests.
@code
$ ./test/test-device --list
device:wheel:
@ -52,16 +52,6 @@ uinput by litest. The "no device" entry signals that litest does not
instantiate a uinput device for a specific test (though the test itself may
instantiate one).
Check provides two filters through environment variables: <b>CK_RUN_SUITE</b>
and <b>CK_RUN_CASE</b>. They may be used independently or combined to narrow
down the set of tests to run. For example:
@code
$ CK_RUN_SUITE="device:wheel" ./test/test-device
$ CK_RUN_CASE="wheel only" ./test/test-device
$ CK_RUN_SUITE="device:wheel" CK_RUN_CASE="wheel only" ./test/test-device
@endcode
The `--filter-test` argument enables selective running of tests through
basic shell-style function name matching. For example: