1. Technology Readiness Training
March 2017
Welcome to the Technology Readiness presentation At the end of the presentation, you’ll receive contact information for Indiana Customer Service.
The PowerPoint for today’s presentation will be available on the Indiana ISTEP+ and IREAD-3 Resource Center at

2. ISTEP+ Part 2 Pre-Test Admin Q&A Sessions April 3, 5, 11, 13
Key Dates
ISTEP+ Part 2 Pre-Test Admin Q&A Sessions April 3, 5, 11, 13
We will have Q&A sessions prior to the start of ISTEP+ Part 2. Reminders will be sent to all CTC’s via the list serve.
Technology Readiness and Proctor Caching

3. Computer-based Testing Components
PearsonAccessnext
Assessment administration portal
Manage student data, test sessions, access reports
TestNav 8
Student test delivery engine
Early warning system
Computer-based assessments are comprised of three main technology components working together to securely deliver test content to students and preserve the security of student responses. Those components are PearsonAccessnext, TestNav 8, and Proctor Cache.
[CLICK] PearsonAccessnext is a system that administrators use to manage student data, set up and schedule computer-based tests, and manage test sessions. PearsonAccessnext is role-based, and users can be assigned specific roles that control which functions those roles can access, and what people serving in those roles can do in the system.
[CLICK] TestNav 8 is the secure testing engine that students will use to interact with test items. Behind the scenes, an inner-component of TestNav called the Early Warning System maintains test security and checks for connectivity or content issues.
The Early Warning System also maintains student responses. While a student is testing, the Early Warning System records student responses in a local encrypted and saved response file. After a few questions are answered, TestNav bundles the answers into a packet and transmits them to our servers. TestNav then waits for a handshake acknowledgement that verifies we’ve successfully captured the responses on our side. This means that we control and verify the transmission of student responses to our servers. It also gives the added benefit of students being able to resume where they left off in the case of a connectivity or network failure.
Another important thing to note is that when students submit their final answers, TestNav won’t completely finalize the student’s test until it has received confirmation that the responses have been captured on our side. We want to be absolutely sure that we have all of the student’s answers before we wrap up the test.
[CLICK] Proctor Cache is free software that works with TestNav to reduce the overall bandwidth requirement for computer-based testing, by pre-downloading the entire test content that your students need and storing it locally in an encrypted format. This feature allows you to serve test content at local speeds rather than Internet download speeds. The requirements are very flexible. This feature doesn’t have to be installed on a server-class operating system. In most cases, a single proctor cache machine can be used to service many students.
Proctor Cache
Works with TestNav to reduce bandwidth requirements
Technology Readiness and Proctor Caching

4. Resources http://indiana.pearsonaccessnext.com
Your technical resources can be found on the Pearson Indiana ISTEP+ and IREAD-3 Resource Center portal. The portal is a central repository for information. There are links to Technology Resources, Training Resources, and Support. You can also link directly to PearsonAccessnext and other tools through this site.
Technology Readiness and Proctor Caching

5. TestNav 8
Let’s begin with an examination of TestNav 8.

6. TestNav 8 Introduction Secure student testing application
Corporation / School Test Coordinators should develop tracking plan
TestNav is the secure application that students will use to participate in computer-based testing.
Students will receive all of the information they need to access TestNav through a student authorization ticket that is printed from PearsonAccessnext.
Corporation and School Test Coordinators (CTCs and STCs) should develop a plan for tracking which computers or devices each student uses to test. It’s best practice to have students resume on the same computer. For tablets and Chromebooks, students must resume testing on the same device.
Technology Readiness and Proctor Caching

7. TestNav 8 Support http://indiana.pearsonaccessnext.com
Support can be found in a couple of places. Again, you can visit the Resource Center at the URL on the screen. As mentioned earlier, you will see a Technology Resources section, a Training Resources section, and a Support section on the home page. We recommend that you visit this portal first for Indiana-specific resources. You can also navigate to the Pearson support site directly for general product support information.
Technology Readiness and Proctor Caching

8. TestNav 8 – Getting Started & Demonstration
Training resources are available on the Indiana Resource Center. We recommend that you review this section for steps to help you get started. You can also access proctor caching, which we’ll discuss later.
[CLICK] Notice the green box for downloading the various TestNav 8 applications.
[CLICK] Later we will discuss Technology Readiness Testing. Please note that information may be accessed here as well.
Technology Readiness and Proctor Caching

