Form testing and sign off: what is involved and what you need to do

You need to test your form during the development process. If your form is to go into our Formtools database (ability to download submissions as excel file etc) it requires additional testing.

Testing is when you make sure the form is doing everything you expect it to. When the form meets your functional requirements you must sign off so development can continue.

Stage 1: functional testing - all forms require at least this testing

The Web Team develops your form according to your requirements. The developer tests the form, fixes any issues and passes it onto you to test and sign off.

Step A - Your functional testing should include:

  • Are the labels clear and understandable?
  • Do the labels on the form fields match the output?
  • Are text boxes the right size? Can you easily read the content as you type? Can the text box hold the likely amount of text someone would enter?
  • Where a field is compulsory, if you do not complete it does the form behave as you expect?
  • Where people must select an option, have you included all the options needed?
  • Does your form have all the fields needed?
  • You should test several combinations of options you are likely to receive from people using your form
  • Test any other functions specific to your form

This is where you need to identify any changes required to form function.

This is most important for forms stored in our Formtools database. If you miss something and later decide to make a change to function eg decide to add another field, we may not be able to meet your 'go live' date.

Step B - Sign off your functional testing

Once you are happy with the function of your form you must sign off so development can proceed to the next stage.

Sign off is an email to the developer working on your form to tell them you are happy with the form and development can proceed.

For example:

"Many thanks (having tested a few options) this registration form meets my needs.
Please accept this as a sign-off for the next stage to proceed".

Until you sign off we cannot continue to develop your form.

Stage 2: final testing - forms that are in the Formtools database

If your form will be stored in our Formtools database (ability to download submissions as an excel file etc) you have further testing to do.

The person developing your form will send you an email with the information your need to access the Formtools database.

Step A: Your final acceptance testing should include:

Do the compulsory fields still behave as you expected?

Is the form function unchanged from your earlier testing? (eg are the text fields large enough etc)

Can you log into Formtools and view the test submissions? (details are emailed to you)

Check the email you receive as the administrator of the form and the email the person filling in the form receive makes sense, including the

email subject line. (Remember, once the form is live you will only receive the administrator email)

Step B: Sign off your final acceptance testing

When you are happy the form meets your needs you must sign off before it can go live.

Sign off is an email to the developer working on your form to tell them you are happy with the form and it can now go live.

For example:

"Many thanks (having tested a few options) this registration form meets my needs.
Please accept this as final sign off. The form is complete and can now go live.

Until you sign off we cannot continue to develop your form and it cannot go live.

Stage 3: Final touches by the developer

Remove any extra email addresses from Formtools that were used during testing.

The form is linked and available for people to fill in. The form is handed back to you (or the person in your department who will administer it).