THE GENORY TOOLKIT

Synthetic Test Data Generators

Choose a complete profile for a form, a custom schema for an import, or one field for a focused check. Generated data helps exercise your software; it does not define which real-world records are valid.

Tools in this category

Search all tools →

Test Data Builder

Build custom datasets with names, test emails, numbers, dates and your own columns.

Data

Card format test data

Seven card networks with Luhn-valid numbers, expiry dates and security codes.

Data

BIN Search

Look up the network format of a 6- or 8-digit BIN prefix in your browser.

Data

BIN Generator

Generate synthetic card samples from a fixed BIN prefix, with expiry dates and security codes.

Data

Test Data Generator

A complete synthetic profile, ready for your next test.

Data

Name generator

Localized names in Latin script for interfaces and test fixtures.

Data

Address generator

Street, city and postal formats for your forms.

Data

Phone generator

Phone format samples for localization testing.

Data

IBAN Generator

Generate synthetic IBANs for testing across 89 country formats, with format and checksum checks.

Data

Which tool fits your task?

A complete profile

Test Data Generator keeps related names and contact fields together. Select a country and read locality coverage before using the address in a test.

Your own columns

Test Data Builder is for a deliberate schema. Name each column, choose a format and test a small export before creating a larger batch.

A focused field

Name, address and phone tools help isolate a single input. Country guides suggest additional editorial fixtures beyond the generator’s Latin-script output.

Banking and card formats

IBAN, card and BIN tools describe checksums and reference coverage. Use provider-issued sandbox credentials when testing actual payment-provider workflows.

A useful workflow

01
Start with one representative record and document the expected result.
02
Choose /generate for a profile or the builder for a custom schema.
03
Test copying and round trips before scaling; exports, batches and API access depend on your plan.

Worked example

Import contract (illustrative, not generated output)
columns: country_code, postal_code, display_name
postal_code: store as text
expected: export → import preserves the original values
coverage: keep the generator’s quality note alongside the fixture

Guides for this task

All guides →