9. Secure Tests
We have two types of tests that are used: secure tests and Experience Items. Secure tests require Kiosk Mode, defined here. Secure tests include all production tests and training center tests. The details of where to get the relevant version of TestNav are shown. We’ll cover these requirements and those from the next slide again shortly. [PAUSE]
Technology Readiness and Proctor Caching

10. No Kiosk Mode Required
Tests that do not require Kiosk Mode (Experience Items)
Non-Kiosk Mode tests are used only for Experience Items. Experience Items will help parents and students familiarize themselves with content and format of online tests. They are not production tests. The requirements are listed here for the different browsers.
Technology Readiness and Proctor Caching

11. TestNav App Installers
If your school is downloading the TestNav 8 app, it’s accessible at download.testnav.com.
Based on the platform that you will be using – Desktop or laptop, iPad, or Chromebook - download the app or apps that you’ll need for testing. We’ll talk more about iPads and Chromebooks shortly.
If you’re installing TestNav for Desktop, there are options for Mac, Windows, and Linux.
There are two options for Microsoft Windows: .msi and .exe.
The .msi file is optimized for network installation as a group and pushing out to multiple computers.
The .exe file is for downloading onto individual computers.
There is a .dmg file for installing on Macs.
In general, the Desktop installation takes only a few minutes on an individual computer. Network installations will vary depending on your environment.
[CLICK] Please note the link on this page to TestNav System Requirements. The information on the next several slides all comes from that link.
Technology Readiness and Proctor Caching

12. Updating TestNav App Updating TestNav App: TestNav App Update Process
The update to version is required
Users will see an error message if a testing device does not have the updated version installed
TestNav App
Update Process
Android app
Auto update. No action required.
Chrome app
iOS app
Download updated version from App Store.
TestNav Desktop
Download updated version from download.testnav.com.
TestNav did get updated since the Spring and Summer 2016 ISTEP+ and IREAD-3 test administrations and will have to be reinstalled. You will need to install the new version of TestNav even if you’re using the same computers as last year. If schools tested online for ISTEP+ Part 1 or IREAD, this will already have been updated.
Technology Readiness and Proctor Caching

13. Network Configuration
Firewalls, content filters, spam filters and any other routing or blocking systems should be set to allow access to the following:
*.testnav.com: 80
*.testnav.com: 443
*.pearsontestcontent.com
*.thawte.com
*.usertrust.com
*.comodoca.com
google-analytics.com (optional)
ols+and+PNP+Profile#AccessibilityToolsandPNPProfile- TestNavWhitelist
Before you begin, firewalls and other filtering systems will need to be set to allow a small number of sites. A full list can be reached by clicking “TestNav System Requirements” from download.testnav.com. Please refer to the support site for TestNav System requirements.
Technology Readiness and Proctor Caching

14. Windows, OS X and Linux System Requirements
Windows 7, 8.1 and 10
Mac OS X 10.9 – 10.11
Mac OS is not supported at this time
Linux Fedora 24 (64-bit); Ubuntu (64-bit)
No Java or browser dependencies
The installable TestNav app has a few minimum technology requirements. We’ll cover Windows, Mac OS X, and Linux now, and then discuss Chromebooks, iPads, and Android devices separately.
Mac OS X and Windows are supported; (Mac OS X 10.9 – and Windows 7 – Windows 10).
Please note: Apple recently released iOS 10 and macOS Sierra 10.12; however, Pearson does not currently support these for use with installable TestNav apps, because of a potential test security issue with a feature introduced in these versions. iOS 10.2 however, is supported.
Pearson has added support for macOS Sierra for Kiosk Mode testing with TestNav only with Firefox ESR 45.
Linux is supported on Fedora 24 and Ubuntu
Technology Readiness and Proctor Caching

15. Chromebook System Requirements
Hardware and software requirements
Memory requirements
Operating system
No Java or browser dependencies
Chromebooks and proctor caching
Students testing on Chromebooks can gather cached content
Chromebooks cannot be used as Proctor Cache machines
For Chromebooks, it’s important to note some highlights:
Minimum and recommended memory requirements are listed here
And TestNav requires Chrome OS 50-56
There are no Java or browser requirements for Chromebooks, as students will use the TestNav 8 App to access their test content.
And while a Chromebook can take advantage of a Proctor Cache setup, allowing TestNav to gather cached content, a Chromebook cannot be used as the actual Proctor Cache machine itself.
Technology Readiness and Proctor Caching

