PARCC Field Test Spring 2014

PARCC Field Test Spring 2014
Technology Set Up This module addresses the technical setup for your network and devices in preparation for the PARCC Field Test in the Spring of It is recommended that this presentation be viewed by both district and school test administrators as well as district and school technology staff. Understanding this information for all staff involved in the computer-based assessment will facilitate successful test administration. Many of the features and functionalities described in this module must be accessed with a secure PARCC PearsonAccess login obtained from your district coordinator.

Agenda Technology Setup Introduction Computer-Based Testing Components
Site Readiness Checklist Preparing for Testing TestNav Proctor Caching SystemCheck for TestNav TestNav Configuration Providing Support During Testing Early Warning System Other Technology Considerations Contacts During this presentation, we will introduce you to preparing your Technology Setup, cover the necessary activities to prepare for testing, discuss how Pearson provides support during testing, cover some other technology considerations, and wrap up by providing contact information if you have any questions.

Computer-Based Testing Components
There are several technology components of computer-based testing. We will discuss: PearsonAccess, the administrative website used by district and school coordinators, administrators, and technology coordinators. Proctor caching, the Pearson supplied software to accelerate the delivery of test content TestNav, the secure, browser-based student application for accessing the computer-based assessment SystemCheck for TestNav, an application developed to assist district and school technology coordinators with determining device and network readiness PearsonAccess includes both secure and non-secure areas within the website. Users without secure access can review available training and materials, access SystemCheck, and download proctor caching software. Users must be issued a secure login id and password to create and maintain TestNav configurations, create and manage online test sessions and maintain student data and test registrations. You must also have secure access to pre-cache test content for proctor caching. We will also discuss TestNav’s ability to temporarily store and transfer student response information to Pearson servers for scoring and reporting. The ability to locally store encrypted backup files of student responses requires student read and write access to testing workstations and network file shares.

Site Readiness Checklist
Identify technology coordinators Configure firewall, content filter, proxy server and spam filter Identify the testing rooms and the number of workstations to be used for testing Identify the proctor caching machine(s) and install proctor caching Complete the SystemCheck tests to verify testing workstation readiness and the number of concurrent testers supported using proctor caching Update testing workstations to comply with TestNav hardware/software requirements Enter TestNav configuration(s) in PearsonAccess training site Pre-cache test content from PearsonAccess site Complete the Infrastructure Trial by launching Training Test from student machines to verify TestNav configuration(s) and test network config Duplicate TestNav configuration(s) in PearsonAccess operational site These are the steps necessary to prepare for a computer-based assessment. This training module will provide information on these steps to prepare for a computer-based assessment. Identify technology coordinators who will be assisting in site readiness activities at the district and school level Configure firewall, content filter, proxy server and spam filter to allow Pearson testing addresses Identify the testing rooms and the number of workstations to be used for testing so you know how many testing workstations may be used concurrently Identify the proctor caching machine(s) and install proctor caching Complete the SystemCheck tests to verify testing workstation readiness and the number of concurrent testers supported using proctor caching Based on the results from step 5, you may need to update testing workstations to comply with TestNav hardware/software requirement Enter TestNav configuration(s) in PearsonAccess training site Pre-cache test content from PearsonAccess training site Complete the Infrastructure Trial by launching Training Test from student machines to verify TestNav configuration(s) and test network config Duplicate TestNav Configuration(s) in PearsonAccess operational site The time required to complete site readiness activities can vary a lot from school to school, but past reports from LEAs indicate that many schools can be completed in less than 2 hours.

TestNav Browser-Based Testing Platform TestNav is a secure, browser–based application used at student workstations to take computer-based tests. For the PARCC field test, students will be using the TestNav 8 platform. Some states may be using the browser-based, TestNav 7.5 platform for other computer-based assessments. You may only access PARCC assessments using TestNav 8.

