Jotform test form before you share it

When you test your own form you already know the answers, the order of the questions and which answer opens the next one. A stranger reads the first question and guesses. A question that appears after a yes can block the submit if it is required and the visitor did not know to answer it. The public link can also behave differently from the edit page, since a form can be closed or limited, and you only see that from a logged-out browser. On a phone, the keyboard can cover the field being typed in. The edit page shows none of this.

• Open the public link in a private window, not from the edit page, and confirm it loads without a login.
• Note every question that appears under a condition, and fill each answer that opens one.
• Press Submit with a required field empty and read the error the visitor sees.
• Check the thank-you step after a complete submit, including any address it sends the visitor to.
• On a phone, type into the last field and confirm the keyboard does not hide the Submit button.

A stranger taps the link and sees the first question with no context, sometimes on a phone with the keyboard open before the page has finished loading. They answer what they can, skip what they cannot, and press Next or Submit when they think they are done. If the form asks for something they do not have, some leave rather than guess. The owner never sees that moment, because the owner opens the form already knowing which answers are safe to give.

The wrong way is to open the edit page, fill in the answers you know, and read the thank-you screen. That proves one path works, and it is the path you designed. The right way is to open the public link in a private window, list every answer that opens a new question, and fill each one on its own run. Count the routes on paper before you start, since each answer that opens a different question adds one more.

The thank-you step belongs in the test too. A stranger who reaches it believes they have finished, so check the words it shows and the address it sends them to. A thank-you page behind a login, or one that sends them back to the start, is a dead end the owner would not see from the edit page, because the owner is already logged in there.

A simulated run opens the public link, fills the form, presses Submit, and records the step where it stopped. Each simulated visitor takes one route through the form, so give each route its own run. The report gives you the step, a screenshot, and any script error or failed request recorded there. The run sees only the public page, so it cannot show whether the entry reached your inbox or spreadsheet. If the form emails a confirmation to the person who filled it in, the simulated visitor's inbox can receive it, and the report shows that step.

Forms change after you share them. A new question, a changed condition or a moved required mark can block a path that worked last month. Run the same paths again after each change, from the public link on a phone, and compare the step where each simulated visitor stopped with the run before.