Alternative · target: json schema test data generator alternative

json-schema-faker Alternative for Insurance claims API Seed Data

User wants a test-data generator and specifically wants invalid instances, not only valid ones.

Direct answer

SchemaSeed reads the Insurance claims API schema and writes loadable rows; json-schema-faker generates values for one document, with no SQL and no invalid instances. The gap appears with cross-table references.

That gap only matters once the fixture has two or more tables that reference each other, or once a test suite must assert the API rejects malformed input; for one flat schema json-schema-faker is usually sufficient.

The same Insurance claims API schema run through json-schema-faker yields a JSON document whose claims.policy_id reference values that match no parent row; the reference engine rejected that shape with "FOREIGN KEY constraint failed".

Data as of 2026-11-18 · source: 4 Stack Overflow questions, ts-json-schema-generator at 6,275,268 monthly downloads · negative-case messages reproduced by executing the fixture against a local SQL engine (Node.js v24.22.0, engine 3.53.4) at 2026-11-18T11:53:54.233Z

What the incumbent does well — Insurance claims

json-schema-faker is a mature tool and it is not going away. For a single flat schema it produces valid JSON faster than anything else, and its API surface is small enough to learn in an afternoon. If your Insurance claims API fixture is one table with no cross-table references, the honest answer is that json-schema-faker is enough and this page will not change your mind.

The gap that matters for relational seeds

The gap appears the moment the fixture stops being one table. json-schema-faker reads one schema and produces one document; it has no second schema to read, so it cannot know that claims.policy_id must point at a row in policies. The result is values that are individually plausible and collectively unloadable. The reference engine rejected exactly that shape with "FOREIGN KEY constraint failed".

Side by side on the same fixture

The table below scores the two approaches against the identical Insurance claims API fixture. The rows are not opinions about architecture; each one is a property of the fixture that the reference engine can verify. The decisive row is the foreign key row, because a JSON document can carry a dangling reference without any tool complaining until the moment it is loaded.

Migrating an existing fixture

You do not have to rewrite your fixture. Keep the schema file, run the generator against it, and diff the output against the rows you already have. For Insurance claims API the diff is usually small: 3 tables, and the changes are the constrained columns, which are the ones a hand-written seed gets wrong most often. The negative case set is additive, so nothing you already depend on is lost.

How to decide in under a minute

Two questions decide it. Does your schema have more than one table that reference each other? Does your test suite need to prove the API rejects malformed input? If both answers are no, stay on json-schema-faker. If either is yes, the missing piece is the same in both cases: a generator that reads the whole document and treats the constraints as part of the contract rather than as decoration.

SchemaSeed vs json-schema-faker on the Insurance claims API fixtureEight criteria, each decided by a property of the fixture rather than by preference. The left column is what a schema-to-SQL generator does with it; the right column is what document generation leaves unresolved.
CriterionSchemaSeedjson-schema-fakerWhat decided it
Reads a multi-file OpenAPI documentyesyesboth resolve local $ref chains
Honours NOT NULLyespartialboth read the required array
Honours enum, range and length declarationsyespartialthe fixture declares policies.premium_cents with "premium_cents" >= 0; the declaration is read out of the schema, the DDL carries it as a CHECK constraint and the value that breaks it ships as a negative case
Honours enum membersyesyesthe enum array is copied verbatim
Produces SQL, not just JSONyesnooutput format is the difference
Resolves foreign keys across schemasyesnothe fixture has claims.policy_id pointing at policies, and the second tool never reads that table
Emits deliberately invalid instancesyesnonegative cases are a separate output
Same seed produces the same bytesyesyesboth are seedable
Real constraint failures for the Insurance claims API fixtureReproduced by executing the fixture against a local SQL engine (Node.js v24.22.0, engine 3.53.4) on 2026-11-18T11:53:54.233Z. The message column is verbatim engine output; the SQLSTATE column is the PostgreSQL error class for the same constraint class.
Failure classColumnSQLSTATEError nameEngine message (verbatim)
Missing required fieldpolicies.holder_name23502not_null_violationNOT NULL constraint failed: policies.holder_name
Out-of-contract valuepolicies.premium_cents23514check_violationCHECK constraint failed: policies_premium_cents_check
Dangling foreign keyclaims.policy_id23503foreign_key_violationFOREIGN KEY constraint failed
The four checks that decide whether a schema tool is enough for Insurance claims APIApplied to Insurance claims API.
CheckResult on this fixtureConsequence
More than one table references anotheryes — claims → policiesthe generator must resolve cross-table references
Output has to be SQL, not JSONyes — the target is PostgreSQLa document generator produces the wrong artefact
Tests must assert the API rejects bad inputyes — a negative case for every declaration in the schemanegative instances have to be generated separately
Same seed must reproduce the same bytesyes — seed 42 is fixedfixtures can be committed and diffed
README.md

npx --yes @wenlu8848/schemaseed generate --input ./claims.openapi.yaml --out ./seed --formats pytest --count 10 --seed 42

Download claims.openapi.yaml

# Generated pytest suite

Seed: 42 — mode: nested

Run it with:

```
pytest pytest/
```

The suite is self contained: `_validator.py` implements the JSON Schema
keywords the generated data uses, so only pytest is needed.

- `test_policies.py`: 10 valid rows, 15 negative cases (format-violation, missing-required, null-violation, range-violation, type-mismatch)
- `test_claims.py`: 10 valid rows, 24 negative cases (enum-violation, format-violation, missing-required, null-violation, range-violation, type-mismatch)
- `test_claim_items.py`: 10 valid rows, 24 negative cases (enum-violation, format-violation, missing-required, null-violation, range-violation, type-mismatch)

Frequently asked questions

Is json-schema-faker still worth using?
For one flat schema, yes. The gap opens on Insurance claims API: json-schema-faker produces values for a single schema, while this fixture has 3 related tables that have to load together.
Can I keep the fixtures I already wrote?
Yes. Regenerate against the same Insurance claims API schema and diff. On this fixture only the constrained columns move, and the negative cases are additive.
Does SchemaSeed replace json-schema-faker entirely?
No. It is a different artefact: json-schema-faker produces values for one schema, SchemaSeed produces a pytest fixture plus invalid instances for 3 related tables.
Is there a paid version?
No. The CLI is MIT licensed and free: unlimited local generation, no account, no telemetry and no usage limit, and it runs on your own machine. Sponsorship is what keeps it maintained.

Run it against your own schema

SchemaSeed is MIT licensed and free: unlimited local generation, no account, no telemetry and no usage limit. It reads your schema file on your own machine, so nothing is uploaded anywhere. If it saves you time, you can support the project.

Get SchemaSeed — free Support the project

Questions: support@schemaseed.drz8848.win