TestNav Technology Requirements
Firewalls, content, and spam filters must be set to allow access to Pearson domains Minimum screen resolution of 1024 x 768 is required Browser Requirements: Java runtime plugin version 1.5 or higher Windows firewall configured to allow javaw.exe to communicate Accept Java applet Allow pop-ups for Pearson sites Allow local file access to home directory Complete requirements for TestNav 8 can be found at: Note: For states also using TestNav 7.5 for other assessments, Adobe Flash Player version 10 or higher is required. TestNav has minimum technology requirements to successfully launch a computer-based assessment. Firewalls, content and spam filters must be configured to allow access to Pearson domains. The list of domains are available in the TestNav 8 Technology Guidelines and also listed in the next slide. A minimum screen resolution of 1024x768 is required. TestNav is browser-based and has minimum browser requirements. On a desktop or laptop workstation, your browser will need Java runtime plug-in version 1.5 or higher and the Windows firewall must be configured to allow javaw.exe to communicate. If you receive a pop-up requesting access for a Java applet to run, you must accept the Java applet. Pop-ups should be set as allowed for Pearson sites and students must be allowed to read and write to a local home directory for the purpose of temporarily storing response and log file information. For a complete list of TestNav 8 requirements, visit the requirements page at Pearson continually monitors and evaluates hardware and software requirements. As vendors release newer versions of their products, the recommended requirements are updated accordingly. If your state uses TestNav 7.5 or earlier, Adobe Flash Player version 10 or higher is required but TestNav 8 does not require Flash.

Firewalls, Content Filters & Spam Filters
The following domains and ports must be allowed to pass through your Internet firewalls, content filters, or spam filters. *testnav.com 80, 443 *pearsonaccess.com 80, 443 *amazonaws.com 80, 443 Note: Districts using IP-based content filters MUST contact Pearson Technical Support to receive the allowed IP addresses and Pearson support will make an update in PearsonAccess so that the correct URL prints on the Student Authorization Tickets. PARCC Call Center phone number: PARCC Customer Support PARCC Customer Support Hours: 6:00 am 8:00 pm CST, Monday–Friday The following domains and ports must be allowed to pass through your Internet firewalls, content filters, or spam filters: *testnav.com , 443 *pearsonaccess.com , 443 *amazonaws.com 80, 443 Please note, districts that use an IP-based content filter must contact Pearson Technical Support to receive the allowed IP addresses and Pearson support agents will change a setting in PearsonAccess so that the Student Authorization tickets print the correct URL. The PARCC support center will be available to assist you, if needed. Support is available Monday-Friday, 6:00am to 8:00pm central time.

Preparing Student Computers
After verifying network and testing workstation readiness, freeze your environment and do not accept updates until after the test window, if possible. Any applications or update processes that may launch automatically on testing workstations may interrupt testing. These programs should be configured to not launch automatically. Common applications that may launch automatically include: Anti-virus software, Java, Adobe, browsers or operating systems performing automatic updates Power management software on laptops warning of low batteries Screen savers with automatic message notification Energy saving features After verifying you network and testing workstation readiness, Pearson recommends that you freeze your environment and do not accept updates until after the testing window, if possible. Any applications or update processes that may launch automatically on testing workstations may interrupt testing. These programs should be configured to not launch automatically. Common applications that may launch automatically include: Anti-virus software, Java, Adobe, browsers or operating systems performing automatic updates Power management software on laptops warning of low batteries Screen savers with automatic message notification Energy saving features

Wireless Best Practices and Recommendations
Wireless testing for computer-based testing Wireless testing for computer-based testing is supported. Determining the number of access points that are needed for coverage, along with the location of each, will depend on the number of students using the access point(s), the wireless protocols used, and the interference sources in the building (e.g., pipes, wires, wall and stud types, other signals, etc.)

Wireless Best Practices and Recommendations
Best practices when testing wirelessly: Ensure sufficient wireless access and limit the number of computers per wireless access point for better performance. Computers located closer to wireless access points perform better than those that are far away. Obstructions such as walls and equipment between testing workstations and wireless access points can disrupt connection and negatively affect performance. SystemCheck can be used to assess the number of students that can be tested using a wireless network. Set up a small number of workstations to measure performance on a wireless network before setting up a large number of workstations. Test your wireless network using the device configuration you plan for test day. If you are planning to test wirelessly, there are some best practices Pearson recommends: Ensure there is sufficient wireless access, and limit the number of computers per wireless access point for better performance. Distance from the wireless access point matters; computers located closer to wireless access points perform better than those located farther away. Obstructions can disrupt connection and negatively affect performance. Be aware of walls and equipment that might be between testing workstations and wireless access points. SystemCheck’s Testing Capacity tab can be used to help assess the number of students that can be tested using a wireless network. Scale your set up – start with a small number of workstations to measure performance on a wireless network before setting up a large number of workstations. Prior to student testing, test your wireless network using the device configuration you plan to use.

