How to Test your FluidReview Site

Sarah Paterson -

Testing your site is a crucial step in ensuring that all aspects are working as you desired them to be. With many customized and automated processes, the system will work as it is configured to, therefore this article will walk through the different ways in which you can test different sections of the site prior to launch. 

In this Article...

Adding a Test User

When testing your site, it is extremely helpful to have email accounts that you can use to test various processes in your site.

Adding a User

The process of adding a test user is the same as adding a live user to the site. In order to add a new user:

  1. Click on Manage Your Site
  2. Select Add Users
  3. Enter the First NameLast Name, and Email Address of the user you wish to add
  4. Select the Group(s) you wish to add the user to in order to test. For example, if testing the submission process, you will want to add the user to an Applicant group
  5. Select "I have permission to contact this user via email."
    NOTE: You will not be able to add a user to your site without selecting this option. 
  6. Click Add User

WARNING! Your test users will follow the same rules as given to your registered users. For example, any deadlines, start dates or visibility settings placed on tasks will also apply to this user. 

Using Gmail Spoofing to add Test Users

Within FluidReview, you can make use of Gmail's ability to spoof an email address. This process will allow you to set up multiple accounts within the site which appear to have different email addresses, however if an email is sent from the site it will be sent to the real email. 

The way this works is if your normal email is example@gmail.com you can create as many accounts as you need to under this email by adding a + and additional text after the initial part of the email. For example: 
example+test1@gmail.com
example+applicant@gmail.com
example+100@gmail.com

This can be useful in testing how an email will be displayed when received and when in the process certain emails will be sent. You can refer to Testing Emails for more information in regards to this. 

NOTE: The value that goes after the + can be anything you need it to be as long as the characters adhere to a regular email format. 

Return to Top

Testing the Submission Process

Once you have added a user as an Applicant to the site you can use this applicant to test the submission process.

Testing the Submission Process

In order to test the submission process with applicant permissions:

  1. Assume the Role of the Applicant
  2. Create a new submission for that user
  3. Navigate through the submission process by completing the tasks in the Application stage as if you were an applicant applying to that submission. 
    NOTE: Try by testing your application forms, uploads, recommender invites etc. This will also allow you to gain a better understanding of the process when it comes to troubleshooting live applicant issues. 
  4. Once you have completed all the tasks and are satisfied with the application process, submit your test submission and begin testing the Review process.  

Testing Submissions while Locking out Registered Applicants

In certain circumstances your site is open and you need to test the workflow. However, you may not want your registered applicants to be able to log-in and complete the submission process.

As mentioned above in Adding Test Users, your test users will follow the same rules as given to your applicants. For example, any restrictions, deadlines, start dates or visibility settings placed on tasks will also apply to test users

In order to test without allowing users to access the application you will need to:

  1. Temporarily Unlock Submissions from the Dashboard Quick Controls.
  2. Test your Submissions
  3. Once you are done testing you can then Lock submissions again if you wish to restrict users from editing existing submissions.

Testing the Recommendation Task

If your submission process has a recommendation task involved, you may wish to test this process.

  1. Assume the Role of the Applicant
  2. Within the created submission Start the recommender task
  3. Enter information for your test recommender. 
    TIP! Use Gmail spoofing detailed above to send the invite to your own email address and test the login process of a recommender. 
  4. Either login as the test recommender or Assume the Role of the recommender
  5. Once you are in the recommender panel, complete the applicable task
  6. Submit the recommendation
  7. Go to the submission as an administrator to see the completed recommendation appear at the top of the page. 

Testing the submission process will allow you to ensure that all of the piping variables in your forms and the triggers are all working correctly for you. You can also refer to the specific sections below for more information on how to test each feature. Adding a user and a test submission will be consistently referred to throughout the various sections of this article. 

Return to Top

Testing the Review Process

Using your test submission(s) you can move these submissions to a Review Stage in order to test the review process.

In order to test the review process:

  1. Add a User as a Reviewer
  2. Assign the submission(s) to the Reviewer
    NOTE: If the submissions are not assigned to the reviewer using one of the available methods, the submissions will not be visible to the reviewer in their reviewer panel.
  3. Assume the Role of the Reviewer
  4. Navigate through the review process to complete reviews for your test submissions.
    NOTE: Try by testing the review form, making notes on submissions, downloading reviews and submissions etc. This will also allow you to gain a better understanding of the process when it comes to Troubleshooting live reviewer issues. 

