china-testdata-generator

1. What format-valid-but-random means

ID numbers pass MOD 11-2, phones use real prefixes, credit codes pass mod 31, cards pass Luhn — they fool format validation, which is exactly the job of test data. But sequences are random: the odds of colliding with a registered number are astronomically small, and nothing is paired with names (this tool deliberately never generates name-number pairs). Bank cards use public payment-gateway test BINs (411111 etc.) that fail in real payment environments by design.

2. Compliance boundaries (read this)

1. Allowed: dev/test environment fill, form-validation integration, teaching demos, replacement data for anonymization drills.
2. Forbidden: impersonating anyone on real services, defeating real-name verification, or feeding phishing/fraud pages — the Cybersecurity Law and PIPL attach clear liability.
3. Gray-line test: if generated data would leave your test environment and touch a real system or a real person, stop.

3. Pair it with the validators

The recommended engineering loop: generate a batch → feed your form → point the form at the same rules this site’s validators use → deliberately corrupt one digit and confirm the validator catches it. The loop surfaces both failure classes — checks too loose (corrupted data passes) and too strict (valid data rejected) — and the latter, in production, locks out real users, which is usually the costlier bug.