Re: gtester git repo (Re: GLib testing framework)

Your API has g_test_rand_bit() which should (IMO) be called g_test_rand_boolean() to match the fundamental type's name that's used for this in glib (gboolean) and also to provide consistency with g_rand_boolean(). I think a difference to the rest of the g_* API isn't really helpful in using the new test framework (imagine someone porting self-written tests to the framework and the g_rand_boolean() has to be replaced with g_test_rand_bit() - feels a little odd).


Am 08.11.2007 um 15:59 schrieb Tim Janik:

On Tue, 6 Nov 2007, Tim Janik wrote:

i've checked in Sven's and my code into a git-svn mirror of glib on so you can browse the recent changes here:;a=shortlog;h=gtester

e.g. todays latest version of the testing examples is here:;a=blob;f=glib/tests/ testing.c;hb=9c8ae8c0097b8f7c098970e87bf413cd9c4f6a22

i've created a different repo for testing framework previews now,
as cloning the above includes dozens of megabytes for all of the
GLib history.

the new shallow repo is here:;a=summary

the branch i'm currently pushing to is: testing.git;a=shortlog;h=gtester1

i'll create gtester2, etc. everytime the branch is rebased onto
recent upstream changes.
the repo can be cloned with:
   git-clone git://

however building it might require this before
   mkdir -p build/win32/dirent build/win32/vs8 &&
touch build/win32/vs8/ build/win32/dirent/ build/win32/ build/

gtk-devel-list mailing list
gtk-devel-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]