NorthMock · Practical QA workflow
Bulk address generator for QA test data
Generate a small batch of US or Canadian test records, inspect separate address fields, and export the current session as CSV or JSON for forms, fixtures, demos, and staging imports.
What the batch generator produces
Choose a specific US state, Canadian province or territory, or a random North American region. A single action can request 1, 5, 10, or 25 records. For a fixed region, every row retains that two-letter state or province code. Random mode can return a mixture of supported regions.
Each row contains a full address plus separate address line, city or municipality, state or province, and ZIP or postal-code fields. It also includes an independently assembled fictional name, a gravityengine.cc disposable email and inbox link, a local reserved 555-01XX test number, and a real assigned phone prefix whose subscriber digits remain masked.
Form QA
Paste individual fields into checkout, CRM, onboarding, and registration forms to verify labels, required fields, formatting, and responsive layouts.
Fixture preparation
Download JSON when tests need named properties, or CSV when a spreadsheet, import wizard, or database-seeding step expects tabular rows.
Regional regression checks
Keep one region selected to exercise state, province, ZIP, postal-code, and local phone formatting across repeated records.
Disposable verification flows
Open each generated inbox in a separate tab without using a personal email address or changing the original NorthMock mailbox format.
How to create and export a test batch
- Select scope. Choose a state, province, territory, or random-region mode before generating the batch.
- Select quantity. Start with five rows for layout checks; use 10 or 25 only when the test needs variation across multiple records.
- Inspect the first row. The detailed card and map show the first generated result, including its split postal fields and safe phone formats.
- Review the batch table. Confirm region codes, postal formatting, and field lengths before importing the data into another system.
- Copy or download. Copy tab-separated rows, download UTF-8 CSV for a spreadsheet, or download JSON for code and API fixtures.
- Delete after testing. Treat generated rows as temporary fixtures and remove them from staging systems after the test run.
CSV and JSON export fields
The two download formats contain the same named values. CSV is prefixed for UTF-8 spreadsheet compatibility, quotes fields safely, and prefixes formula-like spreadsheet cells; JSON retains exact values in an array of structured objects.
| Field | Meaning | QA use |
|---|---|---|
address_line | Street portion of the selected address | Address line 1 inputs and field-length checks |
locality | US city or Canadian municipality label | City and municipality validation |
region_code | Two-letter state, province, or territory code | Dropdowns and subdivision rules |
postal_code | ZIP, ZIP+4, or Canadian A1A 1A1 value | Postal-field formatting and parsing |
full_address | Complete display address from the regional pool | Single-line previews and map tests |
safe_phone_national | Local area code with reserved 555-01XX line | Phone masks without completing a subscriber number |
safe_phone_e164 | Reserved phone in strict +1 E.164 form | International phone normalization |
assigned_prefix_masked | Officially assigned NPA-NXX with XXXX subscriber digits | Prefix-aware UI without producing a real full number |
email and inbox_url | Disposable mailbox address and matching new-tab inbox URL | Email confirmation and inbox-link tests |
When to use CSV, JSON, or copy batch
Use CSV for tabular imports
CSV works well for spreadsheets, CRM import previews, database seed templates, and QA evidence that reviewers need to scan row by row.
Use JSON for automated fixtures
JSON preserves field names and is convenient for frontend mocks, API contract tests, end-to-end fixtures, and development scripts.
Use copy batch for quick checks
The copy action creates tab-separated text that can be pasted directly into a spreadsheet without creating a local file.
Use one record for manual forms
A single record keeps the full detail card, copy buttons, disposable inbox link, and an automatically loaded map preview without adding a batch table.
Quality, privacy, and usage limits
- The 25-row limit keeps the interactive tool responsive and discourages unnecessary collection of location records; the public API remains rate limited.
- Export files are created locally in the browser. NorthMock does not upload an export file or provide persistent batch history.
- Addresses may describe real places, but all contact components are assembled independently and must not be treated as a person who lives at that location.
- Use generated records only for legitimate development, education, demos, and sandbox testing—not mail delivery, residency claims, fraud, impersonation, or identity verification.
- Review the NorthMock data methodology, source boundaries, and validation controls before using exports in a shared test environment.
Need a fixed region? Browse the US address generators by state or the Canadian address generators by province and territory.