Test Monitoring Overview

Overview 

The Test Monitoring Application within the DRC INSIGHT Portal uses a Monitoring Code to assign a participant’s test session to a Test Monitor. To do this, a Test Monitor will open the Test Monitoring application where a random unique Monitoring Code will be assigned. The Test Monitor will share this code with the participants they will be monitoring. After logging in to a test, participants will enter the Monitoring Code and they will then show up on the Test Monitoring Dashboard. 

Once the participant is admitted to the test, they appear in the Test Monitoring Dashboard with the following filterable information: 

• Participant Name
• Assessment
• Status 
  Note: See the All Tab section below for a full description of all statuses
• Registration Start

Test Monitors can only see participants using their Monitoring Code, and cannot share their Monitoring Code with other DRC INSIGHT Portal users. Upon launching the application, if there is not an active Monitoring Code, one is generated that will expire at the end of the day. Test Monitors can generate a new code and choose an expiration date of up to five days from when the code is generated. Monitoring Codes expire at 11:59 p.m., local time, on their expiration date.   

Test Monitoring Test Session Configurations

The test session can be configured to use Test Monitoring using Manage Test Sessions in the DRC INSIGHT Portal Test Management application by editing the following fields: 

• Test Monitoring settings:
  • None (default) - the Student Verification page does not display the Enter Monitoring Code field for any participants.  
  • Required - the Student Verification page displays the Enter Monitoring Code field for all participants. Participants are required to enter a Monitoring Code to begin testing. 
• Restricted Access settings:
  • False (default) - After entering the test monitoring code on the Student Verification page, the participant will not be placed in a waiting room and may begin testing immediately.
  • True - After entering the test monitoring code on the Student Verification page, the participant will be placed in a Waiting Room, where the Test Monitor controls when participants begin testing.
  • Important: Use of the Waiting Room is highly recommended. If you change the Test Monitoring setting to Required, please also change the Restricted Access setting to "True" to enable use of the Waiting Room.

For directions on how to use a Monitoring Code, see Generating and Using a Monitoring Code. 

For directions on how to configure a test session to use Test Monitoring, see Configure a Test Session for Test Monitoring. 

Waiting Room Tab

The Waiting Room tab will contain participants who are in a Waiting status. The tab label will show the number of participants currently in the Waiting Room so that the Test Monitor is aware of how many participants are waiting to be allowed into the test. As participants have been allowed into the test, their status changes from Waiting to Active. They will be removed from the Waiting Room tab, and will be visible in the All tab for monitoring.

Test Monitors can view the following information on the Waiting Room tab:

• Name - the participant’s name
• Actions
  • Allow:
    • Enabled when participant has a status of Waiting 
    • Clicking Allow will let that participant enter the test
• Assessment - the name of the Assessment to which the participant is registered to the dashboard
• Registration Start - the date/time that the participant registered to the dashboard (entered a valid Monitoring Code on the Student Verification screen in the Test Engine)
• Elapsed Waiting Time - the number of minutes the participant has been in the Waiting Room in the Test Engine

Test Monitors can take the following action on the Waiting Room tab:

• Sort or filter the results
• Allow a single participant, multiple participants, or all participants into the test

All Tab

The All tab contains all participants who are registered to the Monitoring Code. The tab label will show the number of participants registered to the Monitoring Code. 

The user can view the following information on the All tab:

• Name - the participant’s name
• Actions
  • Allow: Enabled when student has a status of Waiting. Clicking Allow will let that student enter the test.
  • Pause: Will pause a student test for up to 20 minutes.
  • Stop: Will exit the student from the test. The student will be able to log back in and resume testing at another time. This will not submit the student test for scoring.
  • Resume: Enabled when student has status of Paused. Clicking Resume will restart a student test after it has been paused.
    
• Assessment - the name of the Assessment to which the participant is registered to the dashboard
• Status
  • Active - Participant is registered to the Monitoring Code and may be actively testing; is not in one of the other statuses
  • Waiting - Participant is in the Waiting Room and needs to be allowed into the test
  • Inactive - Participant has done no navigation within the Test Engine for at least 5 minutes
  • Paused - Participant has Paused the test
  • Exited - Participant has exited the Test Engine either from using the Exit button, closing the secure browser on their testing device, or from timing out on the Pause Test screen
  • Completed - Participant has submitted the test session
• Navigation - the part of the test and screen that the participant is currently viewing in the Test Engine. Example: Reading: Question 1 / 20 where Reading is the Test Session.
• Progress - the number of answers the participant has submitted out of the expected number of answers for that part of the test.
  • N/A will appear when the participant has not yet begun testing (they are still on Student Verification, Waiting Room, Test Sessions, or Test Directions screen)
• Registration Start - the date/time that the participant registered to the dashboard (entered a valid Monitoring Code on the Student Verification screen in the Test Engine)

Test Monitors can take the following action on the All tab:

• Sort or filter the results
• Allow a single participant, multiple participants, or all participants into the Test

Participant View

After a participant has successfully logged into the Test Engine, they are brought to the Student Verification screen. It is on this screen that the participant enters the Monitoring Code if the Test Session is configured to use Test Monitoring. 

If they enter an invalid or expired code, they will see the following message: Your monitoring code is invalid. Please request a valid code from your test administrator.

When the configuration for Test Monitoring is set to Required, the participant must enter a valid Monitoring Code before they can click the Continue button and proceed into the test.

When the configuration for Test Monitoring is set to Required with Restricted Access, the participant must enter a valid Monitoring Code before they can click the Continue button. Once they click Continue, they are brought to the Waiting Room screen where they are unable to start the test until they have been allowed in from the Test Monitoring Dashboard by the Test Monitor.

Participants can take the following action from within the Waiting Room screen: 

• Exit from the Test Engine. In this scenario, the Test Monitoring Dashboard will show the participant with a status of Exited.
• Continue into the test after they have been allowed in from the Test Monitoring Dashboard by the Test Monitor.