JSON Schema Draft4 Test Suite - Known Failing Tests

[simbo1905]

This issue tracks the known failing tests in the JSON Schema Draft4 Test Suite that are currently being skipped.

Test Results

• Total Tests: 759
• Passed: 469
• Failed: 0 (after skipping)
• Skipped: 290

Known Failing Tests

The following tests are skipped due to known implementation issues:

Reference Resolution Issues (16 tests)

• infinite-loop-detection.json#evaluating the same schema location against the same data location twice is not a sign of an infinite loop#passing case
• infinite-loop-detection.json#evaluating the same schema location against the same data location twice is not a sign of an infinite loop#failing case
• ref.json#nested refs#nested ref valid
• ref.json#nested refs#nested ref invalid
• ref.json#ref overrides any sibling keywords#ref valid
• ref.json#ref overrides any sibling keywords#ref valid, maxItems ignored
• ref.json#ref overrides any sibling keywords#ref invalid
• ref.json#property named , containing an actual #property named valid
• ref.json#property named , containing an actual #property named invalid
• ref.json#id with file URI still resolves pointers - *nix#number is valid
• ref.json#id with file URI still resolves pointers - *nix#non-number is invalid
• ref.json#id with file URI still resolves pointers - windows#number is valid
• ref.json#id with file URI still resolves pointers - windows#non-number is invalid
• ref.json#empty tokens in json-pointer#number is valid
• ref.json#empty tokens in json-pointer#non-number is invalid

Remote Reference Issues (4 tests)

• refRemote.json#base URI change - change folder#number is valid
• refRemote.json#base URI change - change folder#string is invalid
• refRemote.json#base URI change - change folder in subschema#number is valid
• refRemote.json#base URI change - change folder in subschema#string is invalid

JSON Parsing Issues (2 tests)

• required.json#required with escaped characters#object with all properties present is valid
• required.json#required with escaped characters#object with some properties missing is invalid

Root Causes

1. **Unresolved **: Reference resolution issues with local and remote references
2. Duplicate member names: JSON parser limitations with escaped characters in object keys
3. Remote fetching disabled: Tests requiring remote schema fetching are skipped at group level

Implementation Status

These tests are currently skipped using Assumptions.assumeTrue(false, ...) to prevent build failures while maintaining test coverage for passing tests.