16. Chromebooks – Setup Overview
Two Setup Methods
Managed Chromebooks
Unmanaged Chromebooks
Can be performed simultaneously on all Chromebooks in your domain
Two main steps to complete
Install TestNav 8 App and set it to run as a Kiosk App
Preserve local data on Chromebook to retain SRF and log files on the device
Steps have to be performed on each Chromebook
Requires access to the administrator / owner account for each device
Device will be backed up to cloud storage and wiped if you do not have access to the administrator account for the device
Now let’s move into the setup details. As we mentioned before, Chromebooks can either be managed or unmanaged, which presents us with two different setup methods.
[CLICK] For managed devices, all of the setup steps will be performed through the central administration, so all Chromebooks in a domain can be configured at once. When using managed devices, there are two main steps you’ll need to complete – install the TestNav 8 App and set it to run as a Kiosk App, and preserve the local data on the Chromebook to retain Saved Response File (SRF) and log files on the device.
[CLICK] For unmanaged devices, the setup steps will have to be performed on each device individually. This requires access to the administrator account for the device. If you don’t have access to the administrator account, the Chromebook will need to be backed up to cloud storage and wiped clean before you can continue. After testing, it can be restored from the cloud.
Technology Readiness and Proctor Caching

17. Saved Response File (SRF) on Tablets and Chromebooks
Primary saved response file location is managed by the TestNav 8 App
A secondary save location that utilizes an SFTP address must be configured to ensure all devices have a backup save location
Pearson support site provides steps and instructions to find SRF and log files on the TestNav System Requirements page
With TestNav Desktop and browser-based TestNav, the primary save location for Saved Response Files (SRF) and TestNav log files is managed by your TestNav Configuration in PearsonAccessnext, which we’ll examine in a few minutes. With tablets and Chromebooks, the primary location is hardware storage space that is reserved and managed by the TestNav 8 app. Creating secondary save locations is a critical step in preparing for a successful online testing experience. CTCs must confirm with local IT staff that secondary save locations have been configured prior to the test administration to ensure successful capture of student responses. Non-SFTP addresses will be used only by TestNav Desktop and browser-based testing.
The Pearson Support site provides steps and instructions to assist you, should you need to locate the SRF and log files on any student testing computer. This can be found from the TestNav System Requirements page.
Technology Readiness and Proctor Caching

18. iPad System Requirements
Hardware and software requirements
Memory requirements
Operating system
No Java or browser dependencies
iPads and proctor caching
Students testing on iPads can gather cached content
iPads cannot be used as Proctor Cache machines
iOS ‒ , 10.2, are supported
iOS 10 is not supported
Let’s have a look at the system requirements for iPads. It’s important to note some highlights for the iPad:
Minimum and recommended memory requirements are listed.
And your iPad Requires iOS ‒ or 10.2 –
As with Mac OS Sierra, iOS 10 is not supported at this time, though iOS 10.2 and are.
And while an iPad can take advantage of a Proctor Cache setup, allowing TestNav to gather cached content, an iPad cannot be used as the actual Proctor Cache machine itself.
Technology Readiness and Proctor Caching

19. Set Up TestNav on iPad Install TestNav Run App Check
Confirm App Self Lock
Passing systems display
Failing systems display
Start the TestNav app
The first time TestNav is launched, it displays the Enable Microphone Permission message
Tap or click Yes to grant microphone permission
If the student taps or clicks No, TestNav displays another prompt
Now let’s move into the setup details.
Download TestNav for iPads from the AppStore.
To run App Check on each device: Click or tap the appropriate icon for your test from the home page, if you haven’t done so already.
Click or tap the user drop-down menu, and select App Check.
On the Confirm App Self Lock message, click or tap Yes to continue.
Passing systems display a green success message at the top-right of the page.
Failing systems display a red failure message at the top-right of the page.
When you’re ready to start a test, note that the first time TestNav is launched, it displays the Enable Microphone Permission message.
Tap or click Yes to grant microphone permission. If the student taps or clicks No, TestNav displays another prompt, shown here.
Start a test to ensure that you can do so without error. 
There is a Practice Tests link on the Sign In page; click Practice Tests and start a test.
When starting a test, the student should:
Enter a username and password, and tap or click Sign In.
On the Confirm App Self Lock message, click or tap Yes to continue testing.
Students that click or tap No cannot continue testing in the secure test.
Technology Readiness and Proctor Caching

