| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
The test suite for JSON-GLib was written back when we only had
gtester-report and freeform verbose test output. These days, we expect
everything to conform to the Test Anything Protocol (TAP), which has
specific constraints on the output format.
|
|
|
|
|
|
|
|
| |
This will give more informative message in case of fail assertions.
Moreover GLib (when compiling with G_DISABLE_ASSERT) disable g_assert
totally, that would make these tests no-op
Signed-off-by: Frederic Martinsons <frederic.martinsons@sigfox.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 028e540 disallowed empty member names in objects, however
they are unfortunately valid JSON. This patch reenables an empty
string as a member name.
Tests are updated to allow the empty string case, and to test
the use of an empty string in generation, iteration etc.
https://bugzilla.gnome.org/show_bug.cgi?id=747279
|
|
|
|
|
|
| |
GLib 2.46.0 forbids this and so the testsuite fails.
https://bugzilla.gnome.org/show_bug.cgi?id=755977
|
|
|
|
|
| |
We depend on a new version of GLib, so we can remove a bunch of old
version checks.
|
|
|
|
|
|
|
|
| |
Starting from GLib 2.36, g_type_init() is going to be deprecated (the
type system will be initialized as soon as libgobject is paged in, using
constructors). As I don't want to bump dependencies just for that, the
call to g_type_init() should be placed under a compile-time version
check, to keep the noise from compiler warnings down.
|
| |
|
|
It's pointless to add the '-test' suffix to files under the tests/ directory.
|