RepoMirrors/cJSON
1
0
Fork 0
mirror of https://github.com/DaveGamble/cJSON synced 2024-12-23 23:22:09 +00:00
Code Issues Releases Wiki Activity
Ultralightweight JSON parser in ANSI C
3 Commits 11 Branches 48 Tags 9.6 MiB
C 80.2%
Ruby 14.9%
CMake 2%
Makefile 1.5%
Python 1.3%
ffb877c94a
Go to file
Max Bruckner ffb877c94a Squashed 'tests/json-patch-tests/' changes from 5405313..0dd0fbc 
0dd0fbc tests.json: Test case sensitivity
01348ad tests.json: Remove trailing whitespace

git-subtree-dir: tests/json-patch-tests
git-subtree-split: 0dd0fbc5ec7eb9dab362fab47e08419079d5675e
2017-05-02 01:56:12 +02:00
.editorconfig Squashed 'tests/json-patch-tests/' content from commit 716417e 2017-04-11 14:45:28 +02:00
.gitignore Squashed 'tests/json-patch-tests/' content from commit 716417e 2017-04-11 14:45:28 +02:00
.npmignore Squashed 'tests/json-patch-tests/' content from commit 716417e 2017-04-11 14:45:28 +02:00
package.json Squashed 'tests/json-patch-tests/' content from commit 716417e 2017-04-11 14:45:28 +02:00
README.md Squashed 'tests/json-patch-tests/' content from commit 716417e 2017-04-11 14:45:28 +02:00
spec_tests.json Squashed 'tests/json-patch-tests/' content from commit 716417e 2017-04-11 14:45:28 +02:00
tests.json Squashed 'tests/json-patch-tests/' changes from 5405313..0dd0fbc 2017-05-02 01:56:12 +02:00

README.md

JSON Patch Tests

These are test cases for implementations of IETF JSON Patch (RFC6902).

Some implementations can be found at jsonpatch.com.

Test Format

Each test file is a JSON document that contains an array of test records. A test record is an object with the following members:

  • doc: The JSON document to test against
  • patch: The patch(es) to apply
  • expected: The expected resulting document, OR
  • error: A string describing an expected error
  • comment: A string describing the test
  • disabled: True if the test should be skipped

All fields except 'doc' and 'patch' are optional. Test records consisting only of a comment are also OK.

Files

  • tests.json: the main test file
  • spec_tests.json: tests from the RFC6902 spec

Writing Tests

All tests should have a descriptive comment. Tests should be as simple as possible - just what's required to test a specific piece of behavior. If you want to test interacting behaviors, create tests for each behavior as well as the interaction.

If an 'error' member is specified, the error text should describe the error the implementation should raise - not what's being tested. Implementation error strings will vary, but the suggested error should be easily matched to the implementation error string. Try to avoid creating error tests that might pass because an incorrect error was reported.

Please feel free to contribute!

Credits

The seed test set was adapted from Byron Ruth's jsonpatch-js and extended by Mike McCabe.

License

Copyright 2014 The Authors

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.