xserver-multidpi/test
Peter Hutterer 8bebb4b489 Store desktop dimensions in screenInfo.
For Zaphod mode screen crossing handling we need to know the size of all
screens together (i.e. the whole desktop size). Store that in the screenInfo to
have it readily available in events.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
2011-10-13 11:26:09 +10:00
..
xi2 Input: Add smooth-scrolling support to GetPointerEvents 2011-09-30 09:24:18 +10:00
.gitignore Don't use empty source files 2011-06-23 05:28:31 -07:00
fixes.c fixes: Add support for pointer barriers 2011-05-31 15:10:51 -04:00
input.c Input: Add smooth-scrolling support to GetPointerEvents 2011-09-30 09:24:18 +10:00
list.c Add null-terminated list interface. 2011-08-22 15:56:53 +10:00
Makefile.am test: add a option duplication test 2011-08-22 15:56:48 +10:00
misc.c Store desktop dimensions in screenInfo. 2011-10-13 11:26:09 +10:00
README Add a test-suite for in-server unit-testing. 2009-04-28 16:03:56 +10:00
xfree86.c xfree86: switch options from pointer to XF86OptionPtr 2011-09-27 11:43:36 +10:00
xkb.c test: remove glib dependency 2011-04-21 13:43:43 +10:00
xtest.c test: remove glib dependency 2011-04-21 13:43:43 +10:00

                        X server test suite

This suite contains a set of tests to verify the behaviour of functions used
internally to the server. This test suite is based on glib's testing
framework [1].

= How it works =
Through some automake abuse, we link the test programs with the same static
libraries as the Xorg binary. The test suites can then call various functions
and verify their behaviour - without the need to start the server or connect
clients.

This testing only works for functions that do not rely on a particular state
of the X server. Unless the test suite replicates the expected state, which
may be difficult.

= How to run the tests =
Run "make check" the test directory. This will compile the tests and execute
them in the order specified in the TESTS variable in test/Makefile.am.

Each set of tests related to a subsystem are available as a binary that can be
executed directly. For example, run "xkb" to perform some xkb-related tests.

== Adding a new test ==
When adding a new test, ensure that you add a short description of what the
test does and what the expected outcome is. If the test reproduces a
particular bug, using g_test_bug().

== Misc ==

The programs "gtester" and "gtester-report" may be used to generate XML/HTML
log files of tests succeeded and failed.

---------

[1] http://library.gnome.org/devel/glib/stable/glib-Testing.html