Tutorial · target: how to mock external api calls in integration tests
How to Generate Payment gateway fixture for a stubbing walkthrough Seed Data with One Command
User cannot call a third-party API from tests and needs a faithful stand-in.
Direct answer
Generating a seed and a negative fixture set for Payment gateway fixture for a stubbing walkthrough takes one generate command and produces a set of committed files, with no hand-written INSERT statement in between.
The steps assume Node.js 22.6 or newer and the schema document that ships with this page; a schema with remote $ref URLs needs the files downloaded first.
One generate command writes 2 tables in dependency order into ./seed/sql/seed.sql, and the negative cases go to ./seed/sql/negatives.sql beside it; the same run also writes the pytest suite in ./seed/pytest, where each negative case is asserted against the schema keyword it breaks.
Data as of 2026-11-18 · source: 30 Stack Overflow questions, 1 Hacker News stories, msw at 128,057,365 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
Prerequisites — Payment gateway
You need a schema document for Payment gateway fixture for a stubbing walkthrough and a Node.js runtime. The Payment gateway fixture for a stubbing walkthrough fixture used here has 2 tables, and the commands below assume the file is at openapi/file that ships with this page. Nothing else is required: no database connection, no API key, no network access at generation time.
The steps
One command does the work. The generate command reads the schema, writes the seed and the negative cases in a single pass, and prints what it produced: the tables it wrote, the rows per table and the number of negative cases. For Payment gateway fixture for a stubbing walkthrough that is 2 tables in dependency order, with 11 constraints carried into the DDL. Two read-only commands sit next to it for checking instead of writing: validate reports the $ref chains that cannot be resolved and exits non-zero when one is broken, and inspect prints the tables, columns, primary keys and foreign keys the tool derived.
What you end up with
A set of committed artefacts: the PostgreSQL seed script, the negative SQL cases and the pytest suite. The seed for Payment gateway fixture for a stubbing walkthrough contains 2 table definitions and their rows in dependency order. The negative file holds the instances the API must reject, one per constraint class that the fixture declares, and the pytest suite carries both the valid rows and the negative ones. All of them are text, all of them diff in review, and all of them are regenerated by re-running the same command.
Wiring it into CI
The CI step is a diff, not a test. Regenerate the seed and fail the build if the committed file differs from the regenerated one. That single check catches the case where Payment gateway fixture for a stubbing walkthrough changed shape and the fixture did not, which is the failure that a hand-maintained seed produces silently for months.
Troubleshooting
If the generator warns about a schema it skipped, the warning names the construct. For Payment gateway fixture for a stubbing walkthrough, the constructs worth knowing about are the range declaration on charges.amount_cents and the reference from charges to merchants. A skipped construct is reported, never silently dropped, which is the behaviour to insist on from any tool in this position.
| Failure class | Column | SQLSTATE | Error name | Engine message (verbatim) |
|---|---|---|---|---|
| Missing required field | merchants.name | 23502 | not_null_violation | NOT NULL constraint failed: merchants.name |
| Out-of-contract value | charges.amount_cents | 23514 | check_violation | CHECK constraint failed: charges_amount_cents_check |
| Dangling foreign key | charges.merchant_id | 23503 | foreign_key_violation | FOREIGN KEY constraint failed |
| Table | Referenced by | Written |
|---|---|---|
| merchants | charges | after charges |
| charges | — | first, no dependencies |
npx --yes @wenlu8848/schemaseed generate --input ./tut_gateway.openapi.yaml --out ./seed --formats ts --count 10 --seed 42
Download tut_gateway.openapi.yaml
// Generated by schemaseed.
export * from './merchants.js';
export * from './charges.js';
Frequently asked questions
- How long does the whole workflow take?
- One generate command and a moment on the Payment gateway fixture for a stubbing walkthrough fixture of 2 tables; the slow part is deciding the row order, which is exactly what the generator removes.
- What do I commit to the repository?
- The generated files, all as text: the PostgreSQL seed script, the negative SQL cases and the pytest suite. Re-running with the same seed reproduces them byte for byte on the Payment gateway fixture for a stubbing walkthrough schema.
- Does the CI step need a database?
- The drift check does not: it regenerates and fails if the committed file differs. Add a database service only if you also load the 2 tables.
- What happens if my schema changes?
- The regenerated file differs, CI fails with the diff attached, and every declaration in the schema is re-read, so a new one appears in the negative set immediately.
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