In order to test your site you will first need to add a new user to your site that you wish to use for testing.
Once you have created all of the processes in your site you can use test users to in order to test the following:
- General User Experience
- General Workflow Movement
This will help to ensure that your site is working as desired. You can use it to test how the submissions may move through your workflow from the application stage to reviewer stages. It is also useful for testing triggers to ensure they are activating correctly.
Warning: Your test user will follow the same rules as given to your real users. For example, any deadlines, start dates or visibility settings placed on tasks will also apply to this user.
In regards to emails, test users are useful for testing deliverability as well as Piping Variables. You will notice when setting up your emails there will be a Send Test Email button, this is solely for the purpose of testing deliverability. You will need to use a test or real user in order to test the piping variables contained within the email as the variables in the email need to be able to pull from live user or submission data.
Testing Submissions while Locking out Real Users
In certain circumstances your site is open and you need to test the workflow however you don't want real users to be able to log-in and complete the submission.
In order to be able to create and Edit submissions the Submissions Quick Control will need to be unlocked. In order to test without allowing users to access the tasks you will need to temporarily unlock submissions. Once you are done testing you can then Lock submissions if you wish to restrict users from editing existing submissions.
For further information on the Dashboard Controls please see the following documentation: Dashboard Quick Controls