Once you've configured your Incident Types, it is critical that you conduct internal testing to ensure that everything is functioning as you expect. This is a great opportunity to make any necessary changes involving your incident flow process, visibility at each step, and the details included in the email notifications. Conducting internal testing can help your team gain confidence to launch the Incident Management process within your organization. If you have not yet configured your Incident Types, please refer to the Incident Types article to get started.
Steps to Conducting Internal Testing of Incident Types
Configure Incident Types in Sandbox - Consider configuring your incident types in sandbox.foodlogiq.com to allow for testing in that environment. You can also test in the Production environment and remove when complete by enabling the deletion feature within the appropriate steps of your incident flow.
Set up a Test "My Location" - Consider creating a "Corporate HQ" or "Test Location" for you to submit test incidents against.
Configure Supply Chain for Test Location to ensure your test distributor is associated if relevant to your process. To learn more about supply chains, visit this article.
Set up Users for Testing - If you are logged in with an "Administrator" role, you will see all sections of the form when you are in your Community Owner account. This may not be an accurate representation of what your end users will see at each step of the process if you have limited sections that can be edited at different steps of the incident flow. You will want to set up a user in your account and any relevant external parties as suppliers, distributors or supply chain members. If your incident involves 3 types of internal roles, and a supplier and a distributor, then you should set up 5 unique logins. You can login as those users to confirm their permissions are correct, they can view the incident, and they are receiving email notifications as expected. We suggest testing in a group and assigning a "role" for each participant to play in the process.
Submit Test Incidents - Submit at least 1 incident of each Incident Type and flow combination, so you can observe each possible route of the incident resolution process, from each party’s perspective. Log in with the appropriate incident submitter role, so you can preview the correct experience. Select your test location when reporting your incident. If you've configured your supply chain, your test distributor should populate. If your incident form includes a supplier field, be sure to select your test supplier as well.
Here are a few things to look for when reviewing your incident form:
- Ordering of fields presented on the page
- The display name for the fields
- Are fields marked as required that should be optional and vice versa?
- Is the Help Text understandable?
- Should you add Help Text to assist users when submitting the form?
- Are the correct sections and fields viewable and editable at the correct steps of the process?
- If using conditional field logic, is it functioning as expected?
Here are a few things to look for when reviewing your email notifications:
- Confirm you received as expected for your test users
- Review subject lines - anything to add/remove?
- Message - any field details from the form you wish to be included? Any additional instructions or messaging that you should add?
Prior to reviewing your email notifications during this testing process, you can also send a preview directly from the template as you are configuring the email. This preview will give you a feel for how the email will appear in an inbox and allow you to confirm that your formatting and configuration meet your needs. For more information on incident email notifications, visit this article.
Gather Feedback to Determine Revisions - As you conduct your testing, make note of any changes or edits that you believe should be made. Gather feedback from other testers and have an internal discussion in order to identify updates that need to be made. You will want to allow time to make these revisions, review once complete, and modify any training materials you would like to use for roll-out.
Test again to review revisions!