Generate Deterministic Edge Fixtures from a Small JSON Schema

How to Use This Tool

Create minimum, maximum, missing and wrong-type cases without claiming exhaustive schema testing. Generate deterministic JSON boundary fixtures from common schema constraints, label expected validity, and download a reproducible QA case set locally.

The work this page finishes

QA teams repeatedly hand-edit one valid object into edge cases, then lose which mutation was expected to pass and which schema features were never covered. For JSON Edge Fixtures, the row-preserving workspace makes a correction repeatable without rebuilding a prompt or transmitting the source file.

Deterministic workflow

Build one stable baseline from supported primitive constraints, vary one property at a time, remove required fields and optionally substitute a deterministic wrong type. For JSON Edge Fixtures, this page accepts at most 5,000 records and 2 MB of text; rejected items retain their row references while valid items remain available.

Why a dedicated interface helps

Treat the output as a transparent starter fixture set and add domain invariants manually; the scope label prevents it from being mistaken for exhaustive property testing. For JSON Edge Fixtures, immediate recalculation and a stable export are useful when the same rule must be applied consistently across a list instead of explained one item at a time.

Assumptions

• The root type is object.
• Primitive property constraints are self-contained.
• A review fixture at a maximum still needs the destination validator as oracle.

For JSON Edge Fixtures, retain the original source until the destination accepts the result; processing stays in this tab, although the device and installed extensions remain part of the user's security boundary.

Limitations and review boundary

It supports a narrow object/property subset and does not resolve references, compositions, patterns, formats, conditional schemas, uniqueItems or custom validators. For JSON Edge Fixtures, no supplied URL is requested and no pasted markup or code is executed; output is inserted through text-only DOM operations.

Verification and provenance

The implementation was checked against JSON Schema 2020-12 specification on 2026-08-26, with fixtures for a known answer, an invalid input and a batch-specific edge condition. The sample produces a valid minimum object, one maximum and wrong-type case per property, plus two missing-required fixtures.