General Best Practices and Recommendations
General Performance: Use proctor caching for best network performance. Use SystemCheck extensively to test proctor caching and network environment before live testing Extremely limited internet connections may require additional planning around pre-caching content Local network or WAN connections can sometimes become the limiting path for connection speed Here are some general performance recommendations; these apply to both wired and wireless networks: Use proctor caching for best network performance. Proctor caching helps reduce the burden on your internet service provider by pre-caching test content locally. Also, you should use SystemCheck extensively to test your proctor caching and network environment before students begin testing. Extremely limited internet connections may require additional planning around pre-caching content. Proctor cache earlier rather than later. Local network or WAN connections can sometimes become the limiting path for connection speed. If a school or district has very low internet connection speeds, or often sees high utilization of their ISP connection (eg, >90%), the district should plan for long download times to pre-cache content. The district may also need to pre-cache during off-hours, to avoid other usage of its internet connection. Some examples of when this might be the best course of action include: Example 1: A middle school that connects to the internet via a WAN connection through a nearby high school, or Example 2: A lab of 50 computers that all feed through a single data port connection to the rest of the local network. In all such cases, the most effective remedy is to set up the proctor caching station on the “student side” of any connection bottlenecks.

Student Responses TestNav will save student responses to an encrypted backup file during testing and when the student exits the system to avoid losing response data. TestNav requires at least one working save location. TestNav, by default, saves student response data to: <home dir>/Pearson/<student>/SRF Pearson recommends designating two Response File Save locations in a TestNav Configuration in PearsonAccess . Create a TestNav configuration to specify custom Primary and Secondary file locations. Primary Response File location should be on student computers. Secondary Response File location should be a shared network location. Students must have full read/write access to designated Response File locations. TestNav will save student responses to an encrypted backup file during testing and when the student exits the system to avoid losing response data. Please note: TestNav requires at least one working save location. TestNav, by default, saves student response data to the local student computer location. Pearson recommends designating two Response File Save locations in a TestNav Configuration in PearsonAccess. When you create a TestNav configuration, you will be able to specify custom Primary and Secondary file locations. The primary Response File location should be on the student’s computer. Pearson recommends the Secondary Response File location should be a shared network location. Please make sure that students have full read/write access to designated Response File locations.

TestNav Directories TestNav creates a Pearson directory in the home directory of the testing computer: Windows XP C:\Documents and Settings\<username>\Pearson\... Windows Vista and 7 C:\Users\<username>\Pearson\... Mac //Users/<username>/Pearson/... Student Log files: Pearson/student/logs Student response file (SRF) default location: Pearson/student/srf TestNav and test content is temporarily stored locally: Pearson/temp Pearson recommends that the Pearson directory be excluded if desktop restoration tools such as DeepFreeze are used. TestNav must have the ability to write to the student’s home directory on the testing workstations. TestNav creates a Pearson directory in the home directory of the testing computer, which will vary depending on the operating system in use. Student Log files, the Student response file (SRF) default location, and the temporarily stored TestNav and test content will also be saved to the Pearson directory. Please note that Pearson recommends the Pearson directory be excluded if desktop restoration tools such as DeepFreeze are used.

Proctor Caching Proctor caching is Pearson-supplied software that is used in conjunction with TestNav to reduce bandwidth requirements and accelerate the delivery of test content. It allows you to cache test content to your local network BEFORE testing and reduces the burden on your ISP by eliminating redundant requests for test content. Cached test content is encrypted and stored locally. The proctor caching software is available on the non-secure support pages within PARCC PearsonAccess. The application is free and does not require secure login access to download.

How Proctor Caching Works
Without proctor caching, multiple redundant copies of the same test are downloaded over the district’s ISP connection while students are waiting for the test to load. This heavy use of bandwidth not only affects how quickly tests load for students, but also the available bandwidth for all other internet related district activities.

With proctor caching, districts will pre-cache one copy of each test and tests will be served to the students from the proctor caching machine. This minimizes redundant requests for test content over the district ISP connection, loads tests faster for students, and minimizes the effect of computer based testing on district bandwidth utilization.

