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
|
|
|
/*
|
|
|
|
|
* Copyright © 2013 Red Hat, Inc.
|
|
|
|
|
*
|
|
|
|
|
* Permission to use, copy, modify, distribute, and sell this software and its
|
|
|
|
|
* documentation for any purpose is hereby granted without fee, provided that
|
|
|
|
|
* the above copyright notice appear in all copies and that both that copyright
|
|
|
|
|
* notice and this permission notice appear in supporting documentation, and
|
|
|
|
|
* that the name of the copyright holders not be used in advertising or
|
|
|
|
|
* publicity pertaining to distribution of the software without specific,
|
|
|
|
|
* written prior permission. The copyright holders make no representations
|
|
|
|
|
* about the suitability of this software for any purpose. It is provided "as
|
|
|
|
|
* is" without express or implied warranty.
|
|
|
|
|
*
|
|
|
|
|
* THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
|
|
|
|
|
* INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO
|
|
|
|
|
* EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY SPECIAL, INDIRECT OR
|
|
|
|
|
* CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
|
|
|
|
|
* DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
|
|
|
|
|
* TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE
|
|
|
|
|
* OF THIS SOFTWARE.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#if HAVE_CONFIG_H
|
|
|
|
|
#include "config.h"
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#ifndef LITEST_H
|
|
|
|
|
#define LITEST_H
|
|
|
|
|
|
|
|
|
|
#include <stdbool.h>
|
|
|
|
|
#include <check.h>
|
|
|
|
|
#include <libevdev/libevdev.h>
|
|
|
|
|
#include <libevdev/libevdev-uinput.h>
|
|
|
|
|
#include <libinput.h>
|
|
|
|
|
|
|
|
|
|
enum litest_device_type {
|
|
|
|
|
LITEST_NO_DEVICE = -1,
|
2014-08-04 12:49:59 +10:00
|
|
|
LITEST_SYNAPTICS_CLICKPAD = -2,
|
|
|
|
|
LITEST_SYNAPTICS_TOUCHPAD = -3,
|
|
|
|
|
LITEST_SYNAPTICS_TOPBUTTONPAD = -4,
|
|
|
|
|
LITEST_BCM5974 = -5,
|
|
|
|
|
LITEST_KEYBOARD = -6,
|
|
|
|
|
LITEST_TRACKPOINT = -7,
|
|
|
|
|
LITEST_MOUSE = -8,
|
|
|
|
|
LITEST_WACOM_TOUCH = -9,
|
|
|
|
|
LITEST_ALPS_SEMI_MT = -10,
|
|
|
|
|
LITEST_GENERIC_SINGLETOUCH = -11,
|
2014-11-05 11:20:36 +10:00
|
|
|
LITEST_MS_SURFACE_COVER = -12,
|
2014-10-29 10:59:58 +10:00
|
|
|
LITEST_QEMU_TABLET = -13,
|
2014-10-29 12:08:20 +10:00
|
|
|
LITEST_XEN_VIRTUAL_POINTER = -14,
|
2014-11-06 16:10:15 +10:00
|
|
|
LITEST_VMWARE_VIRTMOUSE = -15,
|
2014-12-11 13:30:33 +10:00
|
|
|
LITEST_SYNAPTICS_HOVER_SEMI_MT = -16,
|
2015-01-28 15:37:21 +10:00
|
|
|
LITEST_SYNAPTICS_TRACKPOINT_BUTTONS = -17,
|
2015-02-25 16:30:06 +10:00
|
|
|
LITEST_PROTOCOL_A_SCREEN = -18,
|
2015-03-04 10:27:22 +10:00
|
|
|
LITEST_WACOM_FINGER = -19,
|
2015-04-08 09:54:33 +10:00
|
|
|
LITEST_KEYBOARD_BLACKWIDOW = -20,
|
2015-04-13 10:23:47 +10:00
|
|
|
LITEST_WHEEL_ONLY = -21,
|
2015-04-17 15:59:36 +10:00
|
|
|
LITEST_MOUSE_ROCCAT = -22,
|
2015-04-28 16:45:35 +10:00
|
|
|
LITEST_LOGITECH_TRACKBALL = -23,
|
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
|
|
|
};
|
|
|
|
|
|
|
|
|
|
enum litest_device_feature {
|
|
|
|
|
LITEST_DISABLE_DEVICE = -1,
|
|
|
|
|
LITEST_ANY = 0,
|
|
|
|
|
LITEST_TOUCHPAD = 1 << 0,
|
|
|
|
|
LITEST_CLICKPAD = 1 << 1,
|
|
|
|
|
LITEST_BUTTON = 1 << 2,
|
|
|
|
|
LITEST_KEYS = 1 << 3,
|
2014-10-29 11:05:20 +10:00
|
|
|
LITEST_RELATIVE = 1 << 4,
|
2014-01-21 15:18:09 +10:00
|
|
|
LITEST_WHEEL = 1 << 5,
|
2014-01-22 09:58:43 +10:00
|
|
|
LITEST_TOUCH = 1 << 6,
|
2014-03-24 15:25:32 +10:00
|
|
|
LITEST_SINGLE_TOUCH = 1 << 7,
|
2014-06-05 16:25:37 +10:00
|
|
|
LITEST_APPLE_CLICKPAD = 1 << 8,
|
2014-06-11 08:59:11 +10:00
|
|
|
LITEST_TOPBUTTONPAD = 1 << 9,
|
2014-07-24 13:18:56 +10:00
|
|
|
LITEST_SEMI_MT = 1 << 10,
|
2014-09-18 11:15:27 +02:00
|
|
|
LITEST_POINTINGSTICK = 1 << 11,
|
2014-11-05 11:20:36 +10:00
|
|
|
LITEST_FAKE_MT = 1 << 12,
|
2014-10-29 10:59:58 +10:00
|
|
|
LITEST_ABSOLUTE = 1 << 13,
|
2015-02-25 16:30:06 +10:00
|
|
|
LITEST_PROTOCOL_A = 1 << 14,
|
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
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct litest_device {
|
|
|
|
|
struct libevdev *evdev;
|
|
|
|
|
struct libevdev_uinput *uinput;
|
|
|
|
|
struct libinput *libinput;
|
2014-02-22 15:06:34 +01:00
|
|
|
bool owns_context;
|
2014-01-29 15:38:48 +10:00
|
|
|
struct libinput_device *libinput_device;
|
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
|
|
|
struct litest_device_interface *interface;
|
2014-07-21 12:30:40 +10:00
|
|
|
|
|
|
|
|
int ntouches_down;
|
2014-09-17 10:07:38 +10:00
|
|
|
bool skip_ev_syn;
|
|
|
|
|
|
2014-07-24 13:18:56 +10:00
|
|
|
void *private; /* device-specific data */
|
2015-02-02 10:47:52 +10:00
|
|
|
|
|
|
|
|
char *udev_rule_file;
|
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
|
|
|
};
|
|
|
|
|
|
2014-02-22 15:06:34 +01:00
|
|
|
struct libinput *litest_create_context(void);
|
2015-03-13 09:32:37 +10:00
|
|
|
void litest_disable_log_handler(struct libinput *libinput);
|
|
|
|
|
void litest_restore_log_handler(struct libinput *libinput);
|
2014-02-22 15:06:34 +01:00
|
|
|
|
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
|
|
|
void litest_add(const char *name, void *func,
|
|
|
|
|
enum litest_device_feature required_feature,
|
|
|
|
|
enum litest_device_feature excluded_feature);
|
2014-07-14 00:01:10 +02:00
|
|
|
void
|
|
|
|
|
litest_add_for_device(const char *name,
|
|
|
|
|
void *func,
|
|
|
|
|
enum litest_device_type type);
|
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
|
|
|
void litest_add_no_device(const char *name, void *func);
|
|
|
|
|
|
|
|
|
|
int litest_run(int argc, char **argv);
|
|
|
|
|
struct litest_device * litest_create_device(enum litest_device_type which);
|
2014-08-29 14:08:46 +10:00
|
|
|
struct litest_device * litest_add_device(struct libinput *libinput,
|
|
|
|
|
enum litest_device_type which);
|
2014-03-31 10:00:16 +10:00
|
|
|
struct libevdev_uinput *
|
|
|
|
|
litest_create_uinput_device_from_description(const char *name,
|
|
|
|
|
const struct input_id *id,
|
|
|
|
|
const struct input_absinfo *abs,
|
|
|
|
|
const int *events);
|
test: allow partial overriding the test devices
For specific tests we need something that e.g. looks like a touchpad, but has
a different name, a different number of slots, etc. In this case, the
following code will do exactly that:
struct input_absinfo overrides[] = {
{ .value = ABS_MT_SLOT, .minimum = 0, .maximum = 100 },
{ .value = -1 },
};
litest_create_device_with_overrides(LITEST_SYNAPTICS_CLICKPAD,
NULL, NULL, &overrides, NULL);
For general event codes, overrides can only add to the set of events, they
can't remove.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-03-31 14:54:46 +10:00
|
|
|
struct litest_device *
|
|
|
|
|
litest_create_device_with_overrides(enum litest_device_type which,
|
|
|
|
|
const char *name_override,
|
|
|
|
|
struct input_id *id_override,
|
|
|
|
|
const struct input_absinfo *abs_override,
|
|
|
|
|
const int *events_override);
|
2014-02-22 15:06:34 +01:00
|
|
|
struct litest_device *
|
|
|
|
|
litest_add_device_with_overrides(struct libinput *libinput,
|
|
|
|
|
enum litest_device_type which,
|
|
|
|
|
const char *name_override,
|
|
|
|
|
struct input_id *id_override,
|
|
|
|
|
const struct input_absinfo *abs_override,
|
|
|
|
|
const int *events_override);
|
|
|
|
|
|
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
|
|
|
struct litest_device *litest_current_device(void);
|
|
|
|
|
void litest_delete_device(struct litest_device *d);
|
|
|
|
|
int litest_handle_events(struct litest_device *d);
|
|
|
|
|
|
|
|
|
|
void litest_event(struct litest_device *t,
|
|
|
|
|
unsigned int type,
|
|
|
|
|
unsigned int code,
|
|
|
|
|
int value);
|
2014-07-24 13:18:56 +10:00
|
|
|
int litest_auto_assign_value(struct litest_device *d,
|
|
|
|
|
const struct input_event *ev,
|
|
|
|
|
int slot, double x, double y);
|
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
|
|
|
void litest_touch_up(struct litest_device *d, unsigned int slot);
|
|
|
|
|
void litest_touch_move(struct litest_device *d,
|
|
|
|
|
unsigned int slot,
|
2014-07-18 16:01:10 +10:00
|
|
|
double x,
|
|
|
|
|
double y);
|
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
|
|
|
void litest_touch_down(struct litest_device *d,
|
|
|
|
|
unsigned int slot,
|
2014-07-18 16:01:10 +10:00
|
|
|
double x,
|
|
|
|
|
double y);
|
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
|
|
|
void litest_touch_move_to(struct litest_device *d,
|
|
|
|
|
unsigned int slot,
|
2014-07-18 16:01:10 +10:00
|
|
|
double x_from, double y_from,
|
|
|
|
|
double x_to, double y_to,
|
2014-09-25 13:20:47 +02:00
|
|
|
int steps, int sleep_ms);
|
2015-03-12 20:05:25 +01:00
|
|
|
void litest_touch_move_two_touches(struct litest_device *d,
|
|
|
|
|
double x0, double y0,
|
|
|
|
|
double x1, double y1,
|
|
|
|
|
double dx, double dy,
|
|
|
|
|
int steps, int sleep_ms);
|
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
|
|
|
void litest_button_click(struct litest_device *d,
|
|
|
|
|
unsigned int button,
|
|
|
|
|
bool is_press);
|
2014-11-06 16:32:53 +01:00
|
|
|
void litest_button_scroll(struct litest_device *d,
|
|
|
|
|
unsigned int button,
|
|
|
|
|
double dx, double dy);
|
2014-04-01 22:24:10 +02:00
|
|
|
void litest_keyboard_key(struct litest_device *d,
|
|
|
|
|
unsigned int key,
|
|
|
|
|
bool is_press);
|
2014-08-20 17:15:50 +10:00
|
|
|
void litest_wait_for_event(struct libinput *li);
|
|
|
|
|
void litest_wait_for_event_of_type(struct libinput *li, ...);
|
2014-01-22 11:20:50 +10:00
|
|
|
void litest_drain_events(struct libinput *li);
|
2014-06-06 10:58:11 +10:00
|
|
|
void litest_assert_empty_queue(struct libinput *li);
|
2015-04-16 10:42:16 +10:00
|
|
|
struct libinput_event_pointer * litest_is_button_event(
|
|
|
|
|
struct libinput_event *event,
|
|
|
|
|
int button,
|
|
|
|
|
enum libinput_button_state state);
|
2014-09-03 10:53:00 +10:00
|
|
|
void litest_assert_button_event(struct libinput *li,
|
|
|
|
|
unsigned int button,
|
|
|
|
|
enum libinput_button_state state);
|
2014-11-06 14:30:21 +10:00
|
|
|
void litest_assert_scroll(struct libinput *li,
|
|
|
|
|
enum libinput_pointer_axis axis,
|
2014-11-10 11:03:46 +10:00
|
|
|
int minimum_movement);
|
2014-12-18 11:29:32 +10:00
|
|
|
void litest_assert_only_typed_events(struct libinput *li,
|
|
|
|
|
enum libinput_event_type type);
|
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
|
|
|
|
test: add litest helper functions for creating uinput devices
Both functions accept a series of event types/codes tuples, terminated by -1.
For the even type INPUT_PROP_MAX (an invalid type otherwise) the code is used
as a property to enable.
The _abs function als takes an array of absinfo, with absinfo.value
determining the axis to change. If none are given, abs axes are initialized
with default settings.
Both functions abort on failure, so the caller does not need to check the
return value.
Example code for creating a rel device:
struct libevdev_uinput *uinput;
struct input_id id = { ... };
uinput = litest_create_uinput_device("foo", &id,
EV_REL, REL_X,
EV_REL, REL_Y,
EV_KEY, BTN_LEFT,
INPUT_PROP_MAX, INPUT_PROP_BUTTONPAD,
-1);
libevdev_uinput_write_event(uinput, EV_REL, REL_X, -1);
libevdev_uinput_write_event(uinput, EV_SYN, SYN_REPORT, 0);
...
libevdev_uinput_destroy(uinput);
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
2014-03-26 20:09:42 +10:00
|
|
|
struct libevdev_uinput * litest_create_uinput_device(const char *name,
|
|
|
|
|
struct input_id *id,
|
|
|
|
|
...);
|
|
|
|
|
struct libevdev_uinput * litest_create_uinput_abs_device(const char *name,
|
|
|
|
|
struct input_id *id,
|
|
|
|
|
const struct input_absinfo *abs,
|
|
|
|
|
...);
|
|
|
|
|
|
2014-09-16 16:08:29 +10:00
|
|
|
void litest_timeout_tap(void);
|
2015-05-04 08:42:44 +10:00
|
|
|
void litest_timeout_tapndrag(void);
|
2014-09-16 16:08:29 +10:00
|
|
|
void litest_timeout_softbuttons(void);
|
2014-11-06 16:32:53 +01:00
|
|
|
void litest_timeout_buttonscroll(void);
|
2015-03-06 14:36:31 +10:00
|
|
|
void litest_timeout_edgescroll(void);
|
2015-02-16 13:30:24 +01:00
|
|
|
void litest_timeout_finger_switch(void);
|
2015-04-13 16:38:44 +10:00
|
|
|
void litest_timeout_middlebutton(void);
|
2014-09-16 16:08:29 +10:00
|
|
|
|
2014-09-17 10:07:38 +10:00
|
|
|
void litest_push_event_frame(struct litest_device *dev);
|
|
|
|
|
void litest_pop_event_frame(struct litest_device *dev);
|
|
|
|
|
|
2014-12-16 11:28:26 +10:00
|
|
|
/* this is a semi-mt device, so we keep track of the touches that the tests
|
|
|
|
|
* send and modify them so that the first touch is always slot 0 and sends
|
|
|
|
|
* the top-left of the bounding box, the second is always slot 1 and sends
|
|
|
|
|
* the bottom-right of the bounding box.
|
|
|
|
|
* Lifting any of two fingers terminates slot 1
|
|
|
|
|
*/
|
|
|
|
|
struct litest_semi_mt {
|
|
|
|
|
int tracking_id;
|
|
|
|
|
/* The actual touches requested by the test for the two slots
|
|
|
|
|
* in the 0..100 range used by litest */
|
|
|
|
|
struct {
|
|
|
|
|
double x, y;
|
|
|
|
|
} touches[2];
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
void litest_semi_mt_touch_down(struct litest_device *d,
|
|
|
|
|
struct litest_semi_mt *semi_mt,
|
|
|
|
|
unsigned int slot,
|
|
|
|
|
double x, double y);
|
|
|
|
|
void litest_semi_mt_touch_move(struct litest_device *d,
|
|
|
|
|
struct litest_semi_mt *semi_mt,
|
|
|
|
|
unsigned int slot,
|
|
|
|
|
double x, double y);
|
|
|
|
|
void litest_semi_mt_touch_up(struct litest_device *d,
|
|
|
|
|
struct litest_semi_mt *semi_mt,
|
|
|
|
|
unsigned int slot);
|
|
|
|
|
|
2014-02-22 15:06:34 +01:00
|
|
|
#ifndef ck_assert_notnull
|
|
|
|
|
#define ck_assert_notnull(ptr) ck_assert_ptr_ne(ptr, NULL)
|
|
|
|
|
#endif
|
|
|
|
|
|
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
|
|
|
#endif /* LITEST_H */
|