Testing the review process will allow you to ensure that all of the piping variables in your forms and the triggers are all working correctly for you. 

Return to Top

Testing Triggers

When you have created a trigger in the site it is important to test its functionality to ensure that the trigger is correct. This is especially important for when you have conditions on your triggers and want to ensure that it fires for the correct submissions, and doesn't fire for submissions that don't meet your conditions. 

In order to test your triggers:

  1. Create a test submission that matches all of your applicable conditions of the trigger.
  2. Ensure that your trigger is Active
  3. Using the test submission perform the activation.
    For example, if the activation is to complete a form, use the submission to complete that form. 
  4. Go to Analyze Results> Triggers to confirm that the trigger has fired. 

If the trigger has not fired as desired, compare your test submission with the trigger. Ensure that the submission meets all of your conditions, and that you are activating the trigger correctly.

Return to Top

Testing Emails

Using the Send Test button

When creating emails within Manage Users, Manage Submissions, Triggers, or Text & Translation, you will have the ability to Send a Test. This feature will allow you to enter in an email address and test the format and deliverability of the emails when being received. For example, if you have a logo uploaded to The Basics section of the site you will be able to see how it appears within the received email. You can also refer to the article How to Configure the Logo in Emails, to ensure the image is the proper size within the email.

This test email will display the general template of the email, but it will not be personalized to the user receiving it. Therefore, if you have piping variables within the email these would not be sent when clicking Send Test. Instead, the piping variable will be shown as a placeholder. 

 

Using a Test User/Submission (Recommended)

As mentioned above, the Send Test function will not pipe variables into the received emails, therefore if you are looking to test these variables you will need to send the email to a user/submission that those variables apply to. For example, if you are looking to pipe in a response from an applicant form, you will need to ensure that the test submission you are using has completed that response. 

This process is where Gmail Spoofing can come in handy. You can use a spoofed account to create a submission, and then send the email to that account containing your piped variables. The email is sent to your Gmail address and you will be able to see how the variables appear. This test will also include any formatting and design that you have applied to the email. 

Return to Top

Testing Forms

Using the Form Preview

During the build process of a form you have the ability to Preview the form right from the Form Builder. This will allow you to see the form as an applicant would. It will also allow you to test any validation, advanced expression piping, in-form piping, or branching logic that has been created within the form in order to ensure that the correct questions are showing when they should be. 

However, if you are looking to test piping variables within the form, such as pulling in the applicant's name, or a response to a question in a different form, the Preview will not be beneficial. This is because the Preview is not linked to a submission and therefore does not have a source to pull submission data from. This will need to be tested using a Test Submission. 

 

Using a Test Submission

Although the Form Preview has a lot of capabilities for testing the form, you will not be able to test form-to-form piping variables, or piping specific to the applicant, and a registered applicant with this information will need to be used. 

In order to test piping variables in this manner you we would recommend using a Test Submission. Using a test submission will allow you to test Piping Variables, as well as everything that can be tested within the Form Preview. 

Return to Top

Testing Reports

The best way to test your reports is through trial and error. In order to test the report builder:

  1. Create a new report.
    NOTE: The most common report type is the Basic:CSV report
  2. Test the different Sources available when creating your report to determine if the source will pull the information you are looking for.
    NOTE: The most common sources are "Submissions" and "Rankings."
  3. Under the Columns section click on the "(#) Selected" dropdown. This dropdown will allow you to select information that you wish to pull into your report. 
    TIP! If you are looking for a specific column, for example, a response to a question in a form. Use the Quick Search at the top of the dropdown to search for the column you'd like.
  4. Under the Filters section, apply any filters you require to narrow down your submissions in the downloaded report. 
    TIP! 
    If you are looking for a specific filter, for example, filtering by a response to a question in the form. Use the Quick Search at the top of the dropdown to search for the filter you'd like.
  5. Read through the Extra Options and their descriptions to see if those options will suit the report you are looking for.
  6. Click Save & Download

Go through the downloaded report. If the report doesn't download the columns you are looking for, or perhaps the filters aren't showing the correct filters, continue to alter the columns/filters until you are able to reproduce the report you are looking for.

Return to Top

Have more questions? Submit a request

0 Comments

Article is closed for comments.