Guides
Start with the problem you have.
Grouped by what went wrong rather than by feature. Every guide is a full write-up, not a stub.
Getting your data right
Start here if your seed script is fighting you, or if generated data keeps violating constraints.
Faker Works Fine Until Your Schema Has Foreign Keys
4 minRandom values per table look great in isolation and fall apart the moment your data has relationships. Here is why, and what to do instead.
Nobody Can Onboard Without a Working Local Database
4 minDay one goes fine until step four of the README. The seeding script rotted months ago and the person who wrote it has left.
Fixing an unreliable test suite
For suites that fail differently every run, and for CI failures nobody can reproduce.
Your Tests Aren't Flaky. Your Test Data Is.
4 minMost flaky test suites are not a timing problem. They are a shared mutable state problem wearing a timing costume.
Same Rows Every Run: Why CI Needs Deterministic Test Data
4 minA failure you cannot reproduce is not a bug report. It is a rumour. Determinism is what turns one into the other.
Performance and scale
For load tests that pass and then fall over in production at a tenth of the volume.
Getting production data out of your lower environments
For the copy in staging that nobody defends and everybody keeps, and the compliance conversation around it.
Your Staging Database Is a Copy of Production. That's a Breach With a Delay Timer.
5 minNobody defends this practice. Everybody does it. Here is the honest accounting of what you are actually exposing.
Masking Production Data Is Not Anonymisation
4 minReplacing the name field feels like privacy work. Uniqueness in combination is what identifies people, and masking leaves it intact.
The Data Your Bugs Live In Never Survives the Copy
4 minSanitising a production dump removes exactly the rows that break things. The tidy result is the least useful dataset you could have built.
Compliance Says No to Real Data in Test. Now What?
5 minThe policy is usually right. The problem is that nobody funded the alternative, so teams comply on paper and copy anyway.
The Three Day Ticket: Why Refreshing Test Data Needs a DBA and Shouldn't
4 minThe provisioning queue is not a tooling problem. It is a permissions problem that everyone has learned to work around.
Not covered here
For API endpoints and tier limits, read the documentation. For a question about your own schema, ask in the community or get in touch.