huanggen cbe0f7017e 【bug修复】(黄根)增加sql语句中单引号自动的转义处理,以规避因sql执行失败导致的扫描程序异常的问题 | 2 yıl önce | |
---|---|---|
.. | ||
bin | 2 yıl önce | |
remotes | 2 yıl önce | |
tests | 2 yıl önce | |
.gitignore | 2 yıl önce | |
.travis.yml | 2 yıl önce | |
LICENSE | 2 yıl önce | |
README.md | 2 yıl önce | |
tox.ini | 2 yıl önce |
This repository contains a set of JSON objects that implementors of JSON Schema validation libraries can use to test their validators.
It is meant to be language agnostic and should require only a JSON parser.
The conversion of the JSON objects into tests within your test framework of choice is still the job of the validator implementor.
If you're going to use this suite, you need to know how tests are laid out. The
tests are contained in the tests
directory at the root of this repository.
Inside that directory is a subdirectory for each draft or version of the
schema. We'll use draft3
as an example.
If you look inside the draft directory, there are a number of .json
files,
which logically group a set of test cases together. Often the grouping is by
property under test, but not always, especially within optional test files
(discussed below).
Inside each .json
file is a single array containing objects. It's easiest to
illustrate the structure of these with an example:
{
"description": "the description of the test case",
"schema": {"the schema that should" : "be validated against"},
"tests": [
{
"description": "a specific test of a valid instance",
"data": "the instance",
"valid": true
},
{
"description": "another specific test this time, invalid",
"data": 15,
"valid": false
}
]
}
So a description, a schema, and some tests, where tests is an array containing one or more objects with descriptions, data, and a boolean indicating whether they should be valid or invalid.
Draft 3 and 4 should have full coverage. If you see anything missing or think there is a useful test missing, please send a pull request or open an issue.
This suite is being used by:
The JSON Schema Test Suite is also available as an npm package. Node-specific support is maintained on the node branch. See NODE-README.md for more information.
If you use it as well, please fork and send a pull request adding yourself to the list :).
If you see something missing or incorrect, a pull request is most welcome!
There are some sanity checks in place for testing the test suite. You can run
them with bin/jsonschema_suite check
or tox
. They will be run automatically by
Travis CI as well.