Stop using g_assert() in unit tests
Apart from having more developer-friendly messages if the assertions go
wrong, it also prevents the assertions not being run if
G_DISABLE_ASSERT
is defined (e.g. for performance reasons).
Apart from having more developer-friendly messages if the assertions go
wrong, it also prevents the assertions not being run if
G_DISABLE_ASSERT
is defined (e.g. for performance reasons).