Test the complete path a visitor will use, from opening the published page to receiving the response you configured. A form that looks correct in the builder still needs a real-page check.
Prepare a controlled test
- Save the form and check that its status and availability permit the intended visitor to use it.
- Review Confirmations and Notifications. Use a recipient you control for any deliberate email test.
- Embed the form on a test page and save that page.
- Use clearly identifiable sample answers so you can find the resulting entry.
A submitted test can send emails or run add-ons. Review enabled notifications and integrations first. Submitting the saved Preview creates a real entry and runs configured actions too; it is not a dry run. The separate Appearance preview is read-only. Also test the embedded page as a visitor because its theme, access and caching context can differ.
Check the page as a visitor
Open the embedded page in a signed-out or private browser window. Confirm that the page itself is public and that the expected questions, labels, descriptions and submit button appear. If the form requires login, check the signed-out message and then the signed-in experience instead.
Check a narrow phone-sized view as well as desktop. Read the instructions at the size visitors will see them. Use the keyboard to reach fields, choices and navigation buttons.
Test validation and alternate paths
Try submitting with a required answer missing. Enter an invalid email address, then correct it. If the form has limits, test values just outside and inside those limits. Make sure messages explain the correction without losing the other answers.
Where applicable, change answers that control conditional questions, move forward and back through pages, add and remove a Repeater row, or choose a file of an allowed type. For a calculation, compare the result with a simple example you can calculate yourself.
Use the CAPTCHA provider's configured verification where the form includes CAPTCHA. A missing credential or failed verification should be resolved before relying on the form.
Make a successful submission
Complete the form with your sample answers and submit it once. Confirm that the processing state finishes and the expected confirmation appears. A Message, Page or URL response should match the form's configured confirmation.
Go to Logical Forms → Entries, choose the form and open the new entry. Compare the saved answers with what you submitted. Check structured fields, repeated rows and file links where your form uses them.
Check email separately
A successful on-page confirmation and a saved entry do not by themselves prove email delivery. If an enabled notification is part of your test, check its recipient inbox and spam folder, then inspect the entry's action or notification status.
Background sending can complete after the visitor sees the confirmation. A failure or uncertain send needs investigation before resending, since a resend may produce a duplicate message. Check the configured sending mode and your website's mail delivery setup.
Finish the check
Remove or clearly identify temporary test destinations, check your final notification recipients, and verify the intended published page link. Keep a short record of what you tested and which sample entry proves it.
Return to the first-form walkthrough for the basic setup, or the embedding guide if the form is missing from the page.
