Guide

THE TOOLBOX / TESTING & DATABASE SEEDING

Generate deterministic
JSON, CSV & SQL fixtures.

Synthesize reproducible users, e-commerce orders, and audit telemetry using a seeded Mulberry32 PRNG and export to JSON, CSV, SQL INSERT, or TypeScript.

Mulberry32 PRNG · Seed #42
12 rows · 8 cols · 3.1 KB
100% client-side · Zero row limits

Generated 12 deterministic users records with Mulberry32 seed 42.

THE DETAILS

Mulberry32 seeded pseudorandomness, RFC 4180 CSV serialization, and multi-row SQL seeding.

1. Seeded Mulberry32 Deterministic PRNG

Unlike `Math.random()`, which cannot be seeded in JavaScript, our engine uses the 32-bit Weyl-sequence Mulberry32 algorithm. Sharing a seed number (`42`) across your team produces identical UUIDs, names, amounts, and ISO 8601 timestamps every time.

2. Multi-Row Batch SQL INSERT Statements

Switch to the SQL INSERT tab to generate a single multi-tuple `INSERT INTO table (...) VALUES (...), (...);` statement that executes up to $20\times$ faster than individual single-row inserts during database seeding.

3. Strongly Typed TypeScript Fixtures

The TypeScript tab emits both an `export interface MockRecord` declaration and a `readonly MockRecord[]` constant so you can drop realistic mock rows directly into Vitest, Jest, Playwright, or Storybook stories.

Fixture Export Formats & Target Integration Matrix

Export FormatEncoding & Escaping StandardPrimary Engineering Workflow
JSON Array (.json)RFC 8259 UTF-8 (2-space indented)MSW (Mock Service Worker), Postman, Prisma seeds
CSV Table (.csv)RFC 4180 (header row + doubled quote escaping)PostgreSQL \copy, DuckDB, spreadsheet imports
SQL Batch (.sql)ANSI SQL-92 multi-row INSERT INTOPostgreSQL, MySQL, SQLite, D1 migration seeds
TypeScript (.ts)export interface + readonly arrayVitest/Playwright unit tests & Storybook stories

Common Test Data & Database Seeding Pitfalls

Using Production Customer PII in Staging

Copying production database dumps into staging or local laptops risks GDPR/SOC2 violations and accidental customer emails. Always seed non-production environments with synthetic fixtures.

Flaky CI Snapshots from Unseeded Mocks

Calling unseeded faker utilities inside component tests causes visual regression and snapshot diffs on every commit. Lock a deterministic seed (`42`) for repeatable CI builds.

Floating-Point Currency Rounding

When storing monetary amounts in SQL databases, prefer integer cents (`BIGINT`) or `NUMERIC(12, 2)` columns rather than `REAL` / `FLOAT` to avoid binary rounding drift.

Primary Key Sequence Desynchronization

In PostgreSQL, inserting explicit `id` values into a `SERIAL` or `IDENTITY` column does not advance the underlying sequence automatically; run `setval(pg_get_serial_sequence(...))` after seeding.

Frequently Asked Questions

Why does a deterministic PRNG seed matter for unit and E2E test fixtures?

Non-deterministic random generators produce different records on every test run, causing snapshot tests to fail and making race conditions or pagination bugs impossible to reproduce. Our Mulberry32 seeded PRNG guarantees that Seed 42 generates the exact same UUIDs, emails, timestamps, and currency totals on every developer machine and CI runner.

Which export formats are supported for seeding databases and frontend mocks?

You can switch instantaneously between formatted JSON arrays, RFC 4180 CSV tables with header rows, batch SQL INSERT INTO statements (compatible with PostgreSQL, MySQL, and SQLite), and strongly typed TypeScript interfaces with const fixture arrays.

Are the generated email addresses safe to use in staging environments?

Yes. All generated email addresses use the reserved .dev / example testing namespace so automated test runs never accidentally email real external recipients.

How are single quotes and commas escaped in SQL and CSV outputs?

In SQL INSERT mode, internal single quotes are doubled per ANSI SQL rules. In CSV mode, fields containing commas, quotes, or newlines are enclosed in double quotes with internal quotes doubled per RFC 4180.

Does generating 500 rows require an account or server call?

No. All fixture synthesis runs in-memory inside your browser tab in under 5 milliseconds with zero network calls and no row paywalls.