How Test Nexus Generates Country-Specific Test Data

You’re testing user registration for a Brazilian fintech app. You need a complete profile: name, CPF number, address, phone number, email. So you go to a CPF generator website, get a valid number — 123.456.789-09 — with correct check digits. Great. Now you need a name. You type “John Smith” because you don’t know common Brazilian names. The address? You Google “São Paulo address format,” find something on Stack Overflow, and cobble together “Rua Qualquer, 123, São Paulo.” The phone number? You guess it’s +55 followed by… 11 digits? 10? You’re not sure if São Paulo uses area code 11 or 21.

You enter the data. The registration form rejects it. The postal code 01000-000 doesn’t correspond to the neighborhood you entered. The phone number format is wrong — São Paulo mobile numbers are +55 11 9XXXX-XXXX (nine digits after the area code since 2012, not eight). And “John Smith” sailed through, but now your test data looks nothing like what real Brazilian users would enter, which means your edge case coverage is meaningless.

You just spent 25 minutes researching Brazilian naming conventions, CEP postal code ranges, and phone number formatting — not because you’re learning something useful for your career, but because you need fake data that looks real enough to pass both validation logic AND realistic usage patterns.

This is the gap between structurally valid and country-appropriate test data. A basic generator gives you the right number of digits with correct check sums. DataHub gives you a complete identity with culturally appropriate names, addresses in the correct local format, phone numbers with the right area codes, and national IDs that pass real validation algorithms — all generated locally on your device, instantly, and for free.

What DataHub Actually Generates

DataHub generates complete test profiles using bundled country data and deterministic algorithms. No internet connection required. No tokens consumed. Every profile is generated locally on your device.

When you select a country and tap Generate, here’s what you get:

Culturally Appropriate Names (~190 Countries)

DataHub ships with a comprehensive name database covering approximately 190 countries, with 50 first names, 50 middle names, and 50 last names per country — producing thousands of unique combinations. When you generate a Brazilian profile, you get names like “Miguel Eduardo Silva” or “Alice Vitoria Santos” — not “John Smith.” When you generate a Japanese profile, you get “Tanaka Yuki” or “Suzuki Haruto.” The names are drawn from country-specific lists that reflect actual naming conventions.

This matters for testing because:

• Character handling — Brazilian names include accents (ã, é, ç), Japanese names may include kanji, Arabic names include characters your ASCII-only test data never exercises
• Name length — Names with first, middle, and last name fields (like “Miguel Eduardo Silva”) stress UI layouts and database schemas that “John Smith” never will
• Form field mapping — Some cultures use single names, others use first-middle-last conventions. Your form’s name parsing logic needs to handle the variation

Addresses in Local Format (~190 Countries)

Addresses follow each country’s conventions — street naming patterns, unit numbering, postal code structure, and line ordering. A Brazilian address uses “Rua/Avenida” prefixes with neighborhood and CEP. An Australian address uses “Unit X, Y Street” format with suburb and postcode. A Japanese address follows the prefecture/city/ward/chome structure.

Phone Numbers with Correct Structure

Phone numbers are generated in E.164 format and match each country’s actual numbering plan — correct country code, valid area code, and proper digit count:

• Brazil: +5511 9XXXXXXXX — São Paulo mobile with 9-digit format (the ninth digit was added in 2012)
• Australia: +614XXXXXXXX — mobile with the standard 04 prefix
• Romania: +407XXXXXXXX — mobile with 07 prefix
• Chile: +569XXXXXXXX — all Chilean mobiles use area code 9

Area codes follow each country’s real numbering plan. Brazilian profiles get valid area codes (e.g., 11 for São Paulo, 21 for Rio de Janeiro, 61 for Brasília). Phone numbers are validated using Google’s libphonenumber library to ensure they conform to each country’s numbering rules.

National IDs with Valid Check Digits (38 Countries)

This is where DataHub goes beyond what most generators offer. National ID numbers aren’t just random digits — they’re generated using the actual check digit algorithms your app’s backend validates against:

• Brazil CPF: 11 digits where the last two are computed using modular arithmetic with weights of 10→2 and 11→2
• Spain DNI: 8 digits plus a check letter calculated with modulo 23 from the sequence TRWAGMYFPDXBNJZSQVHLCKE
• Chile RUT: 8 digits plus a check digit (0–9 or K) calculated with modulo 11
• Australia TFN: 9 digits with a weighted checksum (weights 1,4,3,7,5,8,6,9,10) that must be divisible by 11
• India Aadhaar, US SSN, Germany Tax ID, Poland PESEL, and 33 more

Some countries have multiple national IDs — the US generates both SSN and EIN, Brazil generates both CPF and CNPJ, and Spain generates DNI, NIF, and NIE — giving you coverage across different document types.

When your app validates a CPF using the standard algorithm, DataHub-generated numbers pass. That means your test covers the actual validation path, not just “does the field accept 11 digits.”

Payment Cards (5 Brands)

Visa, Mastercard, Amex, JCB, and UnionPay — each generated with valid BIN prefix, correct length, Luhn-valid check digit, future expiry date, and CVV. Card brand availability varies by country (e.g., JCB appears for Japan, UnionPay for China, Mastercard and Amex for the US).

Banking Identifiers

DataHub also generates country-specific banking codes for fintech testing: IBAN (12 European countries + Turkey), ABA Routing Number (US), Sort Code (UK), BLZ (Germany), BSB (Australia), IFSC (India), Transit Number (Canada), and CLABE (Mexico). Each follows the correct format and structure for its country.

Additional Fields

Every profile also includes: email (derived from name), username, password (three strength levels — 8-character simple, 12-character medium, or 16-character strong with special characters), gender, marital status, ethnicity, nationality, and date of birth (age 18–65).

