weston

Pekka Paalanen f5b74f7ded tests: ivi_layout test infrastructure Testing the ivi_layout API requires two things: - the tests must be written as a controller module to access the API - the tests need a helper client to create some objects that can then be managed via the API This patch adds all the infrastructure and two different kinds of example tests. Internal ivi-shell (ivi_layout) API tests are listed as ivi-.la files in TESTS in Makefile.am. Weston-tests-env detects these, and runs Weston with ivi-shell, and loads the given module as a controller module, not as a normal plugin. The test controller module ivi-.la will launch a helper client. For ivi-layout-test.la the helper client is ivi-layout.ivi. The helper client uses the weston-test-runner framework to fork and exec each TEST with a fresh connection to the compositor. The actual test is triggered by the weston_test_runner protocol interface, a new addition to weston-test.xml. The helper client uses weston_test_runner to trigger a test, and the server side of the interface is implemented by the test controller module (ivi-layout-test.la). The server side of weston_test_runner uses the same trick as weston-test-runner.h to gather a list of defined tests. A test is defined with the RUNNER_TEST macro. If a test defined by RUNNER_TEST succeeds, an event is sent to the helper client that it can continue (or exit). If a test fails, a fatal protocol error is sent to the helper client. Once the helper client has iterated over all of its tests, it signals the batch success/failure via process exit code. That is cought in the test controller module, and forwarded as Weston's exit code. In summary: each ivi_layout test is a combination of a client side helper/setup and server side actual tests. v2: Load weston-test.so, because create_client() needs it. v3: add a comment about IVI_TEST_SURFACE_ID_BASE. v4: Rebased to upstream weston-tests-env changes. Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> Reviewed-by: Derek Foreman <derekf@osg.samsung.com> (v2)		10 years ago
clients	nested-client: fix typo	10 years ago
data	data: add reference image files for weston-ivi-shell-user-interface	10 years ago
desktop-shell	xwm: tell the shell the pid of the X clients	10 years ago
fullscreen-shell	compositor: Refactor weston_output_mode_switch()	10 years ago
ivi-shell	ivi-shell/weston.ini: fix paths	10 years ago
m4	weston-build: Fix aclocal error during autogen.sh	11 years ago
man	compositor: add option to specify a weston.ini	10 years ago
protocol	tests: ivi_layout test infrastructure	10 years ago
shared	toytoolkit: fix EGL surface creation for lazy drivers	10 years ago
src	gl-renderer: fix configless_context check	10 years ago
tests	tests: ivi_layout test infrastructure	10 years ago
wcap	wcap: Check for mmap and malloc return value in wcap decode module	11 years ago
xwayland	xwm: fix extra break	10 years ago
.gitignore	tests: ivi_layout test infrastructure	10 years ago
COPYING	Add COPYING	13 years ago
Makefile.am	tests: ivi_layout test infrastructure	10 years ago
README	README: Fix typo; add link to testing docs	11 years ago
autogen.sh	Update autotools configuration	14 years ago
configure.ac	configure.ac: make use of wayland-scanner.pc	10 years ago
notes.txt	Add informal notes file	12 years ago
releasing.txt	releasing: Note that Xwayland installation required only for Weston releases	10 years ago
weston.ini.in	libinput: Add tap configuration to weston.ini	11 years ago

README

Weston

Weston is the reference implementation of a Wayland compositor, and a
useful compositor in its own right.  Weston has various backends that
lets it run on Linux kernel modesetting and evdev input as well as
under X11.  Weston ships with a few example clients, from simple
clients that demonstrate certain aspects of the protocol to more
complete clients and a simplistic toolkit.  There is also a quite
capable terminal emulator (weston-terminal) and an toy/example desktop
shell.  Finally, weston also provides integration with the Xorg server
and can pull X clients into the Wayland desktop and act as a X window
manager.

Refer to http://wayland.freedesktop.org/building.html for building
weston and its dependencies.

The test suite can be invoked via `make check`; see
http://wayland.freedesktop.org/testing.html for additional details.