mutter/src/tests/wayland-test-clients/test-driver.xml

<?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>
  </interface>
</protocol>
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 19:05:32 +01: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>`
			`</interface>`
			`</protocol>`