Testing as a User

It is important to understand how changes to Guardian's features and protections will impact your end users. Here, we will go over the steps needed to test these changes in a way that won’t impact other end users unintentionally.

Testing Setup

When testing out different features or protections, it is recommended to have a separate project file and to only modify the Project Settings. This will allow changes to be tested without affecting end users on other registered files.  

Make the desired changes to the Project Settings and then log out of the admin account to test those out as an end user.

User Commands are a good example of something that is best to test as an end user. The Guide and Prevent dialogs are only shown to end users and it’s important to ensure that the wording, images, and links are appearing/working properly.  

New mapping rules can also be tested in a similar way. The mapping rules can be used with either an admin or end user account. The only difference is that end users won’t get the dialog asking to look over incoming properties when loading families into projects.