Skip to content

Latest commit

 

History

History
39 lines (30 loc) · 1.82 KB

README.md

File metadata and controls

39 lines (30 loc) · 1.82 KB

JSON Patch failure behavior

These three scenarios call jsonpatch 1.39. One inserts a list item and updates the key a/b through an escaped JSON Pointer. In the other two, a successful replacement is followed by a failing test. Copy mode preserves the original document. In-place mode retains the earlier write.

From the repository root, using an activated Python 3.12 virtual environment:

python -m pip install -r examples/jsonpatch/requirements.txt
python examples/jsonpatch/verify.py --report jsonpatch-report.json

The verifier runs the installed interaction-check 0.1.0b1 package in isolated mode and checks the version in its report. Omit --report for a temporary report. Run the native input check with python -m unittest discover -s examples/jsonpatch -p native_tests.py.

The scenarios and input handling were extracted from PR #14. The upstream tutorial shows how to exercise copy and in-place behavior directly with the Python API.

Check an unpublished candidate separately

The published baseline above remains pinned to 0.1.0b1. To test the current wheel without replacing that baseline environment:

python -m pip install build
python -m build --wheel
python examples/jsonpatch/check_candidate.py dist --expected-version 0.1.0 --report candidate-jsonpatch.json

Use a distribution directory containing exactly one wheel. The candidate check creates and removes its own virtual environment, installs that wheel together with jsonpatch 1.39 / jsonpointer 3.5, runs the native input tests and all three scenarios in isolated mode, and checks the report's runner version. It does not import the source checkout. CI runs both the published and candidate checks on three systems.