Looking for Individual Validation or More Card Brands?

While DataHub focuses on complete profiles, Test Nexus also includes a standalone IDs & Cards tool for individual data generation and validation. Use it when you need to:

• Validate an existing ID or card number with detailed error messages explaining exactly what’s wrong.
• Generate individual values for any of 56 supported types.
• Access more card brands, including Discover, Diners Club, and Maestro.
• Save favorites with custom labels for repeated testing.

See Post #07 for more on how these individual validation tools differ from the DataHub batch workflow.

Country-Specific Examples

To illustrate what “country-appropriate” means in practice, here’s what DataHub generates for three different countries:

Brazil

Name:    Lucas Eduardo Silva
CPF:     382.916.547-20
Address: SQS 308 Bloco C, Asa Sul
         Brasília, Distrito Federal 70352-030
Phone:   +556198742315
Email:   LucasEduardo-BR-test-4523-@mailinator.cc
Card:    Visa 4532-0151-1283-0366 (Luhn-valid)

The name uses culturally appropriate Brazilian first, middle, and last names from the bundled database. The address uses Brasilia’s sector-quadra-bloco format with a valid CEP postal code. The phone number uses the correct Brazilian mobile format with a valid area code in E.164 format. The CPF passes the standard check digit algorithm.

Japan

Name:    Tanaka Yuki
Address: 1-2-3 Shibuya, Tokyo 150-0002
Phone:   +819038472951
Card:    JCB 3530-1113-3330-0000 (Luhn-valid)
My Number: 1234-5678-9012

Japanese names from the bundled database, address in the Japanese format, mobile number with the common 090 prefix, and a JCB card (the domestic Japanese card brand) alongside the My Number national ID.

Australia

Name:     James McPherson
TFN:      876 543 210
Address:  Unit 7, 42 Marcus Clarke Street
          Canberra, ACT 2601
Phone:    +61438291574
Card:     Visa 4111-1111-1111-1111 (Luhn-valid)
BSB:      062-000

An Australian name, a Tax File Number, an address in the standard Australian format with a valid postcode from the bundled database, a mobile number with the 04 prefix in E.164 format, and a BSB banking code.

Batch Generation

Single-profile generation is useful for quick tests. But when you need to seed a staging database or run load tests, DataHub handles batch generation:

1. Select your country
2. Set the quantity — choose from 10 (default), 20, or 50 profiles per batch
3. Generate — complete profiles with name, address, phone, email, password, and all available IDs for the selected country, created in seconds on-device

Every profile in the batch is unique. Names, addresses, phone numbers, and ID numbers are all different. Check digits are computed for every ID. Phone numbers follow the correct country format. Postal codes use valid regional ranges. No row-by-row debugging when you import the CSV.

Export Options

DataHub exports to four formats:

• JSON — Structured data with nested objects. Best for API testing, Postman collections, NoSQL seeding, and JavaScript/Python scripts
• CSV — Flat tabular data. Best for SQL database seeding (COPY or LOAD DATA INFILE), spreadsheet review, and data pipeline tools
• XML — For systems that expect XML input or SOAP-based test scenarios
• TSV — Tab-separated values for quick spreadsheet imports and shell script processing

Example: Seeding a Staging Database

Generate 50 Brazilian profiles → Export as CSV → Upload via SFTP (using Test Nexus Terminal) → Import with psql COPY → 50 rows with valid CPFs, correctly formatted phone numbers, and properly structured addresses. First-run success because every row was validated before it left DataHub.

How DataHub Compares to Online Generators

Integration with Other Test Nexus Modules

The profiles generated by DataHub aren’t isolated data. They flow into the rest of the Test Nexus platform:

→ AI Custom Forms + Autofill: DataHub profiles can feed into the Autofill system. The Autofill framework injects DataHub-generated data directly into your app’s form fields — zero copy-paste across apps. For domain-specific fields that DataHub doesn’t cover (property descriptions, medical records, recipe ingredients), AI Custom Forms uses Gemini AI to generate contextually appropriate data for any schema you define. See Post #05 for the full guide.

→ Mock Location: When a profile includes a city address, you can set Mock Location to coordinates matching that city. Your GPS matches the test identity’s location.

→ Deep Inspector: If a crash occurs while testing with a DataHub-generated profile, Deep Inspector captures the full stack trace and device state automatically. Export the crash data alongside the profile to give your team both the error and the exact input that triggered it.

→ Company Profiles: Beyond personal identities, DataHub also generates B2B company profiles — 16 fields including company name, industry, size, annual revenue, ownership type, headquarters, and more. Useful for testing business-facing forms and CRM applications.

→ Export: All profiles export to JSON, CSV, XML, and TSV formats, compatible with Postman collections, database seed scripts, and automated test frameworks. You can export all profiles or filter by country and search query before exporting.

Every generated profile is stored in AES-256 encrypted local databases on your device, and never transmitted to any server.

Get Started

DataHub is available immediately after installing Test Nexus. No tokens required. No internet connection needed.

1. Open DataHub → Select a country
2. Generate — Review the profile, copy individual fields or export the full profile
3. Batch mode — Set quantity, generate complete profiles, and export as JSON, CSV, XML, or TSV

New Test Nexus accounts include 20,000 free tokens for AI-powered features like Custom Forms. DataHub profile generation is completely free and doesn’t consume any tokens.

🚀 Generate Your First Country-Specific Profile Install Test Nexus, open DataHub, select a country, and see the difference between “random digits” and “test data that passes validation.” Download Test Nexus →

What’s Next

• Post #03 — Mock Location Made Easy: setup, multi-waypoint routes, speed profiles, and Google Maps integration
• Post #04 — Deep Inspector: automatic crash capture without ADB, stack trace export, and writing effective bug reports from the data