Test Data Form Filler: Fake Data for Web Forms in Chrome
Anyone who builds or tests forms knows the routine: open the signup page on staging, type test, test@test.com, 123, submit, watch the validation complain, type it all again with a real-looking date, submit again. Twenty times a day. It is slow, and worse, "test test test" does not exercise the form the way a real person would.
FillWise, a Chrome extension we build, has a mode for exactly this: one switch, one click, and every empty field on the page gets a believable value. This guide covers what it generates, what it deliberately skips and where a different tool is the better choice. For Google Forms in particular, see the Google Forms guide, which also covers what Google's own controls allow.
Why typing test data wastes more than time
- Validation needs real formats. An email field wants an address, a phone field wants digits, a date field wants a date in its own format. Junk input tests only the error messages.
- Data has to agree with itself. A name in one field and an unrelated email in another hides bugs in anything that compares or displays them together.
- Unique fields block repeats. Sign up twice with the same email and the second attempt fails before it reaches the part you are testing.
- Long forms make everyone cut corners. On an onboarding form with thirty fields, people fill the required ones and never see how the optional ones behave.
How the random data mode works
- Install FillWise and sign in with Google or a one-time email code.
- Open the form you are testing: production, staging, or a local build on localhost.
- In the side panel, under Advanced settings, switch on Fill empty fields with random data (free).
- Leave the text box empty and press Fill form.
- Submit, reload, and fill again: every fill makes up a new person.
With nothing pasted and no file attached, the values are generated inside the extension itself. The fill makes no request to our server or to any AI and does not spend anything from your balance.
What it fills
Each fill invents one consistent person, so the fields agree with each other:
| Field | What goes in |
|---|---|
| First, middle, last and full name | Names from a built-in list |
| Built from the name, for example first.last plus two digits, at gmail.com | |
| Username | Built from the same name |
| Phone | A US-format number, +1 and ten digits |
| Address, city, state, ZIP | Street number and name, a city, a US state, five digits |
| Country, nationality | One of eight countries |
| Company, job title | From built-in lists |
| Password | A test password with a capital letter, digits and a symbol |
| Website | https://example.com |
| Date of birth | Someone between 21 and 55 years old |
| Document issue and expiry dates | Issued in the last five years, expiring in the next five |
| Arrival, departure, start and end dates | A few weeks to six months ahead |
| Number fields | Within the field's own minimum and maximum |
| Dropdowns | One of the real options, never the "Select..." placeholder |
| Radio buttons | The first option in each group (a random one in PDF forms) |
| Checkboxes | Consent and "I agree" boxes and required ones ticked, the rest at random |
| Message and comment boxes | A short neutral sentence |
| Any other text field | The words "Test data" |
A date picker gets a proper date. A date typed into a plain text field goes in day first, such as 31.12.1990.
What it skips on purpose
- Payment and sensitive numbers. Card numbers, CVV and security codes, IBAN, SWIFT and social security numbers are left empty. Use your payment provider's own test card numbers for checkout tests.
- File uploads, hidden fields and buttons. Nothing is uploaded and nothing is clicked.
- Anything you already typed. A text field or dropdown that has a value keeps it. That is the easy way to control one field: type your own test inbox into the email field first, then fill the rest with random data.
Mixing real values and random ones
Sometimes a few values must be exact: a promo code, an invite token, the email of a test account. Paste them into the panel with random data switched on and press Fill form. The AI keeps your values and invents everything else to match the form.
This mixed fill goes through the AI, so it is a normal fill: it spends one fill from your balance, and the field labels and your pasted text are sent to our server for that one fill. Saved templates count as pasted text too, so switch them off if you want a random-only fill to stay free. Typing the exact values straight into the form and then running a random-only fill gives the same result without spending anything.
PDF forms
The same mode works on fillable PDF forms opened in Chrome: text fields, checkboxes, radio groups and dropdowns get generated values, and text is cut to each field's character limit. Flat PDFs, the ones without real fields, need real data; random mode stops there with a message that the PDF has no fillable fields.
Where another tool fits better
FillWise is built for a person sitting in front of a form: exploratory testing, a demo, a screenshot, a quick check after a deploy. It is not a test framework.
- Automated end-to-end tests belong in Playwright, Cypress or a similar framework, with test data from a fake-data library such as Faker. Those run in CI without anyone clicking.
- Load testing needs generated requests, not a browser extension.
- Large data sets for a database come from a seeding script.
What to check by hand
- Emails go to real domains. Generated addresses are at gmail.com and can belong to real people. If your form sends emails, type your own test inbox into the email field first.
- Values are US-style, dates are not. Phone numbers, states and ZIP codes follow US formats, but a date in a text field goes in day first. On a form that wants mm/dd/yyyy, type the dates yourself.
- Names repeat. They come from a short built-in list. On a form that needs a unique email, a repeat is possible after many fills; type a fresh one if the form refuses.
- Custom-drawn controls. Some form builders draw their own choice buttons with no real input underneath. Those stay as they are.
Privacy
A random-only fill is made inside your browser: no form data and no field labels go to our server or to any AI. As after any fill, if you then change a filled field by hand, the extension reports which field you changed, by its name only, never the value. Mixed fills, with text pasted or a template on, send the field labels and that text for one fill, and nothing is stored afterwards. The details are on the privacy and data security page. Do not paste real customers' personal data into a form you are only testing.
Pricing
Random-only fills are free and do not spend fills, on any plan. Fills with your own data are counted as usual: the free plan has 20 fills to start and 5 a week after that, with no card, and paid plans start at $19 for 100 fills a month, on the pricing section.
FAQ
Is random data really free? Yes. It is generated in the extension, so there is no AI call to pay for.
Does it submit the form? No. It fills, you submit. That way you can test the submit and its validation yourself.
Does it work on localhost and staging sites? Yes. It works on regular web pages, local builds on localhost included.
Can I choose the country or language of the fake data? No. Values follow US formats. Paste the values you need instead.
Can it replace my automated tests? No. It speeds up manual testing; automated tests still need a test framework.
Get started
Install FillWise, open the form you are testing, switch on random data and press Fill form.