20. Single App Mode Automatic Assessment Configuration (AAC)
AAC ensures that the student cannot access other apps, pages, or features after Single App Mode starts
Locked out features include:
Auto-correction
Definitions
Keyboard shortcuts
Predictive keyboard
Spell check
A new feature of Single App Mode is Automatic Assessment Configuration (AAC). It locks testers into TestNav, blocking several features they shouldn’t access during the testing process. This change is different than the way we did things last year. Administrators will need to remove previous restrictions from last year.
Technology Readiness and Proctor Caching

21. Android Device System Requirements
Hardware and software requirements
Memory requirements
Operating system
No Java or browser dependencies
Android devices and proctor caching
Students testing on Android devices can gather cached content
Android devices cannot be used as Proctor Cache machines
Let’s have a look at the system requirements for Androids. It’s important to note some highlights, such as minimum and recommended memory requirements. TestNav requires Android 5.0 – 7.0
There are no Java or browser requirements for Android devices, as students will use the TestNav 8 App to access their test content.
And while an Android device can take advantage of a Proctor Cache setup, allowing TestNav to gather cached content, an Android device cannot be used as the actual proctor cache machine.
Technology Readiness and Proctor Caching

22. Android Devices – Setup Overview
Two Setup Methods
Google Play for Education
Mobile Device Manager (MDM)
Install app using your Google Play for Education account
Add names or addresses of the users who will need to access TestNav; can also use Google Group or contact group
Google tips: y/?hl=en#topic=
TestNav app can be installed using an MDM that supports Device Owner
Unmanaged Devices
Install using Google Play Store app
Enter TestNav in the search field
Select TestNav, then select Install
When launching TestNav, it will display the Screen Pin dialog. Tap Yes. Tap Start Test Now.
Now let’s move into the setup details. Android devices can be installed with a Google Play for Education (school license required) account, or by using a mobile device manager that supports Device Owner.
[CLICK] To install on Android devices, you can use your Google Play for Education account to download the app. You’ll need to add the names or addresses of those you want to access the TestNav app. Alternatively, you can use Google Group addresses or a contact group. You can find tips for sending content to students on the Google support site.
[CLICK] You also have the ability to install the TestNav app using a mobile device management (MDM) system that supports Device Owner.
You can install TestNav on unmanaged Android devices by following the link on
Technology Readiness and Proctor Caching

23. Early Warning System
Next, we’ll discuss the Early Warning System, the integrated functionality of TestNav that monitors network connection and student response data submission.

24. Early Warning System (EWS)
The Early Warning System (EWS) is integrated functionality in TestNav that provides additional fail-safes in the event of unexpected network disruptions during computer-based testing.
The Early Warning System (EWS) is integrated functionality in TestNav that runs silently in the background. EWS alerts you to any issues that arise during the test administration, such as an interruption in network connectivity or other applications attempting to take control of the desktop.
Early Warning System notifications often involve IT staff, so it’s important for technical staff, as well as administrators and test proctors, to have an idea of how it works and what will trigger an on-screen message.
Technology Readiness and Proctor Caching

25. Saved Response File (SRF)
EWS writes continuously in the background to the saved response file (SRF).
A combination of the student authorization letter and the test session is used to uniquely identify an SRF.
The SRF 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 while TestNav cycles and attempts another upload.
If the response data upload is successful, TestNav creates a new empty SRF and begins the process again. TestNav deletes an SRF only after it is successfully uploaded to the Pearson servers.
TestNav can identify the correct SRF 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.
[CLICK] The Early Warning System writes continuously in the background to the saved response file (or SRF). Some corporations may be concerned about students overwriting each other’s files, but TestNav ensures this will not happen by using a unique file name for each student’s test attempt. [CLICK] A combination of the student authorization letter and the test session is used to uniquely identify an SRF.
[CLICK] The SRF has a response data threshold that, once reached, triggers TestNav to send response data to Pearson servers. This means that TestNav doesn’t upload each individual response immediately, but writes responses to the SRF until it has a batch of responses to upload.
[CLICK] 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.
[CLICK] If the data upload is successful, TestNav will create a new empty SRF and begin the process again. TestNav will only delete an SRF only after it has been successfully uploaded to the Pearson servers.
[CLICK] TestNav uses the student's unique login information to identify the correct SRF if a test is successfully resumed.
[CLICK] TestNav will use only the SRF from the student’s last test attempt when a student resumes a test.
Technology Readiness and Proctor Caching

