FGCOM/jansson
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
cfd817895a
jansson/test/suites/api/util.h

91 lines
4.0 KiB
C
Raw Normal View History

Add some missing copyright notices
2009-08-25 22:50:41 +08:00
/*
Update copyrights for 2014
2014-01-28 15:16:05 +08:00
* Copyright (c) 2009-2014 Petri Lehtinen <petri@digip.org>
Add some missing copyright notices
2009-08-25 22:50:41 +08:00
*
* Jansson is free software; you can redistribute it and/or modify
* it under the terms of the MIT license. See LICENSE for details.
*/
Add lots of tests for pack/unpack code, fix bugs found Closes GH-12.
2011-02-23 01:08:41 +08:00
#ifndef UTIL_H
#define UTIL_H
Expand value test coverage
2009-08-19 02:33:45 +08:00
Make real number encoding and decoding work under all locales The decimal point '.' is changed to locale's decimal point before/after JSON conversion to make C standard library's locale-specific string conversion functions work correctly. All the tests now call setlocale(LC_ALL, "") on startup to use the locale set in the environment. Fixes GH-32.
2011-10-03 02:27:53 +08:00
#ifdef HAVE_CONFIG_H
Renamed config.h -> jansson_private_config.h This is because it's really easy to get a name collission if compiling Jansson as a subproject in a larger CMake project. If one project includes several subprojects each having their own config.h, this will cause the wrong file to be loaded.
2014-01-14 00:13:44 +08:00
#include <jansson_private_config.h>
Make real number encoding and decoding work under all locales The decimal point '.' is changed to locale's decimal point before/after JSON conversion to make C standard library's locale-specific string conversion functions work correctly. All the tests now call setlocale(LC_ALL, "") on startup to use the locale set in the environment. Fixes GH-32.
2011-10-03 02:27:53 +08:00
#endif
Add lots of tests for pack/unpack code, fix bugs found Closes GH-12.
2011-02-23 01:08:41 +08:00
#include <stdio.h>
Extend array API Added functions: json_array_insert json_array_insert_new json_array_remove json_array_clear json_array_extend
2009-09-30 02:19:55 +08:00
#include <stdlib.h>
Make real number encoding and decoding work under all locales The decimal point '.' is changed to locale's decimal point before/after JSON conversion to make C standard library's locale-specific string conversion functions work correctly. All the tests now call setlocale(LC_ALL, "") on startup to use the locale set in the environment. Fixes GH-32.
2011-10-03 02:27:53 +08:00
#if HAVE_LOCALE_H
#include <locale.h>
#endif
Add lots of tests for pack/unpack code, fix bugs found Closes GH-12.
2011-02-23 01:08:41 +08:00
#include <jansson.h>
Don't use the nonstandard __FUNCTION__ macro
2014-10-03 13:38:57 +08:00
#define failhdr fprintf(stderr, "%s:%d: ", __FILE__, __LINE__)
Extend array API Added functions: json_array_insert json_array_insert_new json_array_remove json_array_clear json_array_extend
2009-09-30 02:19:55 +08:00
Expand value test coverage
2009-08-19 02:33:45 +08:00
#define fail(msg) \
do { \
Add lots of tests for pack/unpack code, fix bugs found Closes GH-12.
2011-02-23 01:08:41 +08:00
failhdr; \
fprintf(stderr, "%s\n", msg); \
Extend array API Added functions: json_array_insert json_array_insert_new json_array_remove json_array_clear json_array_extend
2009-09-30 02:19:55 +08:00
exit(1); \
Expand value test coverage
2009-08-19 02:33:45 +08:00
} while(0)
Add lots of tests for pack/unpack code, fix bugs found Closes GH-12.
2011-02-23 01:08:41 +08:00
/* Assumes json_error_t error */
pack_unpack: List unrecognized keys in strict unpacking Otherwise figuring out what's wrong with your JSON can be tricky, especially if you're using a single fmt string to validate a large, complicated schema. The comma delimiting will make separating keys that contain commas difficult. For example: {"foo, bar": true, "baz": false} will generate errors like: 2 object item(s) left unpacked: foo, bar, baz but that seems like a small enough corner case to not be worth much worrying. I wanted to find a way to handle this without have_unrecognized_keys, but the strbuffer tooling makes it look like I shouldn't be reaching in to do things like: strbuffer_t unrecognized_keys; unrecognized_keys.value = NULL; and then using 'unrecognized_keys.value == NULL' in place of have_unrecognized_keys.
2015-12-18 08:56:22 +08:00
#define check_errors(texts_, num_, source_, line_, column_, position_) \
Add lots of tests for pack/unpack code, fix bugs found Closes GH-12.
2011-02-23 01:08:41 +08:00
do { \
pack_unpack: List unrecognized keys in strict unpacking Otherwise figuring out what's wrong with your JSON can be tricky, especially if you're using a single fmt string to validate a large, complicated schema. The comma delimiting will make separating keys that contain commas difficult. For example: {"foo, bar": true, "baz": false} will generate errors like: 2 object item(s) left unpacked: foo, bar, baz but that seems like a small enough corner case to not be worth much worrying. I wanted to find a way to handle this without have_unrecognized_keys, but the strbuffer tooling makes it look like I shouldn't be reaching in to do things like: strbuffer_t unrecognized_keys; unrecognized_keys.value = NULL; and then using 'unrecognized_keys.value == NULL' in place of have_unrecognized_keys.
2015-12-18 08:56:22 +08:00
int i_, found_ = 0; \
for(i_ = 0; i_ < num_; i_++) { \
if(strcmp(error.text, texts_[i_]) == 0) { \
found_ = 1; \
break; \
} \
} \
if (!found_) { \
Add lots of tests for pack/unpack code, fix bugs found Closes GH-12.
2011-02-23 01:08:41 +08:00
failhdr; \
pack_unpack: List unrecognized keys in strict unpacking Otherwise figuring out what's wrong with your JSON can be tricky, especially if you're using a single fmt string to validate a large, complicated schema. The comma delimiting will make separating keys that contain commas difficult. For example: {"foo, bar": true, "baz": false} will generate errors like: 2 object item(s) left unpacked: foo, bar, baz but that seems like a small enough corner case to not be worth much worrying. I wanted to find a way to handle this without have_unrecognized_keys, but the strbuffer tooling makes it look like I shouldn't be reaching in to do things like: strbuffer_t unrecognized_keys; unrecognized_keys.value = NULL; and then using 'unrecognized_keys.value == NULL' in place of have_unrecognized_keys.
2015-12-18 08:56:22 +08:00
if (num_ == 1) { \
fprintf(stderr, "text: \"%s\" != \"%s\"\n", error.text, texts_[0]); \
} else { \
fprintf(stderr, "text: \"%s\" does not match\n", error.text); \
} \
Add lots of tests for pack/unpack code, fix bugs found Closes GH-12.
2011-02-23 01:08:41 +08:00
exit(1); \
} \
if(strcmp(error.source, source_) != 0) { \
failhdr; \
\
fprintf(stderr, "source: \"%s\" != \"%s\"\n", error.source, source_); \
exit(1); \
} \
if(error.line != line_) { \
failhdr; \
fprintf(stderr, "line: %d != %d\n", error.line, line_); \
exit(1); \
} \
if(error.column != column_) { \
failhdr; \
fprintf(stderr, "column: %d != %d\n", error.column, column_); \
exit(1); \
} \
if(error.position != position_) { \
failhdr; \
fprintf(stderr, "position: %d != %d\n", error.position, position_); \
exit(1); \
} \
} while(0)
Make real number encoding and decoding work under all locales The decimal point '.' is changed to locale's decimal point before/after JSON conversion to make C standard library's locale-specific string conversion functions work correctly. All the tests now call setlocale(LC_ALL, "") on startup to use the locale set in the environment. Fixes GH-32.
2011-10-03 02:27:53 +08:00
pack_unpack: List unrecognized keys in strict unpacking Otherwise figuring out what's wrong with your JSON can be tricky, especially if you're using a single fmt string to validate a large, complicated schema. The comma delimiting will make separating keys that contain commas difficult. For example: {"foo, bar": true, "baz": false} will generate errors like: 2 object item(s) left unpacked: foo, bar, baz but that seems like a small enough corner case to not be worth much worrying. I wanted to find a way to handle this without have_unrecognized_keys, but the strbuffer tooling makes it look like I shouldn't be reaching in to do things like: strbuffer_t unrecognized_keys; unrecognized_keys.value = NULL; and then using 'unrecognized_keys.value == NULL' in place of have_unrecognized_keys.
2015-12-18 08:56:22 +08:00
/* Assumes json_error_t error */
#define check_error(text_, source_, line_, column_, position_) \
check_errors(&text_, 1, source_, line_, column_, position_)
Make real number encoding and decoding work under all locales The decimal point '.' is changed to locale's decimal point before/after JSON conversion to make C standard library's locale-specific string conversion functions work correctly. All the tests now call setlocale(LC_ALL, "") on startup to use the locale set in the environment. Fixes GH-32.
2011-10-03 02:27:53 +08:00
static void run_tests();
int main() {
#ifdef HAVE_SETLOCALE
setlocale(LC_ALL, "");
#endif
run_tests();
return 0;
}
Expand value test coverage
2009-08-19 02:33:45 +08:00
#endif
Reference in New Issue Copy Permalink