mainnika
/
weston
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4657 Commits
1 Branch
0 Tags
13 MiB
Tag: Branch: Tree: 708d326b30
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '708d326b30'
${ noResults }
weston/protocol/weston-test.xml

129 lines
4.9 KiB
Raw Normal View History Unescape

tests: Define and implement a test protocol extension. The weston test extension, called weston-test.so, can be loaded from the "modules" configuration option on the command line or in the .ini file. Clients can bind to the "wl_test" interface to interact with the weston test extension. Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
12 years ago
<?xml version="1.0" encoding="UTF-8"?>
tests: Rename wayland-test to weston-test wayland-test isn't and will never be wayland protocol, it's weston internal. Renamed wayland-test to weston-test, and wl_test to weston_test. Also added a Big Fat Warning to the description of weston_test to try to keep people from thinking it's a good idea to use some of these functions outside of testing. Signed-off-by: Derek Foreman <derekf@osg.samsung.com> Acked-by: Bryce Harrington <bryce@osg.samsung.com> Reviewed-by: Bryce Harrington <bryce@osg.samsung.com>
10 years ago
<protocol name="weston_test">
tests: Define and implement a test protocol extension. The weston test extension, called weston-test.so, can be loaded from the "modules" configuration option on the command line or in the .ini file. Clients can bind to the "wl_test" interface to interact with the weston test extension. Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
12 years ago
<copyright>
Copyright © 2012 Intel Corporation
Permission to use, copy, modify, distribute, and sell this
software and its documentation for any purpose is hereby granted
without fee, provided that the above copyright notice appear in
all copies and that both that copyright notice and this permission
notice appear in supporting documentation, and that the name of
the copyright holders not be used in advertising or publicity
pertaining to distribution of the software without specific,
written prior permission. The copyright holders make no
representations about the suitability of this software for any
purpose. It is provided "as is" without express or implied
warranty.
THE COPYRIGHT HOLDERS DISCLAIM ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS, IN NO EVENT SHALL THE COPYRIGHT HOLDERS BE LIABLE FOR ANY
SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
THIS SOFTWARE.
</copyright>
tests: Rename wayland-test to weston-test wayland-test isn't and will never be wayland protocol, it's weston internal. Renamed wayland-test to weston-test, and wl_test to weston_test. Also added a Big Fat Warning to the description of weston_test to try to keep people from thinking it's a good idea to use some of these functions outside of testing. Signed-off-by: Derek Foreman <derekf@osg.samsung.com> Acked-by: Bryce Harrington <bryce@osg.samsung.com> Reviewed-by: Bryce Harrington <bryce@osg.samsung.com>
10 years ago
<interface name="weston_test" version="1">
<description summary="weston internal testing">
Internal testing facilities for the weston compositor.
It can't be stressed enough that these should never ever be used
outside of running weston's tests. The weston-test.so module should
never be installed.
These requests may allow clients to do very bad things.
</description>
tests: Define and implement a test protocol extension. The weston test extension, called weston-test.so, can be loaded from the "modules" configuration option on the command line or in the .ini file. Clients can bind to the "wl_test" interface to interact with the weston test extension. Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
12 years ago
<request name="move_surface">
<arg name="surface" type="object" interface="wl_surface"/>
<arg name="x" type="int"/>
<arg name="y" type="int"/>
</request>
<request name="move_pointer">
<arg name="x" type="int"/>
<arg name="y" type="int"/>
</request>
<request name="send_button">
<arg name="button" type="int"/>
<arg name="state" type="uint"/>
</request>
<request name="activate_surface">
<arg name="surface" type="object" interface="wl_surface" allow-null="true"/>
</request>
<request name="send_key">
<arg name="key" type="uint"/>
<arg name="state" type="uint"/>
</request>
weston-test: add device_{release/add} into protocol This request simulates device creation/destruction from evdev (libinput) v2: added support for touch. Touch is not supported yet, but better be prepared Signed-off-by: Marek Chalupa <mchqwerty@gmail.com> Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
10 years ago
<request name="device_release">
<arg name="device" type="string"/>
</request>
<request name="device_add">
<arg name="device" type="string"/>
</request>
tests: Define and implement a test protocol extension. The weston test extension, called weston-test.so, can be loaded from the "modules" configuration option on the command line or in the .ini file. Clients can bind to the "wl_test" interface to interact with the weston test extension. Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
12 years ago
<event name="pointer_position">
<arg name="x" type="fixed"/>
<arg name="y" type="fixed"/>
</event>
tests: Test whether a simple EGL main loop uses too many buffers This adds a test that tries to simulate a simple game loop that would be like this: while (1) { draw_something(); eglSwapBuffers(); } In this case the test is relying on eglSwapBuffers to throttle to a sensible frame rate. The test then verifies that only 2 EGL buffers are used. This is done via a new request and event in the wayland-test protocol. Currently this causes 3 buffers to be created because the release event generated by the swap buffers is not processed by Mesa until it blocks for the frame complete event in the next swap buffers call, but that is too late. This can be fixed in Mesa by issuing a sync request after the swap buffers and blocking on it before deciding whether to allocate a new buffer.
11 years ago
<request name="get_n_egl_buffers">
<!-- causes a n_egl_buffers event to be sent which reports how many
buffer objects are live for the client -->
</request>
<event name="n_egl_buffers">
<arg name="n" type="uint"/>
</event>
protocol: Add test screenshot capability This adds a capture_screenshot request which returns an image of the screen in the client-supplied wl_buffer for the given display output. A 'done' event is used to indicate when screenshotting has finished and the wl_buffer is ready to be read. Signed-off-by: Bryce Harrington <bryce@osg.samsung.com> Reviewed-By: Derek Foreman <derekf@osg.samsung.com>
10 years ago
<request name="capture_screenshot">
<description summary="records current screen image">
Records an image of what is currently displayed on a given
display output, returning the image as an event.
</description>
<arg name="output" type="object" interface="wl_output"
summary="output to capture from"/>
<arg name="buffer" type="object" interface="wl_buffer"
summary="buffer for returning screenshots to the test client"/>
</request>
<event name="capture_screenshot_done">
<description summary="screenshot capture is done">
The capture_screenshot_done signal is sent when a screenshot has been copied into the
provided buffer.
</description>
</event>
tests: Define and implement a test protocol extension. The weston test extension, called weston-test.so, can be loaded from the "modules" configuration option on the command line or in the .ini file. Clients can bind to the "wl_test" interface to interact with the weston test extension. Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
12 years ago
</interface>
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
<interface name="weston_test_runner" version="1">
<description summary="weston internal testing">
This is a global singleton interface for Weston internal tests.
This interface allows a test client to trigger compositor-side
test procedures. This is useful for cases, where the actual tests
are in compositor plugins, but they also require the presence of
a particular client.
This interface is implemented by the compositor plugins containing
the testing code.
A test client starts a test with the "run" request. It must not send
another "run" request until receiving the "finished" event. If the
compositor-side test succeeds, the "finished" event is sent. If the
compositor-side test fails, the compositor should send the protocol
error "test_failed", but it may also exit with an error (e.g. SEGV).
Unknown test name will raise "unknown_test" protocol error.
</description>
<enum name="error">
<entry name="test_failed" value="0" summary="compositor test failed"/>
<entry name="unknown_test" value="1" summary="unrecognized test name"/>
</enum>
<request name="destroy" type="destructor"/>
<request name="run">
<arg name="test_name" type="string"/>
</request>
<event name="finished"/>
</interface>
tests: Define and implement a test protocol extension. The weston test extension, called weston-test.so, can be loaded from the "modules" configuration option on the command line or in the .ini file. Clients can bind to the "wl_test" interface to interact with the weston test extension. Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
12 years ago
</protocol>