fdo-mirrors/libinput
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/libinput/libinput.git synced 2026-01-13 20:20:17 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
libinput/test/Makefile.am

182 lines
5.9 KiB
Text
Raw Normal View History

Add the framework for a test suite Just the scaffolding, no actual tests just yet Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 14:17:35 +10:00
if BUILD_TESTS
Add our own version of linux/input.h Avoids having to #define any values we're trying to use. Header file is from Linux 3.15-rc8. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-06-03 07:51:37 +10:00
AM_CPPFLAGS = -I$(top_srcdir)/include \
-I$(top_srcdir)/src \
$(CHECK_CFLAGS) \
test/Makefile.am: Also add LIBUDEV_CFLAGS to AM_CPPFLAGS Signed-off-by: Jonas Ådahl <jadahl@gmail.com>
2014-06-28 22:40:23 +02:00
$(LIBEVDEV_CFLAGS) \
test: fix distcheck Broken in e0b200caa60830 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-12-07 10:28:40 +10:00
$(LIBUDEV_CFLAGS) \
-I$(top_builddir)/src # for libinput-version.h
Add a device test suite A rather large commit, copied from a similar (almost identical) suite in libtouchpad and ported for libinput. The goal here is to make testing for various devices easy, so the litest ("libinput test") wrappers do that. The idea is that each device has some features, and tests are likely to exercise some features or won't work with other features. Each test case takes a list of required features and a list of excluded features. The test suite will create a new test case for each device in the suite that matches that set. For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would run on clickpads only, not on touchpads with buttons. check supports suites and test cases, both named. We wrap that so that each named set of cases we add are a test suite, with the set of devices being the test cases. i.e. litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY); adds a suite named "foo:bar" and test cases for both devices given, with their shortnames as test case name, resulting in: "foo:bar", "trackpoint" "foo:bar", "clickpad" ... Multiple test functions can be added to a suite. For tests without a device requirement there is litest_add_no_device_test(...). The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow the set of test cases. The test suite detects when run inside a debugger and disables fork mode (the default). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
Hook up gcov for coverage reports ./configure --enable-gcov adds the required flags to link everything ready for gcov. A new make gcov target runs the test suite, then pulls all the gcov bits together into ./test/gcov-reports/ including a summary file. The script to pull everything out is used in libevdev too, we just have an extra condition here to ignore the selftest gcov bits (it overwrites the useful litest.c coverage output). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-05 15:21:24 +10:00
AM_CFLAGS = $(GCC_CFLAGS) $(GCOV_CFLAGS)
test: silence compiler warning for C++ build test cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++ [enabled by default] Since gcc also complains about adding -Wno-strict-prototypes we have to handle the two separately. A side-effect here: now that we promote the GCC_CFLAGS to AM_CFLAGS, litest.la is built with the correct CFLAGS too. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-06 09:38:35 +10:00
AM_CXXFLAGS = $(GCC_CXXFLAGS)
configure: check for -lm through AC_CHECK_LIB Saves us from manually appending it everywhere Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2014-07-03 09:29:22 +10:00
TEST_LIBS = liblitest.la $(CHECK_LIBS) $(LIBUDEV_LIBS) $(LIBEVDEV_LIBS) $(top_builddir)/src/libinput.la
Add a device test suite A rather large commit, copied from a similar (almost identical) suite in libtouchpad and ported for libinput. The goal here is to make testing for various devices easy, so the litest ("libinput test") wrappers do that. The idea is that each device has some features, and tests are likely to exercise some features or won't work with other features. Each test case takes a list of required features and a list of excluded features. The test suite will create a new test case for each device in the suite that matches that set. For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would run on clickpads only, not on touchpads with buttons. check supports suites and test cases, both named. We wrap that so that each named set of cases we add are a test suite, with the set of devices being the test cases. i.e. litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY); adds a suite named "foo:bar" and test cases for both devices given, with their shortnames as test case name, resulting in: "foo:bar", "trackpoint" "foo:bar", "clickpad" ... Multiple test functions can be added to a suite. For tests without a device requirement there is litest_add_no_device_test(...). The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow the set of test cases. The test suite detects when run inside a debugger and disables fork mode (the default). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
noinst_LTLIBRARIES = liblitest.la
liblitest_la_SOURCES = \
litest.h \
litest-int.h \
touchpad: if an external touchpad and keyboard share a VID/PID assume dwt This requires to expand the blacklisting to be a bit more specific so we don't initialize dwt config on devices that won't need it. https://bugs.freedesktop.org/show_bug.cgi?id=99140 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-12-19 15:36:34 +10:00
litest-device-acer-hawaii-keyboard.c \
litest-device-acer-hawaii-touchpad.c \
test: prefix all test device files with litest-device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:06:11 +10:00
litest-device-alps-semi-mt.c \
litest-device-alps-dualpoint.c \
evdev: only reject devices with missing MT x/y if they're MT devices A fake MT device may have ABS_MT_POSITION_X but not Y. In this case we don't care, because we don't handle those axes anyway. http://bugs.freedesktop.org/show_bug.cgi?id=93474 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-12-23 15:15:29 +10:00
litest-device-anker-mouse-kbd.c \
touchpad: mark the Apple onebutton touchpad as clickfinger-default We don't initialize click methods on devices with physical buttons. This model is a special case, it's not a clickpad but it only has one button (because one button is all you ever need and whatnot). https://bugs.freedesktop.org/show_bug.cgi?id=99283 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-10 09:22:16 +10:00
litest-device-apple-appletouch.c \
touchpad: fix DWT pairing for Macbook Pro 2015 Label internal keyboards through the udev hwdb and only pair the internal (usb) Apple touchpads with those keyboards labelled as such. https://bugs.freedesktop.org/show_bug.cgi?id=93367 Co-authored-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-12-13 22:27:55 -08:00
litest-device-apple-internal-keyboard.c \
test: add an apple magicmouse device This device has a touchpad on the mouse but it's labeled as mouse. For litest we only label it as LITEST_MOUSE feature and test the touchpad directly on the device. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-06-15 19:36:56 +10:00
litest-device-apple-magicmouse.c \
evdev: init pointer acceleration for any device with pointer cap and rel x/y The Asus RoG Gladius exposes two event nodes, one mouse, one keyboard. The keyboard node has REL_X/Y and REL_HWHEEL on top of the various key bits and ABS_VOLUME. The keyboard node does not have BTN_* set, udev tags this device as a keyboard only, not as a pointer but we still initialize the pointer caps for it because of the wheel. When moving this mouse, some deltas (ca "1 in every 20") are sent through the keyboard node, causing a crash because we never initialized pointer acceleration. https://bugzilla.redhat.com/show_bug.cgi?id=1275407 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-10-28 09:13:24 +10:00
litest-device-asus-rog-gladius.c \
test: prefix all test device files with litest-device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:06:11 +10:00
litest-device-atmel-hover.c \
litest-device-bcm5974.c \
test: add a device and test for udev-set calibration values Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-11-25 14:59:27 +10:00
litest-device-calibrated-touchscreen.c \
evdev: disable the mode button on the Cyborg RAT 5 This button sends a release N, press N+1 on each press, cycling through the three event codes supported. This causes a stuck button since the current mode is never released. Long-term this better served by a set of switches that toggle accordingly, for now disable the button codes. https://bugs.freedesktop.org/show_bug.cgi?id=92127 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-01-29 10:09:13 +10:00
litest-device-cyborg-rat-5.c \
test: add an Elantech touchpad device This is an old recording and predates properties. It's not a clickpad, we assume INPUT_PROP_POINTER is set. From: https://bugs.freedesktop.org/attachment.cgi?id=57154 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:11:11 +10:00
litest-device-elantech-touchpad.c \
test: prefix all test device files with litest-device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:06:11 +10:00
litest-device-generic-singletouch.c \
test: add the HUION PenTablet device Tablet with pressure and proximity but no distance axis. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-12-11 10:53:06 +10:00
litest-device-huion-pentablet.c \
test: prefix all test device files with litest-device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:06:11 +10:00
litest-device-keyboard.c \
test: add a keyboard test device with all codes enabled Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-05-10 12:22:40 +10:00
litest-device-keyboard-all-codes.c \
test: prefix all test device files with litest-device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:06:11 +10:00
litest-device-keyboard-razer-blackwidow.c \
test: add tests for lid switch Ship a custom udev rule for the test device until systemd v333 is commonplace. Signed-off-by: James Ye <jye836@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-20 16:54:16 +11:00
litest-device-lid-switch.c \
switch: for surface 3 tablets, write the lid open to the device These tablets only ever give us a close event, the open event is broken. So when we detect keyboard events, fix the kernel device's state by writing the event to the fd. We still sync the lid state manually, in case this fails and we don't get the SW_LID through the normal event sequence. If it works fine, the real open event will just be ignored. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-30 12:58:37 +10:00
litest-device-lid-switch-surface3.c \
test: prefix all test device files with litest-device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:06:11 +10:00
litest-device-logitech-trackball.c \
litest-device-nexus4-touch-screen.c \
litest-device-magic-trackpad.c \
litest-device-mouse.c \
test: add wheel tilt tests Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-11-28 11:08:01 +10:00
litest-device-mouse-wheel-tilt.c \
test: prefix all test device files with litest-device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:06:11 +10:00
litest-device-mouse-roccat.c \
litest-device-mouse-low-dpi.c \
test: add a device to check MOUSE_WHEEL_CLICK_ANGLE handling Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-11-09 10:18:17 +10:00
litest-device-mouse-wheel-click-angle.c \
evdev: implement support for the MOUSE_WHEEL_CLICK_COUNT property Not all mice have a click angle with integer degrees. The new MOUSE_WHEEL_CLICK_COUNT property specifies how many clicks per full rotation, the angle can be calculated from that. See https://github.com/systemd/systemd/pull/4440 for more information CLICK_COUNT overrides CLICK_ANGLE, so we check for the former first and then fall back to the angle if need be. No changes to the user-facing API. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-10-28 15:08:32 +10:00
litest-device-mouse-wheel-click-count.c \
test: prefix all test device files with litest-device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:06:11 +10:00
litest-device-ms-surface-cover.c \
litest-device-protocol-a-touch-screen.c \
litest-device-qemu-usb-tablet.c \
litest-device-synaptics.c \
litest-device-synaptics-hover.c \
touchpad: if we have a serio keyboard, override any previous dwt pairing If a USB keyboard like the YubiKey is found before the internal keyboard, it will be paired with the touchpad when it is seen. The internal keyboard is seen later bug ignored because we already have a keyboard paired with the touchpad. This is obviously wrong. For now, give priority to serio keyboards, and override existing dwt pairings with the new keyboard. https://bugs.freedesktop.org/show_bug.cgi?id=93983 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-02-04 11:20:38 +10:00
litest-device-synaptics-i2c.c \
test: add a synaptics RMI4 test device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-12 13:37:43 +10:00
litest-device-synaptics-rmi4.c \
test: prefix all test device files with litest-device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:06:11 +10:00
litest-device-synaptics-st.c \
litest-device-synaptics-t440.c \
litest-device-synaptics-x1-carbon-3rd.c \
litest-device-trackpoint.c \
litest-device-touch-screen.c \
evdev: always defuzz absolute touchscreens If a touchscreen has a fuzz value use it for motion hysteresis similar to how we do it for a touchpad. This stops pointer wobbles as seen in https://bugs.freedesktop.org/show_bug.cgi?id=94918 It's up to the system to override or set the kernel's fuzz value correctly, i.e. a udev hwdb entry is required where the kernel driver does not set it. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2016-04-14 15:21:50 +10:00
litest-device-touchscreen-fuzz.c \
test: rename wacom test devices to a consistent naming scheme Use the model names in the file name and append pad/pen/finger as appropriate Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-16 11:11:45 +10:00
litest-device-wacom-bamboo-16fg-pen.c \
litest-device-wacom-cintiq-12wx-pen.c \
test: add a Cintiq 13 HDT test device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-07-12 14:25:23 +10:00
litest-device-wacom-cintiq-13hdt-finger.c \
litest-device-wacom-cintiq-13hdt-pad.c \
litest-device-wacom-cintiq-13hdt-pen.c \
test: rename wacom test devices to a consistent naming scheme Use the model names in the file name and append pad/pen/finger as appropriate Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-16 11:11:45 +10:00
litest-device-wacom-cintiq-24hd-pen.c \
test: add pad mode group tests Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com> Reviewed-by: Carlos Garnacho <carlosg@gnome.org>
2016-06-06 14:01:02 +10:00
litest-device-wacom-cintiq-24hdt-pad.c \
test: add an Wacom EKR test device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com> Reviewed-by: Carlos Garnacho <carlosg@gnome.org>
2016-06-08 09:49:17 +10:00
litest-device-wacom-ekr.c \
test: add a Wacom HID 4800 test device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com>
2016-08-22 17:16:21 +10:00
litest-device-wacom-hid4800-pen.c \
test: tablet pad tests Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com> Reviewed-by: Carlos Garnacho <carlosg@gnome.org>
2016-02-05 10:57:37 +10:00
litest-device-wacom-intuos3-pad.c \
test: rename wacom test devices to a consistent naming scheme Use the model names in the file name and append pad/pen/finger as appropriate Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-16 11:11:45 +10:00
litest-device-wacom-intuos5-finger.c \
test: tablet pad tests Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jason Gerecke <jason.gerecke@wacom.com> Reviewed-by: Carlos Garnacho <carlosg@gnome.org>
2016-02-05 10:57:37 +10:00
litest-device-wacom-intuos5-pad.c \
test: rename wacom test devices to a consistent naming scheme Use the model names in the file name and append pad/pen/finger as appropriate Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-16 11:11:45 +10:00
litest-device-wacom-intuos5-pen.c \
litest-device-wacom-isdv4-e6-pen.c \
litest-device-wacom-isdv4-e6-finger.c \
Merge branch 'master' into tablet-support
2015-07-14 13:13:11 +10:00
litest-device-waltop-tablet.c \
test: prefix all test device files with litest-device Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-10 14:06:11 +10:00
litest-device-wheel-only.c \
litest-device-xen-virtual-pointer.c \
litest-device-vmware-virtual-usb-mouse.c \
touchpad: if we have a serio keyboard, override any previous dwt pairing If a USB keyboard like the YubiKey is found before the internal keyboard, it will be paired with the touchpad when it is seen. The internal keyboard is seen later bug ignored because we already have a keyboard paired with the touchpad. This is obviously wrong. For now, give priority to serio keyboards, and override existing dwt pairings with the new keyboard. https://bugs.freedesktop.org/show_bug.cgi?id=93983 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-02-04 11:20:38 +10:00
litest-device-yubikey.c \
Add a device test suite A rather large commit, copied from a similar (almost identical) suite in libtouchpad and ported for libinput. The goal here is to make testing for various devices easy, so the litest ("libinput test") wrappers do that. The idea is that each device has some features, and tests are likely to exercise some features or won't work with other features. Each test case takes a list of required features and a list of excluded features. The test suite will create a new test case for each device in the suite that matches that set. For example, the set of required LITEST_TOUCHPAD, excluded LITEST_BUTTON would run on clickpads only, not on touchpads with buttons. check supports suites and test cases, both named. We wrap that so that each named set of cases we add are a test suite, with the set of devices being the test cases. i.e. litest_add("foo:bar", some_test_function, LITEST_ANY, LITEST_ANY); adds a suite named "foo:bar" and test cases for both devices given, with their shortnames as test case name, resulting in: "foo:bar", "trackpoint" "foo:bar", "clickpad" ... Multiple test functions can be added to a suite. For tests without a device requirement there is litest_add_no_device_test(...). The environment variables CK_RUN_SUITE and CK_RUN_CASE can be used to narrow the set of test cases. The test suite detects when run inside a debugger and disables fork mode (the default). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 15:02:11 +10:00
litest.c
Split libinput-util into a noinst helper library Fixes distcheck (automake 1.14.1) make[2]: Entering directory '....../libinput-0.7.0/_build/test' Makefile:926: ../src/.deps/libinput-util.Plo: No such file or directory make[2]: *** No rule to make target '../src/.deps/libinput-util.Plo'. Stop. make[2]: Leaving directory '....../libinput/libinput-0.7.0/_build/test' Makefile:412: recipe for target 'distclean-recursive' failed That was the only place we used subdir objects, so we can drop it from configure now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-05 12:52:22 +10:00
liblitest_la_LIBADD = $(top_builddir)/src/libinput-util.la
test: always install our own udev rule/hwdb files for tests We can't rely on the system having these files installed, at least not in the latest version that we'd like. Copy them over from the source directory into the /run/ and /etc/ directories for each test and update udev and the hwdb. This ensures the tags we set in the hwdb file are always set, regardless of the system configuration. Note that the /run/udev/* files need to have a different filename to the ones we ship to avoid getting overridden by local configuration. systemd does not have support for /run/udev/hwdb.d [1]. So our hwdb.d file is in /etc/udev/hwdb.d instead and marked them with a REMOVEME and a comment that if that file is left after the tests, it should be removed by the user. [1] https://github.com/systemd/systemd/issues/127 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-06-05 10:52:04 +10:00
liblitest_la_CFLAGS = $(AM_CFLAGS) \
test: Make udev path variables more explicitly named This is to make room for more types of rules files. Signed-off-by: Jonas Ådahl <jadahl@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-27 15:53:53 +08:00
-DLIBINPUT_MODEL_QUIRKS_UDEV_RULES_FILE="\"$(abs_top_builddir)/udev/90-libinput-model-quirks-litest.rules\"" \
Ignore test devices for libinput contexts not run from the test suite Add a LIBINPUT_TEST_DEVICE udev parameter to test devices created by the test suite. When an application tries to add such a device to the path backend or when the udev backend discovers such a device, it will be ignored. Only the context when run via the test suite will actually handle these devices. Doing this will enable a user to run the libinput test suite on a system running libinput without having the test suite devices interfering with the actual system. Note that X.org users running an input device driver that is not the libinput X input driver will still need to manually configure the X server to ignore such devices (see test/50-litest.conf). Signed-off-by: Jonas Ådahl <jadahl@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-27 16:08:04 +08:00
-DLIBINPUT_MODEL_QUIRKS_UDEV_HWDB_FILE="\"$(abs_top_srcdir)/udev/90-libinput-model-quirks.hwdb\"" \
-DLIBINPUT_TEST_DEVICE_RULES_FILE="\"$(abs_top_srcdir)/udev/80-libinput-test-device.rules\""
test: add a backtrace facility to litest The check unit test framework isn't particularly suited to having ck_assert* calls in helper functions. A failed assertion in a helper function or the litest framework merely gives us a the failed line in litest.c. which doesn't tell us which test actually failed. Add a backtracing facility with litest_backtrace(). And since this requires wrapping all ck_assert macros with litest_assert() this patch ended up replacing/duplicating a bunch of ck_assert_* bits. So rather than ck_assert_int_eq() we now use litest_assert_int_eq(), etc. in the litest framework itself. The int comparison macros are more type-safe than ck_assert()'s macros which just cast all the ints to intmax_t. Backtrace is spewed to stderr, which is good enough for debugging. Example backtrace: FAILED COMPARISON: status != expected Resolved to: 0 != 0 in disable_button_scrolling() (pointer.c:115) Backtrace: 0: ./test/test-pointer (litest_fail_comparison_int+0xab) [0x40973b] 1: ./test/test-pointer (disable_button_scrolling+0x174) [0x40421b] 2: ./test/test-pointer (middlebutton_middleclick+0x40) [0x40829c] 3: /lib64/libcheck.so.0 (srunner_run+0x7f5) [0x7f0e8a277025] 4: ./test/test-pointer (litest_run+0x107) [0x40a42b] 5: ./test/test-pointer (main+0x2fa) [0x4090e7] 6: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f0e88f5e790] 7: ./test/test-pointer (_start+0x29) [0x403ce9] 8: ? (?+0x29) [0x29] litest_backtrace() itself is copied from xserver/os/backtrace.c which git blame attributes to Marcin. CC: Marcin Slusarz <marcin.slusarz@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-05-04 09:13:22 +10:00
if HAVE_LIBUNWIND
liblitest_la_LIBADD += $(LIBUNWIND_LIBS) -ldl
liblitest_la_CFLAGS += $(LIBUNWIND_CFLAGS)
endif
Add the framework for a test suite Just the scaffolding, no actual tests just yet Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 14:17:35 +10:00
test: swap order for selftest and test suite Making sure the test suite behaves as expected should be done before we use it. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-09 11:01:59 +10:00
run_tests = \
test-litest-selftest \
libinput-test-suite-runner
test: add a backtrace facility to litest The check unit test framework isn't particularly suited to having ck_assert* calls in helper functions. A failed assertion in a helper function or the litest framework merely gives us a the failed line in litest.c. which doesn't tell us which test actually failed. Add a backtracing facility with litest_backtrace(). And since this requires wrapping all ck_assert macros with litest_assert() this patch ended up replacing/duplicating a bunch of ck_assert_* bits. So rather than ck_assert_int_eq() we now use litest_assert_int_eq(), etc. in the litest framework itself. The int comparison macros are more type-safe than ck_assert()'s macros which just cast all the ints to intmax_t. Backtrace is spewed to stderr, which is good enough for debugging. Example backtrace: FAILED COMPARISON: status != expected Resolved to: 0 != 0 in disable_button_scrolling() (pointer.c:115) Backtrace: 0: ./test/test-pointer (litest_fail_comparison_int+0xab) [0x40973b] 1: ./test/test-pointer (disable_button_scrolling+0x174) [0x40421b] 2: ./test/test-pointer (middlebutton_middleclick+0x40) [0x40829c] 3: /lib64/libcheck.so.0 (srunner_run+0x7f5) [0x7f0e8a277025] 4: ./test/test-pointer (litest_run+0x107) [0x40a42b] 5: ./test/test-pointer (main+0x2fa) [0x4090e7] 6: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f0e88f5e790] 7: ./test/test-pointer (_start+0x29) [0x403ce9] 8: ? (?+0x29) [0x29] litest_backtrace() itself is copied from xserver/os/backtrace.c which git blame attributes to Marcin. CC: Marcin Slusarz <marcin.slusarz@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-05-04 09:13:22 +10:00
test: Add include from C++ build test
2014-03-24 23:45:05 +01:00
build_tests = \
test-build-cxx \
test-build-linker \
test-build-pedantic-c99 \
test-build-std-gnuc90
Add the framework for a test suite Just the scaffolding, no actual tests just yet Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 14:17:35 +10:00
noinst_PROGRAMS = $(build_tests) $(run_tests)
add simple symbols leak checker This patch adds simple script that compares libinput.sym file to the functions that are marked by LIBINPUT_EXPORT. This script is added to make check target. Signed-off-by: Marek Chalupa <mchqwerty@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-02-12 09:25:36 -05:00
noinst_SCRIPTS = symbols-leak-test
Disable test runs on 'distcheck' The tests require the creation of udev devices which in turn require root and usually cause distcheck runs to fail. Add a new option to disable the *running* of tests at distcheck (we still want to build them). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-11-14 09:35:56 +10:00
if RUN_TESTS
add simple symbols leak checker This patch adds simple script that compares libinput.sym file to the functions that are marked by LIBINPUT_EXPORT. This script is added to make check target. Signed-off-by: Marek Chalupa <mchqwerty@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-02-12 09:25:36 -05:00
TESTS = $(run_tests) symbols-leak-test
Disable test runs on 'distcheck' The tests require the creation of udev devices which in turn require root and usually cause distcheck runs to fail. Add a new option to disable the *running* of tests at distcheck (we still want to build them). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2016-11-14 09:35:56 +10:00
endif
Add the framework for a test suite Just the scaffolding, no actual tests just yet Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 14:17:35 +10:00
test: prefix all test source files with "test-" They weren't originally prefixed but the various tests were, but now that we only have one test runner binary anyway, the prefix helps sorting the files easily within e.g. gcov results. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-13 10:25:56 +10:00
libinput_test_suite_runner_SOURCES = test-udev.c \
test-path.c \
test-pointer.c \
test-touch.c \
test-log.c \
test-tablet.c \
test-pad.c \
test-touchpad.c \
test-touchpad-tap.c \
test-touchpad-buttons.c \
test-trackpoint.c \
test-trackball.c \
test-misc.c \
test-keyboard.c \
test-device.c \
test: add tests for lid switch Ship a custom udev rule for the test device until systemd v333 is commonplace. Signed-off-by: James Ye <jye836@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-20 16:54:16 +11:00
test-gestures.c \
test-lid.c
test: merge all tests into a single binary Call it a libinput-test-suite-runner, in subsequent patches we'll handle doing parallel tests ourselves instead of relying on automake features. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-07-22 13:16:49 +10:00
libinput_test_suite_runner_CFLAGS = $(AM_CFLAGS) -DLIBINPUT_LT_VERSION="\"$(LIBINPUT_LT_VERSION)\""
libinput_test_suite_runner_LDADD = $(TEST_LIBS)
libinput_test_suite_runner_LDFLAGS = -no-install
test: add a couple of basic gesture tests 3finger swipe, pinch and spread. While we expect the pinch/spread to have a zero angle, the discrete coordinates we use cause some angle, but below 1 degree. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-07-07 11:52:05 +10:00
test: add a backtrace facility to litest The check unit test framework isn't particularly suited to having ck_assert* calls in helper functions. A failed assertion in a helper function or the litest framework merely gives us a the failed line in litest.c. which doesn't tell us which test actually failed. Add a backtracing facility with litest_backtrace(). And since this requires wrapping all ck_assert macros with litest_assert() this patch ended up replacing/duplicating a bunch of ck_assert_* bits. So rather than ck_assert_int_eq() we now use litest_assert_int_eq(), etc. in the litest framework itself. The int comparison macros are more type-safe than ck_assert()'s macros which just cast all the ints to intmax_t. Backtrace is spewed to stderr, which is good enough for debugging. Example backtrace: FAILED COMPARISON: status != expected Resolved to: 0 != 0 in disable_button_scrolling() (pointer.c:115) Backtrace: 0: ./test/test-pointer (litest_fail_comparison_int+0xab) [0x40973b] 1: ./test/test-pointer (disable_button_scrolling+0x174) [0x40421b] 2: ./test/test-pointer (middlebutton_middleclick+0x40) [0x40829c] 3: /lib64/libcheck.so.0 (srunner_run+0x7f5) [0x7f0e8a277025] 4: ./test/test-pointer (litest_run+0x107) [0x40a42b] 5: ./test/test-pointer (main+0x2fa) [0x4090e7] 6: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f0e88f5e790] 7: ./test/test-pointer (_start+0x29) [0x403ce9] 8: ? (?+0x29) [0x29] litest_backtrace() itself is copied from xserver/os/backtrace.c which git blame attributes to Marcin. CC: Marcin Slusarz <marcin.slusarz@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-05-04 09:13:22 +10:00
test_litest_selftest_SOURCES = litest-selftest.c litest.c litest-int.h litest.h
test: always install our own udev rule/hwdb files for tests We can't rely on the system having these files installed, at least not in the latest version that we'd like. Copy them over from the source directory into the /run/ and /etc/ directories for each test and update udev and the hwdb. This ensures the tags we set in the hwdb file are always set, regardless of the system configuration. Note that the /run/udev/* files need to have a different filename to the ones we ship to avoid getting overridden by local configuration. systemd does not have support for /run/udev/hwdb.d [1]. So our hwdb.d file is in /etc/udev/hwdb.d instead and marked them with a REMOVEME and a comment that if that file is left after the tests, it should be removed by the user. [1] https://github.com/systemd/systemd/issues/127 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2015-06-05 10:52:04 +10:00
test_litest_selftest_CFLAGS = -DLITEST_DISABLE_BACKTRACE_LOGGING -DLITEST_NO_MAIN $(liblitest_la_CFLAGS)
test: add a backtrace facility to litest The check unit test framework isn't particularly suited to having ck_assert* calls in helper functions. A failed assertion in a helper function or the litest framework merely gives us a the failed line in litest.c. which doesn't tell us which test actually failed. Add a backtracing facility with litest_backtrace(). And since this requires wrapping all ck_assert macros with litest_assert() this patch ended up replacing/duplicating a bunch of ck_assert_* bits. So rather than ck_assert_int_eq() we now use litest_assert_int_eq(), etc. in the litest framework itself. The int comparison macros are more type-safe than ck_assert()'s macros which just cast all the ints to intmax_t. Backtrace is spewed to stderr, which is good enough for debugging. Example backtrace: FAILED COMPARISON: status != expected Resolved to: 0 != 0 in disable_button_scrolling() (pointer.c:115) Backtrace: 0: ./test/test-pointer (litest_fail_comparison_int+0xab) [0x40973b] 1: ./test/test-pointer (disable_button_scrolling+0x174) [0x40421b] 2: ./test/test-pointer (middlebutton_middleclick+0x40) [0x40829c] 3: /lib64/libcheck.so.0 (srunner_run+0x7f5) [0x7f0e8a277025] 4: ./test/test-pointer (litest_run+0x107) [0x40a42b] 5: ./test/test-pointer (main+0x2fa) [0x4090e7] 6: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f0e88f5e790] 7: ./test/test-pointer (_start+0x29) [0x403ce9] 8: ? (?+0x29) [0x29] litest_backtrace() itself is copied from xserver/os/backtrace.c which git blame attributes to Marcin. CC: Marcin Slusarz <marcin.slusarz@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-05-04 09:13:22 +10:00
test_litest_selftest_LDADD = $(TEST_LIBS)
test_litest_selftest_LDFLAGS = -no-install
test: add missing libunwind cflags to test-litest-selftest Signed-off-by: JoonCheol Park <jooncheol@gmail.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-06-11 16:38:02 +09:00
if HAVE_LIBUNWIND
test_litest_selftest_LDADD += $(LIBUNWIND_LIBS) -ldl
test_litest_selftest_CFLAGS += $(LIBUNWIND_CFLAGS)
endif
test: add a backtrace facility to litest The check unit test framework isn't particularly suited to having ck_assert* calls in helper functions. A failed assertion in a helper function or the litest framework merely gives us a the failed line in litest.c. which doesn't tell us which test actually failed. Add a backtracing facility with litest_backtrace(). And since this requires wrapping all ck_assert macros with litest_assert() this patch ended up replacing/duplicating a bunch of ck_assert_* bits. So rather than ck_assert_int_eq() we now use litest_assert_int_eq(), etc. in the litest framework itself. The int comparison macros are more type-safe than ck_assert()'s macros which just cast all the ints to intmax_t. Backtrace is spewed to stderr, which is good enough for debugging. Example backtrace: FAILED COMPARISON: status != expected Resolved to: 0 != 0 in disable_button_scrolling() (pointer.c:115) Backtrace: 0: ./test/test-pointer (litest_fail_comparison_int+0xab) [0x40973b] 1: ./test/test-pointer (disable_button_scrolling+0x174) [0x40421b] 2: ./test/test-pointer (middlebutton_middleclick+0x40) [0x40829c] 3: /lib64/libcheck.so.0 (srunner_run+0x7f5) [0x7f0e8a277025] 4: ./test/test-pointer (litest_run+0x107) [0x40a42b] 5: ./test/test-pointer (main+0x2fa) [0x4090e7] 6: /lib64/libc.so.6 (__libc_start_main+0xf0) [0x7f0e88f5e790] 7: ./test/test-pointer (_start+0x29) [0x403ce9] 8: ? (?+0x29) [0x29] litest_backtrace() itself is copied from xserver/os/backtrace.c which git blame attributes to Marcin. CC: Marcin Slusarz <marcin.slusarz@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2015-05-04 09:13:22 +10:00
test: add a build-test for -pedantic We don't build with -pedantic, but a caller may try to actually stick to the c99 standard, so let's make sure our public header doesn't cause any issues there. Likewise, make sure that our header compiles with GNU C90. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 14:18:39 +10:00
# build-test only
test_build_pedantic_c99_SOURCES = build-pedantic.c
test: drop TEST_CFLAGS We're using the same flags for everything anyway, drop the custom flags Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-06 14:58:14 +10:00
test_build_pedantic_c99_CFLAGS = -std=c99 -pedantic -Werror
test: add a build-test for -pedantic We don't build with -pedantic, but a caller may try to actually stick to the c99 standard, so let's make sure our public header doesn't cause any issues there. Likewise, make sure that our header compiles with GNU C90. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 14:18:39 +10:00
test_build_std_gnuc90_SOURCES = build-pedantic.c
test: drop TEST_CFLAGS We're using the same flags for everything anyway, drop the custom flags Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-06-06 14:58:14 +10:00
test_build_std_gnuc90_CFLAGS = -std=gnu90 -Werror
test: add a build-test for -pedantic We don't build with -pedantic, but a caller may try to actually stick to the c99 standard, so let's make sure our public header doesn't cause any issues there. Likewise, make sure that our header compiles with GNU C90. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 14:18:39 +10:00
test: add test for minimal linker flags The most basic program using libinput should only need to link against -linput and get the rest resolved automatically. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-11 08:20:59 +10:00
# test for linking with the minimal linker flags
test_build_linker_SOURCES = build-pedantic.c
test_build_linker_CFLAGS = -I$(top_srcdir)/src
Split libinput-util into a noinst helper library Fixes distcheck (automake 1.14.1) make[2]: Entering directory '....../libinput-0.7.0/_build/test' Makefile:926: ../src/.deps/libinput-util.Plo: No such file or directory make[2]: *** No rule to make target '../src/.deps/libinput-util.Plo'. Stop. make[2]: Leaving directory '....../libinput/libinput-0.7.0/_build/test' Makefile:412: recipe for target 'distclean-recursive' failed That was the only place we used subdir objects, so we can drop it from configure now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-12-05 12:52:22 +10:00
test_build_linker_LDADD = $(top_builddir)/src/libinput.la $(top_builddir)/src/libinput-util.la
test: add test for minimal linker flags The most basic program using libinput should only need to link against -linput and get the rest resolved automatically. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-11 08:20:59 +10:00
test: Add include from C++ build test
2014-03-24 23:45:05 +01:00
# test including from C++
test_build_cxx_SOURCES = build-cxx.cc
test_build_cxx_CXXFLAGS = -Wall -Wextra -Wno-unused-parameter $(AM_CXXFLAGS)
test: automatically run the tests against valgrind for leaks Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-03-27 11:04:24 +10:00
if HAVE_VALGRIND
VALGRIND_FLAGS=--leak-check=full \
--quiet \
--error-exitcode=3 \
--suppressions=$(srcdir)/valgrind.suppressions
test: make the valgrind test an actual dependency of the test run With parallel builds the valgrind test run would run at the same time as the normal run, the test suite isn't designed for that. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-07-22 15:27:49 +10:00
valgrind: check-am
test: write the valgrind test results to a different output file Otherwise we overwriting the output from the normal test run. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-07-06 08:28:09 +10:00
$(MAKE) check-TESTS TEST_SUITE_LOG="test-suite-valgrind.log" LOG_COMPILER="$(VALGRIND)" LOG_FLAGS="$(VALGRIND_FLAGS)" CK_FORK=no USING_VALGRIND=yes
test: automatically run the tests against valgrind for leaks Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-03-27 11:04:24 +10:00
check: valgrind
test: add the valgrind test suite output to the distcleanfiles Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2016-08-30 17:50:49 +10:00
DISTCLEANFILES=test-suite-valgrind.log
test: automatically run the tests against valgrind for leaks Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-03-27 11:04:24 +10:00
endif
Add the framework for a test suite Just the scaffolding, no actual tests just yet Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2013-12-06 14:17:35 +10:00
endif
test: automatically run the tests against valgrind for leaks Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Jonas Ådahl <jadahl@gmail.com>
2014-03-27 11:04:24 +10:00
EXTRA_DIST=valgrind.suppressions
Hook up gcov for coverage reports ./configure --enable-gcov adds the required flags to link everything ready for gcov. A new make gcov target runs the test suite, then pulls all the gcov bits together into ./test/gcov-reports/ including a summary file. The script to pull everything out is used in libevdev too, we just have an extra condition here to ignore the selftest gcov bits (it overwrites the useful litest.c coverage output). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2017-01-05 15:21:24 +10:00
if GCOV_ENABLED
CLEANFILES = gcov-reports/*.gcov gcov-reports/summary.txt *.gcno *.gcda
gcov: generate-gcov-report.sh check-TESTS
$(AM_V_GEN)$(srcdir)/generate-gcov-report.sh gcov-reports $(top_builddir)/src $(builddir)
else
gcov:
@echo "Run ./configure --enable-gcov to produce gcov reports" && false
endif
Reference in a new issue Copy permalink