Test data management: synthetic data, vaults and GDPR
Test data is the part of a test that is hardest to keep honest. Production copies carry personal data and a legal duty; hand-written fixtures go stale; shared accounts collide when two runs use them at once. Good test data management generates what a test needs, isolates it per run, keeps secrets out of the test itself, and knows which fields need their boundary values exercised.
The pages here cover generation (the data factory, with its country formats), the credential vault, what GDPR and India’s DPDP Act mean for a test database, and the case generator for the values at a field’s edges.
What people search for
The literal queries this hub is written to answer; each leads to one of the pages below.
- test data generator
- synthetic test data
- test data management tools
- gdpr test data
- boundary value analysis
- test case generator
Learn
Definitions and the legal frame.
Synthetic test data
Generated, realistic, nobody’s.
GDPR-safe test data
Why a production copy is a processing activity.
Boundary value analysis
The six values that find an off-by-one.
Equivalence partitioning
One value per class.
Do it
The guides and the generator.
Test Data Factory
Generate realistic records in the formats of each country the product covers.
Test case generator
Boundary and class cases for one field, as a table and CSV.
Login flows and authenticated pages
Test accounts, saved sessions and what a stale one looks like.
Prove it
The product pages.
Test data generator and credential vault
The module, with its limits.
Security and data handling
Where test data lives and how it is protected.
Test data by country: the privacy law and what covers a transfer
Synthetic test data matters because of these laws: data that was never personal needs no transfer basis. Each row names the privacy law and what covers personal data held in India, as that country’s page states it.
| Country | Privacy law | What covers data held in India |
|---|---|---|
| United States | State comprehensive privacy laws | The Data Processing Addendum; no general federal data-localisation law applies |
| United Kingdom | UK GDPR and the Data Protection Act 2018 | International Data Transfer Agreement, or the EU clauses with the UK Addendum, and the data protection test |
| India | Digital Personal Data Protection Act, 2023 and the 2025 Rules, phased to May 2027 | None needed for storage: customer data is stored in India |
| Canada | PIPEDA; Quebec Law 25 | The addendum with a comparable-level-of-protection clause; a privacy impact assessment in Quebec |
| Australia | Privacy Act 1988 and the Australian Privacy Principles | APP 8: you stay accountable for the overseas disclosure; safeguards agreed on the addendum |
| Ireland | GDPR and the Data Protection Act 2018 | EU Standard Contractual Clauses, Module Two, with a transfer impact assessment |
| Singapore | Personal Data Protection Act 2012 | A contract binding the recipient to protection comparable to the PDPA: the addendum |
| Germany | DSGVO (GDPR) and the BDSG | EU Standard Contractual Clauses, Module Two, with a transfer impact assessment |
| France | RGPD and the loi Informatique et Libertés | EU Standard Contractual Clauses, Module Two, with a transfer impact assessment |
| Netherlands | AVG (GDPR) and the Uitvoeringswet AVG | EU Standard Contractual Clauses, Module Two, with a transfer impact assessment |
| United Arab Emirates | Federal PDPL (Decree-Law No. 45 of 2021); the DIFC and ADGM run their own regimes | Agreed at contract stage: the PDPL executive regulations were not found published when checked |
| Japan | Act on the Protection of Personal Information (APPI) | Informed consent, or a contract binding the recipient to measures equivalent to the APPI |
| Indonesia | UU 27/2022 (UU PDP), with PP 33/2026 in force from 16 January 2027 | Adequate and binding safeguards under UU PDP Article 56: the addendum; banks also need OJK approval |
Questions people ask
Can I use a copy of production data for testing?
Under GDPR and India’s DPDP Act a copy of personal data is still personal data: it needs a lawful basis, minimisation and the same protection as production. Most teams are better served by generated data that has the shape of production without its people. The GDPR-safe test data article sets out the options with their obligations.
What is synthetic test data?
Data generated to look and behave like real records (valid postcodes, realistic names, plausible dates) without describing any real person. It keeps tests realistic and keeps personal data out of test systems. The Test Data Factory generates it per country format.
How many test cases does one input field need?
For a range, at least the six boundary values (each edge, one step inside, one step outside), one typical value, and the inputs that break parsers: empty, whitespace, letters, exponent notation and non-Latin characters. The test case generator produces that set with the expected outcome for each.
Try it on your own application
The Free plan asks for no card and runs for 14 days after the trial: record a flow, replay it, and read the evidence each step produced.