Test Data Generator

What Is a Test Data Generator?

A test data generator produces realistic, correctly-formatted fake records in bulk — names, addresses, emails, phone numbers — for seeding a test database, populating a QA fixture, or load-testing a form. It's the developer-focused end of the same idea as a fake identity generator: instead of one identity at a time for manual testing, you generate up to 100 in a single batch and export them directly in the format your pipeline actually consumes.

How to Use the Test Data Generator

1. Choose a country, gender, and age range, or leave them on "Any" for varied data
2. Set the batch size (up to 100 records)
3. Enter a seed if this test data needs to be reproducible across CI runs or across a team
4. Click Generate
5. Export as CSV, JSON, or a ready-to-run SQL file with CREATE TABLE and INSERT statements

Export Formats

Each record includes name, address, email, phone, job, and account fields. Depending on what you're building, export as:

• CSV — for spreadsheet review or importing into tools that expect tabular data
• JSON — for feeding directly into API tests or JavaScript fixtures
• SQL — a ready-to-run CREATE TABLE plus INSERT statements, for seeding a database in one step

A single JSON record looks like this:

{
  "fullName": "Sarah Mitchell",
  "email": "sarah.mitchell42@example.com",
  "phone": "+44 7700 900123",
  "city": "Manchester",
  "country": "United Kingdom"
}

And as SQL:

CREATE TABLE IF NOT EXISTS identities (
  full_name VARCHAR(100), email VARCHAR(150),
  phone VARCHAR(30), city VARCHAR(100), country VARCHAR(60)
);
INSERT INTO identities VALUES
  ('Sarah Mitchell', 'sarah.mitchell42@example.com',
   '+44 7700 900123', 'Manchester', 'United Kingdom');

Reproducible Test Data with Seeds

Randomly-generated test data has one real drawback: when a test fails, the exact data that caused it is gone by the next run. Enter any text into the Seed field before generating, and that exact seed always reproduces the exact same batch — useful when a flaky-looking CI failure needs to be reproduced locally, or when a fixture needs to stay identical across a whole team. Leave it blank for a random batch; the tool shows you the seed it used afterward so you can save and reuse it later.

Related Tools

Pair this with a UUID Generator for unique primary keys, a JSON Formatter to validate exported fixtures before committing them, or the full Fake Name & Identity Generator if you need the avatar and per-identity card view rather than a bulk export.