Choosing an identity generator
Most test suites need a person before they need anything else, and most bugs hide in the parts of a person that hand-written fixtures leave out — an apostrophe in a surname, a two-line street address, a name written in kanji. Start from the shape of the record your code consumes:
- A whole user row — use the name generator with email and phone switched on. Each row is built around one imaginary person, so
Maria Gómezgetsmaria.gomez@example.com, not a stranger's inbox. - A sign-up or checkout form — the address generator and phone number generator give you country-correct formats, including postcodes that pass a regex and the national phone grouping your formatter has to handle.
- Government identifiers — the SSN & national ID generator computes the check digits for schemes that have them (Brazil's CPF, Canada's SIN, France's INSEE key), and the passport & licence generator adds issue and expiry dates and an ICAO 9303-shaped MRZ line.
- Authentication flows — the username and password generators let you test length limits, character classes and passphrase policies.
What is real and what is not
Wherever a standard reserves a range, the identity generators use it. US phone numbers sit in 555-0100 to 555-0199, the block the North American Numbering Plan keeps for fiction. UK numbers use Ofcom's drama ranges. Email addresses default to example.com, which RFC 2606 guarantees will never deliver mail. US Social Security Numbers use area 900–999, which the SSA never assigns — and the group stays at 01–49, clear of the ranges the IRS uses for real ITINs.
Names are different: they are recombined from common first names and surnames across eight locales, so a generated name can coincide with a real person's. Treat that as chance, and never present a generated identity as belonging to someone.
For the full list of reserved ranges, and the reasoning behind each one, read Reserved ranges for test data.