Files
xserver/test
Michel Dänzer 8db5a711da test: Use .../piglit instead of .../piglit-*.py
The latter use Python 2 and break with any non-ASCII characters in the
environment, the former uses Python 3 and works fine in that case.

Reviewed-by: Eric Anholt <eric@anholt.net>
(Cherry picked from commit 4aaaf69229)
2019-02-22 11:53:37 +01:00
..
2017-10-04 11:19:09 -04:00
2019-02-20 14:23:50 -05:00
2017-01-12 15:01:36 -05:00
2017-10-30 13:45:20 -04:00
2017-01-12 15:01:36 -05:00
2018-02-14 17:04:48 -05:00
2017-04-25 15:01:23 -07:00
2017-01-12 15:01:36 -05:00
2017-02-23 13:16:07 -05:00
2017-01-12 15:01:36 -05:00
2017-01-12 15:01:36 -05:00
2019-02-20 14:23:50 -05:00

                        X server test suite

This suite contains a set of tests to verify the behaviour of functions used
internally to the server.

= 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" in 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.