61887e7c2f
(cherry picked from commit
|
||
---|---|---|
.. | ||
constraints.txt | ||
fail0.json | ||
fail1.json | ||
fail2.json | ||
fail3.json | ||
fail4.json | ||
fail5.json | ||
fail6.json | ||
fail7.json | ||
fail8.json | ||
fail9.json | ||
fail10.json | ||
fail11.json | ||
fail12.json | ||
fail13.json | ||
fail14.json | ||
fail15.json | ||
fail16.json | ||
fail17.json | ||
fail18.json | ||
fail19.json | ||
fail20.json | ||
fail21.json | ||
fail22.json | ||
fail23.json | ||
fail24.json | ||
fail25.json | ||
fail26.json | ||
fail27.json | ||
fail28.json | ||
fail29.json | ||
fail30.json | ||
pass0.json | ||
pass1.json | ||
pass2.json | ||
pass3.json | ||
pass4.json | ||
README | ||
testserver.py |
The files were taken from http://www.json.org/JSON_checker/ > If the JSON_checker is working correctly, it must accept all of the pass*.json files and reject all of the fail*.json files. Difference with JSON_checker dataset: - *${n}.json renamed to *${n-1}.json to be 0-based - fail0.json renamed to pass3.json as python json module allows JSON payload to be string - fail17.json renamed to pass4.json as python json module has no problems with deep structures - fail32.json renamed to fail0.json to fill gap - fail31.json renamed to fail17.json to fill gap