brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
57ce4e04e5
mutter/src/tests/wayland-test-clients/test-driver.xml

34 lines
1.0 KiB
XML
Raw Normal View History

tests/wayland: Test subsurface commits after parent was reset Without 'wayland/surface-actor: Reset and sync subsurface state when resetting' this test would fail. This also adds a simple framework for testing lower level Wayland semantics. In contrast to the test-client and test-driver framework, which uses gtk and tests mostly window management related things, this framework is aimed to run Wayland clients made to test a particular protocol flow, thus will likely consist of manual lower level Wayland mechanics. A private protocol is added in order to help out clients do things they cannot do by themself. The protocol currently only consists of a request meant to be used for getting a callback when the actor of a given surface is eventually destroyed. This is different from the wl_surface being destroyed due to window destroy animations taking an arbitrary amount of time. It'll be used by the first test added in the next commit. https://gitlab.gnome.org/GNOME/mutter/merge_requests/961
2019-12-06 18:05:32 +00:00
<?xml version="1.0" encoding="UTF-8"?>
<protocol name="test_driver">
<interface name="test_driver" version="1">
<request name="sync_actor_destroyed">
<arg name="callback" type="new_id" interface="wl_callback"/>
<arg name="surface" type="object" interface="wl_surface"/>
</request>
tests/wayland-test-driver: Add generic "sync point" request This can be used by test cases to make sure the compositor tries something after a known client state. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1716 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1795>
2021-06-18 22:15:05 +00:00
tests/wayland: Add more requests to test driver protocol Add `sync_effects_completed()` and `verify_view()` in order to allow Wayland test clients to trigger verifications and add convenience functions to use them to client-utils. Notes: - `sync_effects_completed()` works in two stages in order to ensure it doesn't race with window effects. By the time `sync_effects_completed()` is processed, an effect could already have ended or not yet been scheduled. Thus we defer a check for pending effects to the next paint cycle, assuming that by then they should have been scheduled. - `meta_ref_test_verify_view()` internally triggers the `paint` signal for the stage which is why it can not be run in the after-paint signal handler. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1055>
2022-05-21 16:17:31 +00:00
<request name="sync_effects_completed">
<arg name="callback" type="new_id" interface="wl_callback"/>
<arg name="surface" type="object" interface="wl_surface"/>
</request>
tests/wayland-test-driver: Add generic "sync point" request This can be used by test cases to make sure the compositor tries something after a known client state. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1716 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1795>
2021-06-18 22:15:05 +00:00
<request name="sync_point">
<arg name="sequence" type="uint"/>
tests/wayland-test-driver: Add surface argument to sync_point request Will allow more "specific" sync points; will be used in the future by new tests. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1993>
2021-09-07 08:31:26 +00:00
<arg name="surface" type="object" interface="wl_surface" allow-null="true"/>
tests/wayland-test-driver: Add generic "sync point" request This can be used by test cases to make sure the compositor tries something after a known client state. Fixes: https://gitlab.gnome.org/GNOME/mutter/-/issues/1716 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1795>
2021-06-18 22:15:05 +00:00
</request>
tests/wayland-test-driver: Add sync event Will be used to signal test cases. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1993>
2021-09-07 08:32:53 +00:00
tests/wayland: Add more requests to test driver protocol Add `sync_effects_completed()` and `verify_view()` in order to allow Wayland test clients to trigger verifications and add convenience functions to use them to client-utils. Notes: - `sync_effects_completed()` works in two stages in order to ensure it doesn't race with window effects. By the time `sync_effects_completed()` is processed, an effect could already have ended or not yet been scheduled. Thus we defer a check for pending effects to the next paint cycle, assuming that by then they should have been scheduled. - `meta_ref_test_verify_view()` internally triggers the `paint` signal for the stage which is why it can not be run in the after-paint signal handler. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1055>
2022-05-21 16:17:31 +00:00
<request name="verify_view">
<arg name="callback" type="new_id" interface="wl_callback"/>
<arg name="sequence" type="uint"/>
</request>
tests/wayland-test-driver: Add sync event Will be used to signal test cases. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1993>
2021-09-07 08:32:53 +00:00
<event name="sync_event">
<arg name="sequence" type="uint"/>
</event>
tests/test-driver: Add way to send generic properties to client This will make it rather convenient to send arbitrary strings, e.g. file paths, to the client test case. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2417>
2022-05-13 19:56:50 +00:00
<event name="property">
<arg name="name" type="string"/>
<arg name="value" type="string"/>
</event>
tests/wayland: Test subsurface commits after parent was reset Without 'wayland/surface-actor: Reset and sync subsurface state when resetting' this test would fail. This also adds a simple framework for testing lower level Wayland semantics. In contrast to the test-client and test-driver framework, which uses gtk and tests mostly window management related things, this framework is aimed to run Wayland clients made to test a particular protocol flow, thus will likely consist of manual lower level Wayland mechanics. A private protocol is added in order to help out clients do things they cannot do by themself. The protocol currently only consists of a request meant to be used for getting a callback when the actor of a given surface is eventually destroyed. This is different from the wl_surface being destroyed due to window destroy animations taking an arbitrary amount of time. It'll be used by the first test added in the next commit. https://gitlab.gnome.org/GNOME/mutter/merge_requests/961
2019-12-06 18:05:32 +00:00
</interface>
</protocol>
Reference in New Issue Copy Permalink