Alternative · target: faker alternative for api testing
@faker-js/faker Alternative for HR directory API Seed Data
Generic faker produces names and emails but ignores the API contract, so tests break on shape.
Direct answer
SchemaSeed reads the HR directory API schema and writes loadable rows; @faker-js/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 @faker-js/faker is usually sufficient.
The same HR directory API schema run through @faker-js/faker yields a JSON document whose employees.department_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: 2 Stack Overflow questions, 2 Hacker News stories, @faker-js/faker at 95,721,308 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 — HR directory
@faker-js/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 HR directory API fixture is one table with no cross-table references, the honest answer is that @faker-js/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. @faker-js/faker reads one schema and produces one document; it has no second schema to read, so it cannot know that employees.department_id must point at a row in departments. 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 HR directory 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 HR directory API the diff is usually small: 2 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 @faker-js/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.
| Criterion | SchemaSeed | @faker-js/faker | What decided it |
|---|---|---|---|
| Reads a multi-file OpenAPI document | yes | no | both resolve local $ref chains |
| Honours NOT NULL | yes | no | both read the required array |
| Honours enum, range and length declarations | yes | no | the fixture declares employees.salary_cents with "salary_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 members | yes | no | the enum array is copied verbatim |
| Produces SQL, not just JSON | yes | no | output format is the difference |
| Resolves foreign keys across schemas | yes | no | the fixture has employees.department_id pointing at departments, and the second tool never reads that table |
| Emits deliberately invalid instances | yes | no | negative cases are a separate output |
| Same seed produces the same bytes | yes | yes | both are seedable |
| Failure class | Column | SQLSTATE | Error name | Engine message (verbatim) |
|---|---|---|---|---|
| Missing required field | departments.name | 23502 | not_null_violation | NOT NULL constraint failed: departments.name |
| Out-of-contract value | employees.salary_cents | 23514 | check_violation | CHECK constraint failed: employees_salary_cents_check |
| Dangling foreign key | employees.department_id | 23503 | foreign_key_violation | FOREIGN KEY constraint failed |
| Check | Result on this fixture | Consequence |
|---|---|---|
| More than one table references another | yes — employees → departments | the generator must resolve cross-table references |
| Output has to be SQL, not JSON | yes — the target is PostgreSQL | a document generator produces the wrong artefact |
| Tests must assert the API rejects bad input | yes — a negative case for every declaration in the schema | negative instances have to be generated separately |
| Same seed must reproduce the same bytes | yes — seed 42 is fixed | fixtures can be committed and diffed |
npx --yes @wenlu8848/schemaseed generate --input ./hr.openapi.yaml --out ./seed --formats ts --count 10 --seed 42
// Generated by schemaseed.
export * from './departments.js';
export * from './employees.js';
Frequently asked questions
- Is @faker-js/faker still worth using?
- For one flat schema, yes. The gap opens on HR directory API: @faker-js/faker produces values for a single schema, while this fixture has 2 related tables that have to load together.
- Can I keep the fixtures I already wrote?
- Yes. Regenerate against the same HR directory API schema and diff. On this fixture only the constrained columns move, and the negative cases are additive.
- Does SchemaSeed replace @faker-js/faker entirely?
- No. It is a different artefact: @faker-js/faker produces values for one schema, SchemaSeed produces a TypeScript fixture plus invalid instances for 2 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