Test Data Management
Realistic data without copying production personal data into a weaker environment.
6 to work through
-
intermediate
What are the test-data options, what must be true regardless, and which combination actually finds the bugs that reach production?
2 min answer -
advanced
A multi-tenant platform's tests depend on shared test data that drifts and breaks. What test data strategy works?
2 min answer -
advanced
A payments platform needs realistic test data. What are the options, and what must be true regardless?
2 min answer -
advanced
A team wants an ephemeral database per pull request, seeded from a 4 TB production schema of about 900 tables. Roughly how large is a referentially consistent subset that supports the functional test suite, how long does creating one take, and which assumption dominates the estimate?
3 min answer -
advanced
Review this setup. A nightly masked clone of production feeds three shared environments, a subsetting tool builds per-team slices on request through a ticket queue with a two-day turnaround, and a synthetic generator covers new features. What would you remove, and what is the one change that matters?
3 min answer -
advanced
Your test environments use a nightly copy of the production database. Legal has raised it. What is the replacement?
2 min answer
5 terms in this topic
Anomaly Retention
Preserving the malformed, historical and hand-fixed records when producing test data - because they are precisely what breaks migrations and new code…
practiceReferentially Consistent Subset
A small extract of a production-shaped database in which every referenced row is present, so a test suite runs against realistic structure at a size …
practiceTest Data Management
The problem of getting data that is realistic enough to find defects and safe enough to exist outside production.
practiceTest Data Provisioning
Getting each test the data it needs, in a state it can rely on, without copying production personal data into a weaker environment.
patternTest-Owned Data
Each test creating the exact data it needs through the product's own write path and disposing of it afterwards - replacing shared fixtures whose drif…
Neighbouring topics
Testing & Quality Architecture
General material on designing a testing strategy as an architectural concern.
Test Architecture Strategy
Choosing what to verify where, given the failure modes that actually occur.
Test Pyramid Shapes
Pyramid, trophy and honeycomb, and the system properties that justify each shape.
Integration Test Boundaries
What sits inside a test's boundary, what is faked, and the confidence that follows.
Contract Testing at Scale
Keeping dozens of services compatible without an environment that runs all of them.
Consumer-Driven Contracts
Consumers declaring what they rely on, and providers verifying against those declarations.
Synthetic Data
Generating data with the shape and edge cases of the real thing, and where it misleads.
Environment Parity
The differences between staging and production that decide which bugs survive to release.
Service Virtualisation
Standing in for a dependency you cannot call, and keeping the stand-in honest.
End-to-End Test Economics
Why broad end-to-end suites get slow, flaky and abandoned, and what to keep.
Non-Functional Test Strategy
Testing availability, latency, security and recovery rather than only behaviour.
Performance Test Design
Workload models, warm-up, think time, and the distribution the average hides.
Chaos as a Test
Fault injection with a hypothesis, a blast radius and an abort condition.
Security Testing in the Pipeline
SAST, DAST, dependency and secret scanning, and what to do with the findings.
Accessibility Testing
Automated checks, their ceiling, and the manual testing that has to sit above it.
Mutation Testing
Measuring whether tests would actually notice a defect, not just cover a line.
Flaky Test Management
Quarantine, detection, and the trust a suite loses once red stops meaning broken.
Testing in Production
Synthetic transactions, dark launches and shadow traffic, done deliberately and safely.
Quality Gates
Thresholds that block a release, who may override them, and how they decay.