26. Early Warning System – Triggers
The following will result in a “Test Proctor – Click Here” notification:
Problems writing to save location:
EWS will trigger if…
The student does not have read / write access to save location
TestNav cannot locate the save location
Problems downloading test content:
TestNav cannot connect to a proctor caching workstation to retrieve test content
The student workstation is no longer connected to the Internet
Problems with saved response files (SRF):
The SRF file is moved while the student is testing and TestNav can no longer locate the active file
An aggressive content filter corrupts the SRF file
A technology coordinator attempts to load an incorrect SRF file for the student
Now let’s review the specific events that trigger the Early Warning System. We’ll touch on each of the triggers briefly.
TestNav determines that the Saved Response File location is not viable when:
Students do not have the proper read/write access to either of the designated save locations.
TestNav cannot locate the save location. If the save location is on a network drive and the student is not connected to Internet, TestNav cannot launch the test.
TestNav may be unable to download portions of the test if:
TestNav cannot connect to a proctor caching workstation to retrieve test content.
A student workstation is no longer connected to the Internet while the student is testing and has reached the last item previously downloaded when the student was connected to the Internet.
TestNav is unable to upload student responses to Pearson if:
The SRF file is moved while the student is testing and TestNav can no longer locate the active SRF file.
If an aggressive content filter corrupts the SRF file. Some content filters are very aggressive in filtering data, such as Lightspeed. To avoid this error message, you need to include the static IP address of your proctor caching workstation in your content filter’s exception list to allow full pass-through without data corruption. If you have any questions about this process, please contact the support desk. Contact information for Indiana Customer Service will be provided at the end of today’s presentation.
TestNav might also be unable to upload a student response if a technology coordinator attempts to load an incorrect SRF file for the student. TestNav keeps track of the student’s current SRF file so you cannot load a previously stored SRF for the student or any other student’s SRF using the current login credentials.
Technology Readiness and Proctor Caching

27. Proctor Cache
Let’s move on to Proctor Cache.

28. ProctorCache Overview
ProctorCache is Pearson-supplied software that:
Allows you to pre-cache test content to your local network before a test
Reduces the burden on your internet service provider (ISP) by eliminating redundancy in requests for test content
Stores an encrypted local copy of all pre-cached tests
Proctor caching is required because of its benefits.
Proctor Cache is Pearson-supplied software that’s used in conjunction with TestNav to reduce bandwidth requirements and accelerate the delivery of test content.
So, what can you do with Proctor Cache?
You can precache content before the test to your local network.
You can reduce or eliminate redundant downloads of test content, which will reduce the burden on your Internet service provider (ISP).
And you can store an encrypted local copy of all precached tests and serve them at LAN speeds to students.
Proctor caching is required by the IDOE because of the many benefits it provides.
Technology Readiness and Proctor Caching

29. ProctorCache System Requirements
Runs on Windows and Mac OS X
Utilizes TCP Ports 80, 443, 4480 and 4481
Requires a fixed internal IP address
ProctorCache setup instructions can be found on the Indiana Resource Center site under Technology Resources:
The Proctor Cache software must be installed, and it has a set of minimum requirements. The requirements are not robust, which gives corporations flexibility on what machines they use for proctor caching. It doesn’t require an underlying server-based operating system, and it can run on desktop class hardware and operating systems. Please note that although 1 GB RAM is listed, I would strongly recommend 8 GB RAM, if possible.
Proctor caching can run on both Windows and Mac OS X operating systems
[Macintosh OS X 10.7, 10.8, 10.9, 10.10, or or Windows 7, Windows 8, Windows 10, Windows Server 2008, or Windows Server 2012.]
Proctor caching uses TCP Ports 80 and 443 for communication between the proctor caching machine and the Pearson servers, and ports 4480 and 4481 for communication between testing workstations and the proctor caching machine. This means TCP ports 80, 443, 4480, and 4481 must be opened. 80 and 443 are also listed in the URL and ports configuration. You don’t have to perform this step twice. It’s possible to set custom ports for Proctor Cache. In this case, those specific ports should be opened and not 4480 and 4481.
Because testing workstations must know a predictable network location for the proctor caching machine, proctor caching requires a fixed internal IP address. Those corporations 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 “Upstream Proxy Configuration” section in the Proctor Cache setup instructions.
Technology Readiness and Proctor Caching

