weston_test

version 1
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.

move_surface(surface: object<wl_surface>, x: int, y: int)
Argument
Type
Description
surfaceobject<wl_surface>
xint
yint
move_pointer(tv_sec_hi: uint, tv_sec_lo: uint, tv_nsec: uint, x: int, y: int)
Argument
Type
Description
tv_sec_hiuint
tv_sec_louint
tv_nsecuint
xint
yint
send_button(tv_sec_hi: uint, tv_sec_lo: uint, tv_nsec: uint, button: int, state: uint)
Argument
Type
Description
tv_sec_hiuint
tv_sec_louint
tv_nsecuint
buttonint
stateuint
send_axis(tv_sec_hi: uint, tv_sec_lo: uint, tv_nsec: uint, axis: uint, value: fixed)
Argument
Type
Description
tv_sec_hiuint
tv_sec_louint
tv_nsecuint
axisuint
valuefixed
activate_surface(surface: object<wl_surface>)
Argument
Type
Description
surfaceobject<wl_surface>allow null
send_key(tv_sec_hi: uint, tv_sec_lo: uint, tv_nsec: uint, key: uint, state: uint)
Argument
Type
Description
tv_sec_hiuint
tv_sec_louint
tv_nsecuint
keyuint
stateuint
device_release(device: string)
Argument
Type
Description
devicestring
device_add(device: string)
Argument
Type
Description
devicestring
send_touch(tv_sec_hi: uint, tv_sec_lo: uint, tv_nsec: uint, touch_id: int, x: fixed, y: fixed, touch_type: uint)
Argument
Type
Description
tv_sec_hiuint
tv_sec_louint
tv_nsecuint
touch_idint
xfixed
yfixed
touch_typeuint
pointer_position(x: fixed, y: fixed)
Argument
Type
Description
xfixed
yfixed
Argument
Value
Description
touch_up_with_coordinate0
invalid coordinate

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.

destroy()
run(test_name: string)
Argument
Type
Description
test_namestring
Argument
Value
Description
test_failed0
compositor test failed
unknown_test1
unrecognized test name

Compositor Support

No compositor support found

Copyright © 2012 Intel Corporation

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice (including the next paragraph) shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.