01 / PLANNED
Keep the generation context
Planned recipes would store the seed, generator version, and reference date alongside the scenario definition.
Test data workflows · Early research
Reproduce the data behind the failing test.
A planned workspace for reusable test-data recipes, related records, and pinned generation settings. Join the waitlist to shape reproducible fixtures for small teams.
Get early access ↗In research · Join the waitlist · No payment required
Designed around developers and QA teams maintaining test scenarios with related data.
Concept preview · fictional example
| Scenario | Pinned context | Purpose |
|---|---|---|
| Expired invitation | Fixed reference date | Expiry boundary |
| Account with no orders | Related tables | Empty state |
| Duplicate identifier | Deliberate constraint break | Error handling |
Illustrative sample data. This is a product concept; these features are not available yet.
MADE FOR THE WORK IN BETWEEN↗
THE FRICTION
A random record is easy to generate. Reproducing a bug needs the same relationships, boundary case, generator version, and date assumptions that produced the failure.
THE PRODUCT WE’RE EXPLORING
FixtureForge, in three parts.
FixtureForge would save test-data recipes with explicit seeds, reference dates, and versioned rules. The first pilot would focus on synthetic scenarios that teams can export and review.
Three planned capabilities we want to validate with early users.
02 / PLANNED
Model related records
Proposed rules would connect parent and child records so fixtures reflect the relationships a test depends on.
03 / PLANNED
Name the edge case
Planned scenario variants would make empty fields, boundary dates, and invalid inputs intentional and visible.
AN INTENDED WORKFLOW
A clearer next step.
Less work around it.
A focused approach for developers and QA teams maintaining test scenarios with related data.
- 01
Describe a synthetic scenario
A pilot would start with a small supported schema and generation rules, without copying production records.
- 02
Review the generated sample
Check relationships, constraints, and deliberate edge cases before exporting a dataset.
- 03
Pin and reuse the recipe
Save the exact recipe version and settings with the test so a teammate can reproduce the same scenario.
HELP SHAPE THE FIRST VERSION
A better workflow starts with your experience.
Join the FixtureForge waitlist for early-access updates and an optional research conversation.
This product is in research. Planned features and integrations are not available yet.
NO PAYMENT · NO COMMITTED LAUNCH DATEYOU’RE ON THE LIST
Thanks for raising your hand.
Your signup has been received for FixtureForge. There is no confirmation email to look out for.
Manage your data ↗GOOD TO KNOW
A few useful answers.
Is a data generator available today?
No. FixtureForge is a research waitlist. Recipe editing, generation, relationships, and exports are planned.
Why not just use a random data library?
Libraries already generate useful values. This concept tests a shared workflow for relationships, scenario versions, and the settings needed to reproduce a result.
Will it anonymize production data?
That is outside the proposed first pilot. The initial scope would be synthetic fixtures created from explicit rules, without accepting production records.