What is Test Data Management?
What test data management is, who needs it, and the lifecycle that turns "we need data" into a safe, certified dataset in a test environment.
Topics
Test data management fundamentals
Test data management is the discipline of giving every team the data it needs to test, without handing out copies of production. This hub collects the introductory material: what the discipline covers, why the habit of cloning production causes incidents, and how environments differ in what they need.
Start with the pillar article, then follow the cluster pages in order, or take the readiness assessment to see where your own team stands.
Start here
Go deeper
Why production copies are risky
Why cloning production into test environments creates privacy, security and operational risk, and what a governed alternative looks like.
Test data as a product
Treating datasets like products with owners, versions, documentation and a retirement plan, instead of one-off copies nobody maintains.
DEV vs QA vs SIT vs UAT vs Performance
How data needs differ across development, QA, system integration, user acceptance and performance environments, and how to serve each one.
Storage and compute optimization
Practical levers for reducing the cost of test data — subsetting, reuse, right-sized jobs and expiry — without sacrificing realism.
TDM Readiness Assessment
How It Works
Masked subsets or synthetic data — choosing per test
When a test should run on synthetic data and when it needs a masked subset of real data, with a runnable check of the markers that make synthetic rows unmistakable.
Planning a test-data refresh cadence
Read a pack's weekly refresh policy, compute the next refresh windows and see which settings stop needless rebuilds — a runnable example on a published policy template.
Teams