Testing a form by typing "asdf" into every field gets old fast, and it misses bugs that real-looking data would catch, like a long surname, an accented letter or a plus sign in an email. Here are four ways to fill a form with fake data, from quickest to most repeatable.
Keep a note with one full set: a name, an address, a phone number and an email on a domain you control or on example.com. Paste from it each time. This is fine for a handful of runs, and it breaks down when you need variety.
Libraries such as Faker (for JavaScript, Python and other languages) generate names, addresses, dates and text. They are the right choice for automated tests and seed data, because the output can be fixed with a seed and checked into your test suite.
For manual testing, a form-filling extension saves the copy-and-paste step.
It fills text, email, phone, address, date and number fields, chooses dropdown options and radio buttons, and ticks required checkboxes. Email addresses use example.com, so a test submission cannot reach a real person. Payment, identity and security-code fields are left empty on purpose. See the help page.
Chrome can fill a saved address profile into a form. That works for checking layout, but it uses your real details, so avoid it on a shared test site or a screen recording.
example.com so that a stray email goes nowhere.Check the field's pattern or length rules. Some forms accept only certain phone formats or postcodes for one country.
Custom widgets that are not real select elements may need a click by hand.
Some frameworks reset a field when it receives no input event. Click into the field once and tab out to trigger validation.