Skip to content
  • There are no suggestions because the search field is empty.

How to Test a Form Before Publishing

Learn how to test a form before publishing it in Smarter Drafter Pro

Before you publish a form to your organisation’s Forms Library, it’s essential to preview it, run tests, and check for any issues. This guide walks you through how to test a form effectively using the built-in Testing tab and a checklist of common review items.

Instructions

1. Use the Preview Button to Spot Layout or Logic Issues

  1. In the Builder, click the Preview button at the top-right of the form editor.
  2. The preview window opens in a new tab.
  3. Use this to check:
    • Field layouts and groupings
    • Logic (e.g. conditional visibility)
    • Formatting and user flow

NOTE: The preview simulates form behaviour but doesn’t generate a document

 

2. Use the Testing Tab for Real Submissions

  1. Ensure that your form has been published.
  2. Click on the Options tab
  3. Select Preview.

  1. Fill in the form as a user would and submit it.

  1. Review the output:
    • Generated document
    • Form submission name
    • Contacts created

 

TIP: You can run multiple test submissions and download the generated documents for review.

 

3. Use the Form Testing Checklist Before You Publish

Review these common areas before publishing:

  • Has the form been created in the appropriate folder?
  • Has the form been named according to your organisation’s naming conventions?
  • Have the fields been separated into sections correctly?
  • Have the sections been split across pages correctly?
  • Do all sections have an alias?
  • Have contact and user mapping been applied?
  • Do repeating sections have the correct settings, limitations and calculations?
  • Are the sections/fields in practical order?
  • Have the correct field types been used?
  • Have the questions been worded appropriately?
  • Are the optional fields correctly set?
  • Are the mandatory fields correctly set?
  • Are any fields displayed that could be hidden – or vice versa? 
  • Are any guidance fields required?
  • Has logic been applied to direct the form sections and fields correctly?
  • Have roles been applied to the appropriate fields?
  • Have all required conditional rules been created?
  • Are any unique replacement rules required to be created or universal rules to be removed?
  • Have the correct templates been attached?
  • Have all required settings been completed?
  • Have you designed the form to provide the best form filler experience?

4. Test Edge Cases

  • Try out incomplete submissions.
  • Add multiple repeating items if applicable (e.g. multiple directors).
  • Submit forms with unusual or unexpected inputs (long names, symbols, no data).
  • Test different combinations of answers that affect conditional visibility or logic.


Tips for Use

  • Always submit at least one test submission before publishing.
  • Use different sets of test data to cover various user scenarios.
  • Remember: test submissions do not appear in the main Submissions tab.
  • While developing a form, open the Preview in a separate tab and keep it running in the background.
    • As you fill in the preview, click Save and Resume to retain answers.
    • Then, as you make updates in the Builder, go back to the preview tab and press F5 to reload the latest form version and continue testing without starting from scratch.

Common Issues & Solutions

  • Issue: I can’t submit the form from preview mode.
  • Solution: Use the Testing tab to complete real submissions. The Preview tab is just for visual checks.
  • Issue: The test document doesn’t reflect my logic correctly.
  • Solution: Check that your fields and conditional logic are correctly configured in the form. Use Preview to confirm behaviour.