30. Proctor Caching Diagram
This diagram illustrates two network scenarios.
The scenario on the left illustrates a network setup that doesn’t use proctor caching. Each student is downloading a unique copy of the test content directly from the Pearson servers. The diagram shows that redundant test copies are being downloaded simultaneously over the corporation’s ISP connection, while students are waiting to test. This heavy use of bandwidth not only affects how quickly the test loads for students, but also the available bandwidth for all other Internet-related activities.
The right side of the diagram shows the network traffic for a test environment successfully using proctor caching. The test content is precached once in an encrypted format to a local workstation designated in the TestNav configuration setup as the proctor caching computer. Students that are assigned to the proctor caching computer will locally access the test content without utilizing your Internet bandwidth, thus decreasing overall network traffic for your corporation. The closer the configured computers are to the proctor caching workstation, the faster the delivery of content.
Corporations have the flexibility to decide where to implement proctor caching in the network environment. Based on local network considerations, corporations can implement proctor caching machines at the corporation level or at the school level. If implementing at a corporation level, we recommend considering the added complexity of the connection between the school and the central location. If proctor caching computers are housed at the school where students are testing, then you don’t have to worry about an outside connection.
Without Proctor Cache, each testing computer must individually connect across the Internet to download test content.
With Proctor Cache, test content is mirrored on a local computer from which the testing computers download test content.
Technology Readiness and Proctor Caching

31. Proctor Cache – Setup Download installer
New Proctor Cache installers
Run installer and start service
Service is normally started by default
Shortcuts exist to start or stop the service, if necessary
Verify service is running; purge old cached content
Installing and verifying the Proctor Cache service is very simple and only takes a few minutes.
First, technology coordinators will download the Proctor Cache installer for their system. These are new installer links since last year, so if you have previously installed Proctor Cache, you should purge your old content, uninstall your previous version, and then reinstall the software.
Run the installer; the InstallAnywhere wizard will prompt you through the minimal installation process. After the installation is complete, start the service. This is normally started by default, but shortcuts are available to start or stop the service, if needed.
Next, verify that the service is running by visiting the ProctorCache Diagnostics page; we’ll cover the Diagnostics page in more detail shortly. If you used proctor caching for a previous test, please ensure that you have purged your previously cached test content. Instructions for purging cached content can be found on the Resource Center.
The links for the downloads can also be found in the ProctorCache setup instructions and on the Landing page.
The ProctorCache software is installed on only the designated proctor-caching machine and not on each of the student workstations. Also, the content only needs to be precached once during the test window. You can purge the content after the test window has ended, and directions for how to purge test content are available on the TestNav 8 Support page on the Set Up and Use Proctor Cache page.
Once installed, your ProctorCache computers can be managed from PearsonAccessnext.
Open ProctorCache Diagnostics screen
Select old content and then Purge; password required to complete
Technology Readiness and Proctor Caching

32. TestNav Configurations
Using TestNav Configurations, you can manage proctor-caching computer configurations and response file save locations
To access administration of proctor caching on PearsonAccessnext, log onto the site and select Setup, then TestNav configurations.
Technology Readiness and Proctor Caching

33. TestNav Configurations
Select Create / Edit TestNav Configurations from the start drop-down.
Technology Readiness and Proctor Caching

