Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/json-patch/json-patch-tests
Tests for implementations of json-patch
https://github.com/json-patch/json-patch-tests
ietf json json-patch spec-tests
Last synced: 2 months ago
JSON representation
Tests for implementations of json-patch
- Host: GitHub
- URL: https://github.com/json-patch/json-patch-tests
- Owner: json-patch
- Fork: true (mikemccabe/json-patch-tests)
- Created: 2012-12-03T03:16:03.000Z (about 12 years ago)
- Default Branch: master
- Last Pushed: 2020-05-04T18:06:19.000Z (over 4 years ago)
- Last Synced: 2024-11-11T18:52:33.722Z (3 months ago)
- Topics: ietf, json, json-patch, spec-tests
- Size: 47.9 KB
- Stars: 68
- Watchers: 16
- Forks: 21
- Open Issues: 8
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
JSON Patch Tests
================These are test cases for implementations of [IETF JSON Patch (RFC6902)](http://tools.ietf.org/html/rfc6902).
Some implementations can be found at [jsonpatch.com](http://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 skippedAll 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 specWriting 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](https://github.com/bruth/jsonpatch-js/blob/master/test.js) and
extended by [Mike McCabe](https://github.com/mikemccabe).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 athttp://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.