JSONTestSuite
JSONTestSuite copied to clipboard
nst
A comprehensive test suite for RFC 8259 compliant JSON parsers
From RFC7159: > Any character may be escaped. If the character is in the Basic > Multilingual Plane (U+0000 through U+FFFF), then it may be > represented as a six-character...
I'll take a bite of it (would take a while I guess)
The RFC permits extensions. For example, jq accepts some representations of infinity, and is a bit liberal about number representations. A number of `n_*` tests could be labeled as "failure...
Tests like `parsers/test_ccan_json/json/_test/nst_files/n_31.json` (of which there are many) fail with jq only because jq permits multiple JSON texts in one input stream. I'm not saying this is permissible JSON, just...
Tests like `parsers/test_ccan_json/json/_test/nst_files/n_31.json` (of which there are many) fail with jq only because jq permits multiple JSON texts in one input stream. I'm not saying this is permissible JSON, just...
A quick glance over some files inside the `test_parsing` folder show that most of the files that don't run through the JS-native `JSON.parse()` method are actually encoded in `latin1` and...
Even being the birthplace of JSON, JavaScript still has several implementations and engines which behave differently. The parser labeled "JavaScript" uses NodeJS, whichever version is currently installed indiscriminately. I tested...
For some (probably silly) reasons `run_tests` is [commented out](https://github.com/nst/JSONTestSuite/blob/master/run_tests.py#L858) in `run_tests.py`
I've written a JSON parser in Dlang and was looking for a test suite that would contain extreme number test cases. You seem to have put a lot of effort...
