Testing your form

You'll want to make sure your form is thoroughly tested before releasing it to the public.

On this page:

• The 3 types of testing
• Testing your form while you build it
• Testing your form with the client
• Testing your form with users

The 3 types of testing

Testing your form can be described in 3 categories:

• Build testing occurs while you build your form
• Acceptance testing occurs with the client pre-release
• User testing occurs either pre- or post-release

The tools and steps are different in each type of testing.

Testing your form while you build it

As you build your form, you'll want to check out how it's looking and working. You can test your form and most interactions within the form editor.

To test your form in the editor:

• Click the "Test" button in the button bar

The Form Preview window will open with a representation of your form. Under your form display is a section called "Console". This is where any errors detected with your various formulas or calcuations are identified.

In this preview you can test things like:

• Layout and presentation
• Visibility settings and interactions
• Calculations and combinations
• Validation settings and processing

Click the "Test PDF" button to see what your PDF will look like. (You can also access the PDF test directly using the arrow button on the right of the "Test" button.)

There are a few things to note about the Form Preview:

• It currently uses a different set of styles than CMS Lite, so:
  • It's not an accurate representation of final appearance
  • Required fields are marked with a red star
  • The word "optional" appears after every label, even if it's not
• You can't test things that need the Form Runner server such as:
  • Emails
  • Messages
  • Submission to an API

You can test final appearance and server functions through CMS Lite when preparing for acceptance testing with your client.

For additional information see:

• Orbeon Forms | Formulas console
• Orbeon Forms | Formulas inspector

Testing your form with the client

In order for the client business or program area to review and test the form, it will need to be available to them in CMS Lite.

To learn how to do this, see:

• How publishing works in CMS Forms
• Creating a CMS Lite form page

The purpose of this testing is for the client to confirm that business and technical requirements have been met and to approve its release to the public.

What needs to be tested, how carefully, and by how many people will depend on the type of form and whether it's new or a revision.

Generally, your clients will need to carefully check:

• The text of all labels, hints, help, instructions and other body text.
• All possible variations of a form's flow and interactivity through visibility
• The data presented in any testing fields
• The results of any calculations or combinations
• The subject, body and attachments of all emails sent
• The content of the success message, if custom
• The content and presentation of the PDF and XML files

Feel free to the use the above list as a starting point for creating a checklist for client testing and reviews.

Once the client has confirmed that the form looks and works the way it should, you can:

• Test it with users or
• Release it to the public

Testing your form with users

You may want to conduct user testing when:

• Your form is completely new, not just an online version of a pre-existing form
• Is a considerable departure in style or content from a previous form
• To validate the design as part of a service design project

In these contexts, a user can be:

• Government employees not familiar with your form or program
• Selected members of the intended audience
• Members of the general public who may or may not be familiar with the form or program

You can also choose to perform user testing:

• Formally or informally
• Before or after release to the public

Example approaches you can take include:

• Provide internal government users with a link to the QA version of the form in CMS Lite
• Release the form to the public without announcing or linking to it and inviting members of the intended audience or general public to test the form (known as a "soft launch")
  • You can also use this method for A/B testing
• Release the form to the public normally and provide opportunities for gathering feedback by:
  • Monitoring incoming questions related to the form or process
  • Watching for data errors that could suggest a question or options aren't clear
  • Inviting people to provide feedback in the form itself or through a separate one
  • Arranging one or more post-release surveys

For more information, guidance and support conducting tests, research and surveys, see the following web pages:

• Service experience and digital delivery | Citizen engagement
• Service experience and digital delivery | Service and content design