Unit testing a wayland client

[Wagner, Michael]

Hi,

I am currently looking into possibilities for unit testing our
client whether it calls wayland functions in the correct
form (order, content, etc.)

So I wanted to use fake wl_* functions for mocking
purposes. This seems to be not possible as all the
wayland-scanner generated protocol functions carry
the function definition already in the header file.
This leads to compiler errors (multiple definition).

My question would be, what is the reasoning behind
putting all definitions already in the header?

Maybe I'm completely looking into the wrong direction,
and you have any suggestions on how to unit test a
client application, any hints would be appreciated.


Thank you,

Michael

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20160401/9776eba9/attachment.html>