Districts have the flexibility to decide where to implement proctor caching in the network environment. Based on local network considerations districts can implement proctor caching machines at the district, school or classroom level.

Proctor Caching Requirements
Proctor caching hardware requirements can be found at Runs on Windows and Mac OS X Does not require an underlying server-based operating system or server class hardware TCP Ports: 80 (Internet), 4480, and 4481 (Local Network) Proctor caching requires a fixed internal IP address For setting up an upstream proxy refer to the Windows or Mac “Tips on Proctor Caching” section in the TestNav Proctor Caching User Guide available December 2013 Use the SystemCheck Testing Capacity tab to assess your network capacity during computer-based testing Complete proctor caching hardware requirements can be found at Proctor caching is compatible with both Windows and Mac OS X. It does not require an underlying server-based operating system. It can run on desktop class hardware and a desktop class operating system, which gives districts flexibility on what machines they use for proctor caching. Proctor caching uses TCP Port 80 for communication between the proctor caching machine and the Pearson servers, and ports and 4481 for communication between testing workstations and the proctor caching machine. Because testing workstations must know a predictable network location for the proctor caching machine, proctor caching requires a fixed internal IP address. Those districts which require internet traffic to pass through an upstream proxy server will have to configure proctor caching to point to their proxy server. For details on setting up an upstream proxy refer to the Windows or Mac “Tips on Proctor Caching” section in the TestNav Proctor Caching User Guide. You should use the SystemCheck Testing Capacity tab to assess your network capacity during computer-based testing Please note, the same proctor caching software can be used for states testing with both TestNav 7.5 and TestNav 8. Note: The same proctor caching software can be used for states testing with both TestNav 7.5 and TestNav 8.

Proctor Caching Setup Download proctor caching installer from PearsonAccess at Support > Resources > Technology Information Run the installer and Start Proctor Caching if it is not already started by the installer. Use SystemCheck from client computer to verify that proctor caching is functional. Create a proctor caching setup or add a proctor caching computer within PearsonAccess at the district or school level. You can download the appropriate proctor caching installer from the PARCC PearsonAccess site by going to Support > Resources > Technology Information. Run the installer; proctor caching should be started by the installer. If not, select Start Proctor Caching from the installed Proctor Cache program. You can then use SystemCheck from a client computer to add the proctor caching computer and verify that proctor caching is functional. You will then need to create a proctor caching configuration within PearsonAccess at the district or school level.

Proctor Caching Diagnostics
Once installed, the proctor caching software includes access to a diagnostic monitoring web page to assist district personnel with visibility to the status of cached content and monitoring caching connections from testing workstations. In your browser, type address>:4480 and hit Enter to view the proctor caching interface. You will see three tabs; the Home tab provides an at-a-glance view. Select the Contents tab for information about test content and caching status. Select the Client List tab to monitor client connectivity. Type address>:4480 and hit Enter to view the proctor caching interface Select the Contents tab for information about test content and caching status Select the Client List tab to monitor client connectivity

Contents Tab Content is displayed at the Test and Form level.
Functionality is available to Refresh, Reload, or Purge selected test content. Clicking on a test name will display the Content Details screen which displays individual items cached for the test. On the Contents Tab, you will see content displayed at the Test and Form level. Options are available to Refresh, Reload, or Purge selected test content if necessary, and requires a password. The password is available in the Proctor Caching User Guide to protect against unauthorized deletion of cached content. Clicking on a test name will display the Content Details screen, which displays individual items cached for the test.

Contents Tab – Status Ok – Content is successfully cached Not Loaded – Content is not cached Waiting… - Content is waiting to be loaded Loading… - Content is currently loading Failed to load content – There was a failure to load content MD5 Check Invalid – MD5 comparison could not be completed MD5 Mismatch – MD5 comparison was completed but files did not match In general, any status in red is a critical problem. Any content with a red status should be checked and reloaded. If the problem is not resolved, contact Pearson Support. The content tab provides status indicators for each item of cached test content. An Ok status means the content is successfully cached The yellow status indicators usually appear when the content is in the process of being cached. Not Loaded means the content is not cached Waiting… means the content is in the queue, waiting to be loaded and Loading… means the content is currently loading Red status indicators indicate problems with cached content. Failed to load content means there was a failure to load content Proctor caching also performs an MD5 check once an item has been cached to compare the test content on the Pearson servers with the cached item. The MD5 check should show that the items are identical. MD5 Check Invalid means the MD5 comparison could not be completed successfully MD5 Mismatch means the MD5 comparison was completed but the files did not match In general, any status in red is a critical problem. Any content with a red status should be checked and reloaded. If the problem is not resolved, contact PARCC Customer Support for technical assistance.

