Form Test Data Generator
Generate valid, invalid, boundary, and edge-case data for common forms — then copy it as a table, JSON, CSV, or framework fixture.
Runs 100% client-sideOn this page4 sections
| Field | Valid value | More examples |
|---|---|---|
| Name | Anne-Marie O'Neill | José García · Wei Chen |
qa.user@example.com | qa+test@example.com · first.last@example.co.uk | |
| Username | qa_user01 | test.engineer · jdoe |
| Password | Passw0rd!23 | Tr0ub4dor&3 |
| Date of birth | 1990-05-14 | 2001-12-31 |
HOW TO USE
- 01Pick a form preset — registration, login, checkout, profile, contact, or address.
- 02Choose a data mode: valid, invalid, boundary, special characters, unicode, empty, whitespace, or long input.
- 03Read the generated values in the table, with extra example values per field.
- 04Switch the output format to JSON, CSV, a Playwright/Cypress fixture, or a REST Assured body and copy it.
Try it
Preset = Registration, Mode = Invalid → see why 'qa@example' and a 3-char password should be rejected.WHEN TO USE
Use this when you need more than happy-path data. It targets the values that expose validation, boundary, formatting, encoding, and localisation bugs — invalid emails, boundary-length names, unicode and emoji, whitespace, and long inputs — organised by the form you are testing. Unlike a realistic-data mock generator, the point here is the awkward edge cases. Use synthetic data only and never enter real PII or payment credentials.
WHAT BUGS THIS FINDS
Weak input validation
Invalid emails, negative amounts, and malformed postcodes reveal fields that accept values they should reject.
Boundary and length bugs
Minimum/maximum length names, passwords, and amounts expose off-by-one and truncation errors.
Encoding and localisation bugs
Unicode, emoji, accents, and right-to-left text surface rendering, storage, and normalisation issues.
QA USE CASES
Negative-path manual testing
Run the invalid and boundary sets against a form to confirm error handling is correct.
Automation fixtures
Copy a Playwright or Cypress fixture of valid and invalid users straight into your test suite.
API request bodies
Generate a REST Assured or JSON body to drive negative API tests.