delta/libevdev.git/test, branch libevdev-0.9.1

test: remove NULL test for SW_MAX, 3.13 defines SW_MUTE_DEVICE

2014-01-29T05:08:12+00:00

Signed-off-by: Peter Hutterer

Warn about a SYN_DROPPED right after finishing a sync

2014-01-21T23:15:14+00:00

If the first event after a completed device sync is a SYN_DROPPED, warn the
user that they're not fast enough handling this device.

The test for this is rather complicated since we can't write SYN_DROPPED
through uinput so we have to juggle the device fd and a pipe and switch
between the two at the right time (taking into account that libevdev will read
events from the fd whenever it can).

Signed-off-by: Peter Hutterer

test: abort on unexpected log messages

2014-01-21T23:14:40+00:00

Add two log functions, one that aborts on a received message. We know when we
expect to receive an error, so anytime this happens unexpectedly should
terminate the test.

And for those tests do issue a log message, let them ignore it and don't
print anything.

Signed-off-by: Peter Hutterer

test: fix typo

2014-01-17T00:54:58+00:00

Signed-off-by: Peter Hutterer

test: rename a test to match what it's testing better

2014-01-17T00:54:58+00:00

Signed-off-by: Peter Hutterer

include: update linux/input.h for kernel 3.12

2014-01-08T23:05:05+00:00

Signed-off-by: Peter Hutterer 
Reviewed-by: David Herrmann

test: detect if we're running inside gdb and disable forking

2013-12-23T23:14:12+00:00

The Check test framework forks by default which is annoying when running gdb.
Try to detect whether we're inside gdb by ptracing ourselves. If that works,
we're not inside a debugger. If it doesn't, then assume we're inside a
debugger and set CK_FORK to "no".

Signed-off-by: Peter Hutterer

test: add basic link test

2013-12-12T03:19:52+00:00

This test doesn't do anything but compile and link against libevdev. It's a
simple protection to avoid linker errors. If we ever have libs we depend on
and they don't get resolved properly, this test should warn us in time.

Signed-off-by: Peter Hutterer

test: split tests into run-time and build-time tests

2013-12-12T02:57:21+00:00

The build-time tests don't do anything, we don't need to run them.

Signed-off-by: Peter Hutterer

Don't treat devices with (ABS_MT_SLOT - 1) as multitouch devices

2013-12-10T09:39:47+00:00

Some devices (PS3 sixaxis controller) merely have a bunch of axes, without the
semantic information that linux/input.h requires. For those, the ABS_MT range
may be merely another axis, not the special range that we need to treat it
with.

Use a simple heuristic: if ABS_MT_SLOT - 1 is enabled, don't treat ABS_MT as
multitouch axes. The ABS_MT_SLOT - 1 axis is not used for a real axis.

Signed-off-by: Peter Hutterer 
Reviewed-by: David Herrmann