Client List Tab Clients that have connected to TestNav are listed by IP address. Clicking on a computer will display the Client Details screen which displays information regarding a particular computer connecting to proctor caching. The Client List tab provides visibility to which testing workstations have requested test content from proctor caching. You will see a list of clients (computers) that have connected to TestNav, desginated by their IP address. Clicking on a computer name will display the Client Details screen, which displays information regarding a particular computer connecting to proctor caching.

Client List Tab – Status
Ok – Client is active Idle – 5 to 30 minutes since client was active Long Idle – 30 minutes to 12 hours since client was active Clients are removed after 12 hours of inactivity Each testing workstation on the client list tab also has a status indicator. An Ok status means the client is currently active The yellow status indicators appear when the clients have gone idle. Idle means 5 to 30 minutes have passed since the client was last active Long Idle means 30 minutes to 12 hours have passed since the client was last active Clients are removed after 12 hours of inactivity, but will reappear on the list once they request test content again.

SystemCheck for TestNav SystemCheck for TestNav should be used to assess your testing environment readiness prior to computer-based assessments. SystemCheck allows you to select the test-specific parameters for each upcoming assessment. It can verify that testing devices meet minimum requirements and check actual upload/download speeds from testing workstations. This will allow a district to evaluate their testing environment and make necessary adjustments prior to testing.

SystemCheck for TestNav Overview
SystemCheck was developed for customers to validate their testing workstations meet the minimum system requirements needed to run TestNav and to provide information about network capacity for student testing. To gather realistic results, SystemCheck should be run from a student testing machine on the same day of week/time of day as when you anticipate performing online testing. For example, if you plan to test on a Monday morning at 9am, run your checks on a Monday morning at 9am; running in the afternoon or on a weekend will not replicate the testing environment. SystemCheck will only need to be run once on a computer for each administration unless changes are made to the operating system or Java. To access SystemCheck, visit To learn more about SystemCheck for TestNav, visit the Technology Information Resources page at Note: SystemCheck cannot be launched on iPads and Chromebooks. Also, iPad-mini devices are not supported devices. SystemCheck validates testing workstations meet the minimum requirements to run TestNav 8. To gather realistic results, SystemCheck should be run from a student testing machine on the same day of week/time of day as when you anticipate performing online testing. Launch SystemCheck from Learn more about SystemCheck by visiting

iPads and Chromebooks SystemCheck will not run on iPads or Chromebooks
Since SystemCheck is Java based, it will not run on iPads or Chromebooks. A TestNav app will be available early 2014 to launch TestNav on these devices, which will need to meet minimum system requirements in order to run the app. No other readiness steps will need to be followed for iPads or Chromebooks. SystemCheck will not run on iPads or Chromebooks App coming to launch TestNav on these devices

Create a TestNav Configuration
PARCC Field Test 2014 Create a TestNav Configuration In order for TestNav to know where to save encrypted backup files, you must create a TestNav configuration in PearsonAccess. If you are proctor caching, this configuration also notifies TestNav where to access test content on the proctor caching machine during the testing window.

Creating a TestNav Configuration
To create a TestNav configuration, you will need to get log in access to the PARCC PearsonAccess. Technology staff will receive secure access from their district coordinator. The Configure TestNav menu can be selected from the homepage. It is used to access the configurations settings to set primary and secondary temporary student response save locations, and if applicable, set up a connection to your proctor caching workstations.

PearsonAccess Test Setup: Configure TestNav
To create a TestNav configuration for your organization, click on the New Configuration button.

Enter a unique name for the new configuration to identify it and click on Continue. Configuration names should be something that distinguishes them when creating test sessions; for example, Computer Lab 1 and Computer Lab 2, or High School and Middle School.