34. TestNav Configurations
If creating a new configuration, click Select Tasks, Create / Edit TestNav Configurations. Then click Start. You can have only one configuration assigned to each organization. If you want multiple proctor caching computers per organization, other computers may be added to an existing configuration. If you are creating a new configuration, create a recognizable name for it. Select Precaching Computer Override, if you want to utilize this fail over feature. This setting allows a computer that has already started testing to bypass a proctor caching computer which suddenly becomes unavailable and to resume the test using test content downloaded directly from Pearson servers. Select the organization. Type in the computer name, IP Address, and port. The default ports are 4480 and Creating secondary save locations is a critical step in preparing for a successful online testing experience. CTCs must confirm with local IT staff that secondary save locations have been configured prior to the test administration to ensure successful capture of student responses. For Windows, Mac, and Linux testing machines, you may use a network share or an SFTP server as your secondary response file (SRF) location. For Android, iOS, or ChromeOS, you must utilize an SFTP server for a SRF file location. Not that if you put nothing for the Primary Location, Windows, Mac, and Linux will default to the user directory of the logged on user. If you want to verify locations, you can take a sample testing device, launch a practice test and answer a few questions. From another device, monitor the secondary save location. Verify that a file is created that contains as part of its name the tester’s STN.
Technology Readiness and Proctor Caching

35. Configuration Details
Selecting a configuration name allows review of the details and the addition of more precaching machines.
Technology Readiness and Proctor Caching

36. Configuration Details
With multiple precaching computer settings, note that you can delete the added proctor caching computers.
Technology Readiness and Proctor Caching

37. ProctorCache Diagnostics Screen
IP Address>:4480
Tests:
Provides information about test content and caching status
Test Details displays status of individual test items
Clients:
Displays clients that have connected to TestNav by IP address
Client Details displays details by computer
Settings:
Allows you to set a custom password to refresh, reload, or purge cached content
On the proctor caching computer, you can verify the status of the cached content by using the Proctor Cache Diagnostics page. Depending on your installation preferences, you can access the Diagnostics screen from your Start menu on Windows machines, Finder on a Mac, or through desktop shortcuts.
You also can directly navigate to the ProctorCache Diagnostics page by typing address>:4480 in your browser, and hit Enter to view the proctor caching interface.
[CLICK] You will see three tabs:
[CLICK] Select the Tests tab for information about [CLICK] Test Content and [CLICK] Caching Status.
[CLICK] Selecting the Clients tab [CLICK] will allow you to monitor client [CLICK] Connectivity.
[CLICK] Finally, the Settings tab allows you to set a [CLICK] custom password to refresh, reload, or purge cached content.
Technology Readiness and Proctor Caching

38. Diagnostics Screen – Tests Tab
Content displayed at Test and Form levels
Functionality to Refresh, Reload, or Purge selected content
Clicking on a test name displays the Test Details screen, which shows cached content by item
On the Tests tab, you’ll see content displayed at the Test and Form levels.
Functionality is available to Refresh, Reload, or Purge selected test content if necessary, and it requires a password. The initial password is available in the ProctorCache setup instructions to protect against unauthorized deletion of cached content. We’ll cover how to change the password, if desired, shortly. You’ll also see status indicators for each row of cached test content.
Clicking on a test name will display the Test Details screen, which displays individual items cached for the test. There, status indicators will appear next to each item.
Technology Readiness and Proctor Caching

39. Tests 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
An OK status means the content is successfully cached.
[CLICK] 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.
Loading… means the content is currently loading.
[CLICK] 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 couldn’t be completed successfully.
MD5 Mismatch means the MD5 comparison was completed, but the files didn’t 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 isn’t resolved, contact Pearson Customer Service for technical assistance.
NOTE: 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 the Pearson Help Desk.
Technology Readiness and Proctor Caching

40. Diagnostics Screen – Clients Tab
The Clients tab provides visibility to the testing workstations that have requested test content from proctor caching.
Each testing workstation on the Clients tab also has a status indicator.
Clicking on an IP address or name of a computer will show the details of the computer that connected to the proctor caching machine to fetch test content.
Clients that have connected to TestNav are listed by IP address
Selecting a computer name displays a Details screen, which shows information regarding a particular computer
Technology Readiness and Proctor Caching

41. Clients 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
NOTE: Clients are removed after 12 hours of inactivity.
An OK status means the client is currently active.
[CLICK] 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.
Please note, clients are removed after 12 hours of inactivity but will reappear on the list once they request test content again.
Technology Readiness and Proctor Caching

