<div dir="ltr">Another neat option would be to include blah_blah.c files (with static function definitions u want to test) into blah_blah-test.c files. I like this solution more than macro redefinitions as it's simpler and lets you call actually static functions which makes testing stricter (just a little bit :)<div>
<br></div><div>Have a good day!</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 5, 2013 at 6:38 PM, Marek Ch <span dir="ltr"><<a href="mailto:mchqwerty@gmail.com" target="_blank">mchqwerty@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I did similar thing like is in Weston for testing static functions. Also, I wrote<br>
few wl_buffer unit tests.<br>
I appreaciate any comments :)<br>
<br>
P. S.: based on mailing here:<br>
<a href="http://lists.freedesktop.org/archives/wayland-devel/2013-November/012299.html" target="_blank">http://lists.freedesktop.org/archives/wayland-devel/2013-November/012299.html</a><br>
<br>
<br>
Thanks,<br>
Marek Ch<br>
<br>
<br>
Marek Ch (3):<br>
wayland-private: add define for testing static functions<br>
wayland-private: move struct wl_buffer into wayland-private.h<br>
tests: add tests for wl_buffer_*<br>
<br>
src/connection.c | 18 +---<br>
src/wayland-private.h | 24 +++++<br>
tests/Makefile.am | 12 ++-<br>
tests/buffer-test.c | 247 ++++++++++++++++++++++++++++++++++++++++++++++++++<br>
4 files changed, 286 insertions(+), 15 deletions(-)<br>
create mode 100644 tests/buffer-test.c<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
1.8.4.2<br>
<br>
_______________________________________________<br>
wayland-devel mailing list<br>
<a href="mailto:wayland-devel@lists.freedesktop.org">wayland-devel@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/wayland-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/wayland-devel</a><br>
</font></span></blockquote></div><br></div>