Testing as a User

It is recommended to test Guardian’s various features and protections to better understand how they work and impact the end-user experience. This can be done by following these steps:

1. Create a project model for testing.
   • A copy of an actual project model, or an older completed model, is recommended.
2. Create a new testing Mapping Configuration and assign it to the test model.
   • This will allow the Project Administrators assigned to the project to create mapping rules without affecting other registered models.
3. Establish the Project Settings for the test model.
   • By modifying and activating features through the Project Settings, Administrators can test different features and protections without affecting other registered models.
4. Log out as an Administrator to test as an end user.
   • When  new features/protections are enabled, Administrators can log out of their account and test Guardian’s features and protections from the end-user perspective.
   • Administrators can easily log in and out during the same Revit session to continually change and test settings.

Testing Examples

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 working properly.

New Mapping Rules can also be tested similarly. The Mapping Rules can be used with either an admin or end-user account. The only difference is that end users won’t receive the dialog asking to look over incoming properties when loading families into projects.