Test Data Generator
Create synthetic profiles for development and localization tests. Choose a supported country and review linked fields, coverage notes and plan limits.
Preparing your test data…
Your first record will appear here shortly.
Copy individual values or export the entire result.
Synthetic identities; domains, addresses and numbers may coincide with real values. Do not contact or send payments.
Build a fixture with a purpose.
A believable profile is useful only when it exercises the behavior you want to test. Start with one scenario: a registration form, a contact card, an address layout or a data import. Choose the country and fields for that scenario, then inspect the generated quality notes before saving the fixture.
- 01
Choose the scenario
For an address form, focus on country, postal code, city and street. Avoid including unrelated banking or card fields just because they are available.
- 02
Inspect connected fields
Check that your application keeps city, region and postal information together and handles accents, long labels and missing values.
- 03
Keep a small fixture set
Save the useful examples in your own test environment. A preset stores configuration, not the generated records, so it is not a way to retrieve a previous result.
Example: a postal code is text
Input fixture: { "postalCode": "01234", "city": "Example town" }
Expected: display and export "01234" unchanged
Failure: converting to a number produces 1234This is a deliberately simplified format test, not a geographically validated address. For locality tests, use a generated record and its quality notes. For parser tests, a small hand-written fixture often makes the failure easier to understand.
| Field group | Useful check | What it does not establish |
|---|---|---|
| Names and text | Unicode, wrapping and field lengths | A real person or identity |
| City / region / postal data | Linked locality and stated coverage | Deliverability of the full street address |
| Phone and email | Display and application validation | Permission to call or send messages |
| Bank and card formats | Documented structural checks | An existing account or working payment method |
Before you use the result
Practical answers for your next test.
Should I generate new data for every automated test?
Use fixed fixtures for repeatable assertions and fresh samples for exploration. When a fresh sample reveals a bug, save a minimal synthetic example as a regression test.
Can I choose which fields are included?
Use Select fields for profile generation. For a custom column schema, open Test Data Builder. Export formats and batch sizes follow the current plan.
Are generated addresses verified?
Linked locality records provide city, region and available postal information. Street names and house numbers are synthetic. Postal coverage varies and does not prove delivery.