Click Add Organization. From the View By options set, select either “System/District” or “School/Institution” to locate the correct organization. You will then be prompted select the radio button next to the school or district and click Add. You may add multiple organizations by repeating this process. When you have completed adding organizations click Continue. Please note, an organization can be associated with only one configuration. Additional organizations can be added later under Configuration Details.

Next you will specify the TestNav settings for a proctor caching machine to be used by the organization, if applicable. Fill in a name for the caching machine, the internal network IP address of the caching machine and the port number, which is 4480 for Pearson supplied proctor caching. If you will be using a non-Pearson supplied caching solution you will uncheck the box next to “This computer uses Pearson-supplied proctor caching software” and make sure the port is the correct port for the caching solution you will be using. If you will not be proctor caching, simply leave the IP Address and Port fields blank; you will still need to complete the next steps. Next you will set the Save Locations for the students’ encrypted backup files for Windows or Mac workstations. You may use the Pearson default locations, which is the Pearson folder in the user’s home directory. Pearson recommends that a secondary save location be designated when possible for redundancy. If you wish to set custom locations for the Primary location, uncheck the “Use Default Location” checkbox and enter the path for the custom location. Click Continue to complete the configuration. C:\Documents…

After saving, you will be brought to the main Configure TestNav screen which will display your completed TestNav configurations. You may click on a configuration name to view the Configuration Details screen.

The Configuration Details screen shows you the entire configuration. From this screen you have the ability to edit the TestNav settings, make a TestNav setting the new default for an organization, or delete a TestNav setting by clicking on the links provided. You can also modify the configuration by adding another organization if necessary. This screen shows a configuration with multiple TestNav settings. A TestNav setting is needed for each set-up that will be used by the organizations within the configuration. Note that each TestNav Settings configuration has its own particular Save Locations set up, and note that the top setting is identified as the “Default TestNav Settings” for the organization. When a new test session is created, it will automatically be set to the default TestNav settings for an organization, unless changed to another. Because TestNav settings are now tied to the test session level, you may have sessions pointing to a TestNav setting that you are modifying. If you click Make Default or Delete, you will be asked for instructions on what to do with sessions that are already pointing to a particular TestNav setting.

If you attempt to change the default TestNav Settings for an organization by clicking on “Make Default,” you will be prompted on what to do with test sessions that are pointing to the current default. You may select to redirect those test sessions to use the new default settings, or you may choose to allow those test sessions to remain unchanged. If you change the sessions to point to a different TestNav Setting, the changes will take effect immediately and students from those sessions will use the new settings the next time they log into a test.

In a similar manner, if you attempt to delete a TestNav Setting for an organization by clicking on “Delete,” you will be prompted on what to do with test sessions that are currently pointing to the settings you are deleting. You may select to redirect those test sessions to use the default settings, or you may choose to reassign them to use a specific TestNav Setting by clicking on the radio button and selecting the appropriate settings from the combo box. When you change the sessions to point to a different TestNav Setting the changes will take effect immediately and students from those sessions will use the new settings the next time they log into a test. Please note that PearsonAccess will not allow you to delete the Default TestNav Setting. If you wish to delete the default TestNav Setting you must first designate a new default setting, and then you may delete the unwanted Testnav Setting.

PARCC Field Test 2014 Early Warning System
The TestNav Early Warning System (EWS) is designed to help save student responses locally in the event of a network interruption. EWS saves the student’s responses locally to an encrypted backup file so the student may either continue testing or exit the system without losing data.

Early Warning System (EWS)
The Early Warning System (EWS) is integrated functionality that gives TestNav a high degree of fault tolerance and provides additional fail-safes in the event of unexpected network disruptions during computer-based testing. The Early Warning System (EWS) is integrated functionality that gives TestNav a high degree of fault tolerance and provides additional fail-safes in the event of unexpected network disruptions during computer-based testing. EWS notifications often involve IT staff, so an understanding of Early Warning messages is helpful to correct any issues during testing.

