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