42. Diagnostics Screen – Settings Tab
Allows user to set a custom ProctorCache password
Can only be accessed when visiting the Diagnostics screen from the proctor-caching machine
The Settings tab allows technology coordinators to set a custom ProctorCache password to perform the tasks of refreshing, reloading, or purging cached content. The default password is in the directions located on the Resource Center; however, Pearson strongly recommends that you create a custom password. You can change the default password at any time, but only from the Diagnostics screen from the proctor caching machine.
[CLICK] Enter the current password and then provide a new password and confirm your entry. Then click Submit to save the password. If you forget your password, the administrator can reset it following the directions in the Proctor Cache setup instructions which are located on the Resource Center.
Technology Readiness and Proctor Caching

43. Infrastructure Trial
Let’s move on to Infrastructure Trial.

44. What is an Infrastructure Trial?
An Infrastructure Trial is a “dress rehearsal” of a computer-based assessment. It does not use real student information. This is a low stakes, dry run for final confirmation that:
TestNav is configured correctly
Devices can successfully run TestNav
Network will bear the full load
Participating staff know what to do for computer-based assessments
What is an Infrastructure Trial?
An Infrastructure Trial is a “dress rehearsal”. The IDOE highly recommends participating in an Infrastructure Trial to prepare for computer-based testing. Unlike a live assessment, you won’t use real student information. Instead “dummy” student information is used. During this low-stakes dry run, you’ll confirm that:
TestNav is configured correctly
Devices can successfully run TestNav
The network will bear the full load
And participating staff know what to do for computer-based assessment
An Infrastructure Trial provides an opportunity to review your device, network, and staff readiness in a low-stakes assessment, and most importantly, has the least impact on students.
Technology Readiness and Proctor Caching

45. Infrastructure Trial
The trial is conducted on the Training Site using test data, not on the live site. (Note the tan background on this slide, which indicates that we are on the Training Site.)
Make certain you select Infrastructure Trial as the administration across the top. Then select TestNav configurations under Setup. The same steps for setting up TestNav configurations mentioned previously will need to be done here. A step-by-step guide is available on the Indiana Resource Center website mentioned previously.
Please refer to the Infrastructure Trial Guide found on the Indiana Resource Center website at
Technology Readiness and Proctor Caching

46. Infrastructure Trial
Sample students, groups and test sessions will be generated by Corporation IT staff
Corporation Information Technology staff will need to complete some of the steps of this Infrastructure Trial before Test Coordinators can complete the remaining ones. Technology staff will generate sample students, groups, and test sessions for use throughout this process.
Technology Readiness and Proctor Caching

47. Infrastructure Trial
This trial mirrors the entire process of testing, both verifying the technological resources and the knowledge of some key staff.
As this mirrors a live training administration, sample sessions are created, then students are placed into those sessions.
Students are placed into sample sessions created for this purpose
Technology Readiness and Proctor Caching

48. Infrastructure Trial Precache content for the test sessions
Tests are precached [CLICK] for the sample sessions, [CLICK] [CLICK] testing that process as well.
Technology Readiness and Proctor Caching

49. Infrastructure Trial Tests are started Practice tests conducted
Practice tests are conducted by students or volunteer participants
Tests get marked complete [CLICK]
Take note of any technical issues. You can contact Indiana Customer Service with any questions. We’ll be providing that contact information at the end of this training.
Tests are started
Practice tests conducted
Tests marked complete
Note any technical issues
Technology Readiness and Proctor Caching

50. Wireless Infrastructure Trial
Wireless access points –
more is better
Limit number of computers per wireless access point
Distance – closer is
better
Limit obstructions
Fully charged devices
Another step for some environments is wireless testing, if your school uses wireless devices. Schools can test both wired and wireless at the same time.
Here are some best practices when testing wirelessly:
Ensure sufficient wireless access points 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 farther away.
Obstructions, such as walls and equipment, between testing workstations and wireless access points can disrupt connection and negatively affect performance.
Set up a small number of workstations to measure performance on a wireless network before setting up a large number of workstations.
Test performance before scaling
Technology Readiness and Proctor Caching

51. Support
Thank you for watching this important training.

52. Indiana Customer Service Contacts
Phone: Monday – Friday 7:00 a.m. – 7:00 p.m. Eastern Pearson Indiana ISTEP+ and IREAD-3 Resource Center
If you have questions or need assistance, you can contact Pearson’s Indiana Customer Service by calling , Monday through Friday, from 7 a.m. to 7 p.m. Eastern Time, or via at