Student Responses: SRF Files
The Early Warning System writes continuously in the background to the student response files (SRF). Both the Primary and Alternate files are written to at the same time. The SRF file has a response data threshold that, once reached, triggers TestNav to send response data to Pearson servers. Uploading of response data is continuous. If an upload to the Pearson servers fails, student responses continue to be saved locally and TestNav cycles and attempts another upload. If the response data upload is successful, TestNav creates a new empty SRF file and begins the process again. TestNav only deletes an SRF file once it is successfully uploaded to the Pearson servers. The Early Warning System writes continuously in the background to the student response files (SRF). Both the Primary and Secondary (if configured) save locations are written to at the same time. The SRF file has a response data threshold that, once reached, triggers TestNav to send response data to Pearson servers. This means that TestNav does not upload each individual response immediately, but writes responses to the SRF files until it has a batch of responses to upload. The uploading of response data is continuous. If an upload to the Pearson servers fails, student responses will continue to be saved locally. TestNav will continue to cycle and attempt another upload. If the response data upload is successful, TestNav will create a new empty SRF file and begin the process again. TestNav will only delete an SRF file once it has been successfully uploaded to the Pearson servers.

Student Responses: Identification
A combination of the test ticket ID combined with the session token is used to uniquely identify a Student Response File (SRF). TestNav can identify the correct student response file if a test is successfully resumed. Only the SRF from the student’s last test attempt can be used when the student resumes a test. Since Pearson recommends that one of the SRF save locations be configured as a network location, districts may be concerned about students overwriting each other’s files. TestNav ensures this will not happen by using a unique file name for each student’s attempt to test. A combination of the test ticket ID combined with the session token is used to uniquely identify a Student Response File (SRF). TestNav uses this information to identify the correct student response file if a test is successfully resumed. TestNav will only use the SRF from the student’s last test attempt when a student resumes a test.

TestNav Early Warning System: Triggers
Scenario 1: TestNav determines that neither Save Response File Location is viable. Results in an immediate Test Proctor Click Here notification. Scenario 2: TestNav is unable to download portions of the test. Scenario 3: TestNav is unable to upload student responses to Pearson. Results in a Test Proctor Click Here notification only if the student attempts to Exit or Submit the test. While the Early Warning System operates in the background throughout the entire test, monitoring connectivity and saving responses to encrypted backup files, there are three scenarios which may cause the Early Warning System to display messages to the student. Scenario 1: TestNav determines that neither Save Response File Location is viable. TestNav requires that there be at least one working save location for the encrypted backup file as a safety precaution against a loss of internet connectivity. If TestNav detects that it can not save to any of the configured save locations, it will result in an immediate Test Proctor Click Here notification screen being presented to the student. Scenario 2: TestNav is unable to download portions of the test. TestNav attempts to load the entire test to the testing workstation as quickly as possible in sequential order. If TestNav’s repeated attempts to download a piece of test content are unsuccessful then it assumes there has been a loss of connectivity and this results in an immediate Test Proctor Click Here notification being presented to the student. Scenario 3: TestNav is unable to upload student responses to Pearson. In this scenario, TestNav has already been able to download the test content, and it has at least one valid SRF location to save an encrypted backup file, but an attempt to upload responses has failed after repeated attempts. This also indicates a loss of connectivity, but TestNav will not notify the student immediately. This allows the student to continue testing without disruption. Because TestNav has all the test content to deliver the entire test to the student, and it has at least one valid location to save response to, it will continue to deliver the test, and only results in a Test Proctor Click Here notification being displayed to the student if the student attempts to Exit or Submit the test.

TestNav Early Warning System: Test Proctor Click Here Screens
One of the following screens will appear when scenarios 1, 2, or 3 occurs. Students should be instructed to ALWAYS raise their hand when presented with either of the Test Proctor Click Here screens. They should NEVER click the Test Proctor-Click Here button. Note: It may be necessary to contact your local Technology Coordinator to determine the appropriate course of action. One of the following screens will appear when scenarios 1, 2, or 3 occurs. Students should be instructed to ALWAYS raise their hand when presented with either of the Test Proctor Click Here screens. They should NEVER click the Test Proctor-Click Here button. Please note, it may be necessary to contact your local Technology Coordinator to determine the appropriate course of action.

