xserver-multidpi/test
Peter Hutterer 42dc91e32a include: let BitIsOn() return a boolean value.
Simply returning the mask bit breaks checks like
    BitIsOn(mask, 0) != BitIsOn(mask, 1);
as used in 048e93593e.

The naming of this macro suggests that it should return boolean values
anyway. This patch also adds a few simple tests for these macros to make
sure they don't accidentally break in the future.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Pat Kane <pekane52@gmail.com>
Reviewed-by: Julien Cristau <jcristau@debian.org>
Reviewed-by: Keith Packard <keithp@keithp.com>
2010-11-26 09:59:24 +10:00
..
xi2 test: Fix missing xkbsrv.h include. 2010-11-12 11:49:21 +10:00
.gitignore Ignore build products in the server's test suite. 2010-05-26 11:17:53 -07:00
input.c include: let BitIsOn() return a boolean value. 2010-11-26 09:59:24 +10:00
Makefile.am test: Fix make distcheck when not building unit tests 2010-10-13 19:27:18 -07:00
README Add a test-suite for in-server unit-testing. 2009-04-28 16:03:56 +10:00
xkb.c Add a test-suite for in-server unit-testing. 2009-04-28 16:03:56 +10:00
xtest.c If XTest is always required, then eliminate the XTest devPrivate 2010-06-07 19:56:47 -07: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