Lines Matching refs:suite

1 .. _test-suite:
4 libinput test suite
7 libinput's primary test suite can be invoked with
11 	$ sudo ./builddir/libinput-test-suite
13 When developing libinput, the ``libinput-test-suite`` should always be
18 the full suite when development is done finished.
20 .. note:: The test suite relies on udev and the kernel, specifically uinput.
22 	interfere with your running session. The test suite is not suitable
27 ``meson test -C builddir`` (or ``ninja test``). The ``libinput-test-suite`` is
30 The upstream CI runs all these tests but not the ``libinput-test-suite``.
36 Job control in the test suite
39 The test suite runner has a make-like job control enabled by the ``-j`` or
43 and disable parallel tests. The test suite automatically disables parallel
52 uinput devices created by the test suite are usually recognised by X as
69 root, the test suite runner will exit with status 77, an exit status
88      $ ./builddir/libinput-test-suite --list
127 In the above example, the "pointer:left-handed" suite contains multiple
143      $ ./builddir/libinput-test-suite --filter-test="*1fg_tap*"
153      $ ./builddir/libinput-test-suite --filter-device="synaptics*"
163      $ ./builddir/libinput-test-suite --filter-group="touchpad:*hover*"
182      $ ./builddir/libinput-test-suite --verbose
188 Installing the test suite
191 If libinput is configured to install the tests, the test suite is available
192 as the ``libinput test-suite`` command. When run as installed binary, the
193 behavior of the test suite changes:
196 - no system-wide quirks are installed by the test suite, only those specific
201 It is not advisable to run ``libinput test-suite`` on a production machine.
202 Data loss may occur. The primary use-case for the installed test suite is
205 .. note:: The ``prefix`` is still used by the test suite. For verification
206 	of a system package, the test suite must be configured with the same prefix.
222 Tests invoked by ``meson test`` are grouped into test suites, the test suite
232 The suite names can be provided as filters to ``meson test
233 --suite=<suitename>`` or ``meson test --no-suite=<suitename>``.
239    $ meson test --no-suite=machine  # only run container-friendly tests
240    $ meson test --suite=valgrind --setup=valgrind  # run all valgrind-compatible tests
241    $ meson test --no-suite=root  # run all tests not requiring root