About

This utility addresses the critical need for high-fidelity mock data in software development and Quality Assurance (QA). Unlike basic randomizers, this engine prioritizes determinism and semantic validity. By utilizing a seeded Pseudo-Random Number Generator (PRNG), developers can reproduce identical datasets across different environments (Dev, Staging, Prod) by sharing a single seed value.

The generator simulates real-world entropy, creating data that adheres to strict validation rules, such as the Luhn Algorithm for credit cards and valid IBAN checksums. It supports multi-locale injection, ensuring that address formats, phone codes, and name distributions match the target demographic (e.g., US vs. DE).

Designed for stress testing databases and populating UI layouts, the tool imposes a hard limit of 1000 entities per batch to maintain browser performance, while offering bulk export capabilities in JSON, CSV, and SQL dialects.

Formulas

The core determinism relies on the Mulberry32 algorithm, a fast non-cryptographic PRNG. It transforms a seed state s into a random float r in the interval [0, 1).

{

t = s + 0x6D2B79F5r = normt &xor; t → 14

To validate Credit Card numbers, we use the Luhn Algorithm (Modulus 10). For a number with digits d of length n:

S = n∑i=1 {

d_i if i is oddsum_digits2×d_i if i is even

Reference Data

Field Type	Description	Validation / Logic	Example Output
Identity	Full names, gender, DOB	Locale-specific frequency weighted	John von Neumann
Network	Email, IPv4/IPv6, MAC	RFC 5322 compliant emails	192.168.1.1
Finance	Credit Card, IBAN, CVV	Luhn Checksum passed	4532 0156 7890 1234
Location	Address, City, Zip, Geo	Format varies by Locale code	90210, Beverly Hills
System	UUID, Password, User Agent	UUID v4 (Variant 1)	550e8400-e29b...

Frequently Asked Questions

The seed initializes the PRNG state. If you input the string "QA-BATCH-1", the tool will generate the exact same sequence of users every time. This is critical for regression testing where you need predictable data.

No. They are mathematically valid according to the Luhn algorithm (so they pass frontend validation), but they are not registered with any bank and will fail at the payment processor gateway.

Switch to "Custom" mode. Use handlebars syntax like {{firstName}}, {{email}}, or {{uuid}}. The generator will parse your JSON string and replace these tokens with generated data for each record.

Yes. Switch the view to "SQL". The tool generates "INSERT INTO" statements compatible with standard SQL dialects. You can then run this .sql file directly against your database.

While the probability of collision is astronomically low for UUIDs and distinct combinations (Email + Name), small datasets with simple constraints might produce duplicates. Use the UUID field for a guaranteed primary key.