TestNav Early Warning System: Scenario 1 – SRF Error
In this scenario there is an issue with the Response File Location(s). Either the student does not have full access to the location(s) OR the location(s) are temporarily unavailable. In scenario one, there is an issue with the Response File Locations. Either the student doesn’t have full access to the location(s) OR the location(s) are temporarily unavailable. You can resolve this issue by entering and saving a viable Response File Location. If the issue is temporary, reselect the original location. Then, click the Save and Continue button. Resolve this issue by entering and saving a viable Response File Location. If the issue is temporary, reselect the original location. Then, click the Save and Continue button.

TestNav Early Warning System: Scenario 2 – Unable to Download
In this scenario, TestNav cannot download one or more test items to the student computer. Either the proctor caching machine is not properly functioning OR there is a loss of connectivity between the student and Pearson. The ONLY way to resolve this situation is to click the Close TestNav button. The student’s testing status will remain as STARTED in PearsonAccess. Once communication is restored, resume the student in PearsonAccess and have the student log back into TestNav. In scenario two, TestNav cannot download one or more test items to the student computer. Either the proctor caching machine is not properly functioning OR there is a loss of connectivity between the student and Pearson. The ONLY way to resolve this situation is to click the Close TestNav button. The student’s testing status will remain as STARTED on the Session Details screen within PearsonAccess. Once communication is restored, resume the student in PearsonAccess and have the student log back into TestNav.

TestNav EWS – Scenario 3 – Unable to Upload
In this scenario not all of the student responses have been received by the Pearson testing server. However, responses not received by Pearson have been saved locally to the Primary Response File Location. In scenario three, some or all of the student responses have not been received by the Pearson testing server. However, responses not received by Pearson have been saved locally to the Primary Response File Location. You may try to resolve this scenario by clicking the Retry button until the submission of responses is successful or click on Close TestNav. If you close TestNav, the student will need to log in again and complete their test after communication with the testing server is restored. You may try to resolve this scenario by clicking the Retry button until the submission of responses is successful or click on Close TestNav.

Other Technology Considerations
PARCC Field Test 2014 Other Technology Considerations Now let’s review some other things to keep in mind regarding your technology environment.

Additional technical setup considerations for PARCC Field Tests can be found in the Full Technology Specifications for 2014 PARCC Field Test Participation document at > Additional Information. This document includes: Tablet/thin client specifications Headphones/earphones requirements Keyboard requirements Accommodation/accessibility features Assistive technologies Additional technical setup considerations for PARCC Field Tests can be found in the Full Technology Specifications for 2014 PARCC Field Test Participation document located in the Additional Information section at This document includes information on: Tablet and thin client specifications Headphone and earphone requirements Keyboard requirements Accommodation and accessibility features Other assistive technologies

Additional Training Modules for Technology Setup: SystemCheck for TestNav Evaluating device readiness Evaluating network readiness Setting up an Infrastructure Trial Purpose and description of Infrastructure Trial Infrastructure trial readiness checklist Emerging Technologies and Security with Computer-Based Testing ( available January 2014) Using thin clients and virtual desktops Computer-Based testing on iPads and Chromebooks Security and room layout considerations for computer-based testing Additional training is available to learn more about SystemCheck, Setting up an Infrastructure Trial, and emerging technologies supported for the PARCC field test. The SystemCheck training module will provide instruction on how to use SystemCheck to evaluate your device and network readiness. The module will demonstrate how you can determine your network capacity by adding proctor caching computers to reduce bandwidth utilization. The Setting up an Infrastructure Trial training module will provide you with information about purpose and importance of conducting an Infrastructure Trial prior to the PARCC field-test to confirm readiness. The Emerging Technologies and Security with Computer-Based Testing training module will introduce you to new technologies supported for computer-based assessments. If you are planning on using iPads or Chromebooks, this module will provide you with information on additional setup requirements necessary to secure the desktop for high-stakes assessments. This module will also review special considerations for virtualization and thin client environments. Additionally, this module will provide best practice information for making sure that your computer lab or classroom is ready for secure, high stakes, computer-based testing.

Support Contacts PARCC Support Center 888-493-9888
This concludes our presentation. For additional support, you may contact the PARCC Support Center at or by at

PARCC Field Test Spring 2014

Similar presentations

Presentation on theme: "PARCC Field Test Spring 2014"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

PARCC Field Test Spring 2014

Similar presentations

Presentation on theme: "PARCC Field Test Spring 2014"— Presentation transcript:

Similar presentations

About project

Feedback