xserver/test
Enrico Weigelt, metux IT consult 5e6c583ab1 (!1688) os: directly set console verbosity level, instead of using LogSetParameter()
No need for extra call to some demuxer function for nothing but setting a
simple int variable. Setting verbosity level really is nothing more than just
writing some value into a variable, so it's trivial to just to do that, instead
of having an unncessarily complex "universal setter" for that.

Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
2025-06-03 17:34:08 +02:00
..
bigreq
bugs
damage
scripts
sync
xi1
xi2
.gitignore
README
fixes.c
hashtabletest.c
input.c
list.c
meson.build
misc.c
signal-logging.c (!1688) os: directly set console verbosity level, instead of using LogSetParameter() 2025-06-03 17:34:08 +02:00
simple-xinit.c
string.c
test_xkb.c
tests-common.c
tests-common.h
tests.c
tests.h
touch.c
xfree86.c
xtest.c

                        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.