Testing your forms and workflows before deploying to a group of users is always a best practice approach. This will ensure that you catch any mistakes that may occur during creation. In this article, we will talk about a few ways this can be done.

Before sending out a public link, or notifying users that a workflow is live, we suggest testing the workflow by setting each step completer to "The person that starts the Script". Once these changes are locked in, you can grab the public link and test. This allows you to quickly go through each step sequentially to test and evaluate exactly how each user will interact with the process.

Another great way to test workflows is to complete submission in an incognito window. This will not recognize your Script account allowing you to test the form as an outsider user like a parent or staff member. You will have to fill in a first name, last name, and email address to complete the submission. We suggest using test names and your real email address for notifications.

As you go through the forms and steps in your process, keep in mind that you are pretending to use it as one of your parents/staff. This will help you catch any errors or assumptions made during the design process.

If you find any issues with your form/process, make sure to go back through and edit them. It is important that you update the workflow with your changes.

Another set of eyes is always helpful when testing your workflow. Add other users to the testing group if you'd like and repeat the testing process until you have a great form and process to use.

Did this answer your question?