Presentation is loading. Please wait.

Presentation is loading. Please wait.

Technology Coordinator Training FCAT/FCAT 2.0/EOC Computer-Based Testing.

Similar presentations

Presentation on theme: "Technology Coordinator Training FCAT/FCAT 2.0/EOC Computer-Based Testing."— Presentation transcript:

1 Technology Coordinator Training FCAT/FCAT 2.0/EOC Computer-Based Testing

2 Technology Coordinator Training Agenda 2 Configuring the Testing Environment – Support Information – Computer-Based Testing (CBT) Glossary – Network and System Configurations System Specifications Preparation Information Proctor Caching Overview TestNav and TestHear Overview Wireless Best Practices TestNav and TestHear Configuration Best Practices TestNav System Check Tool

3 Technology Coordinator Training Agenda, cont. 3 – Proctor Caching Downloading, Installing, and Verifying the Proctor Caching Software – TestNav and TestHear Downloading, Installing, and Launching TestNav 6.9 and TestHear – Pre-Caching Test Content TestNav and TestHear Early Warning System Common Errors and Solutions Lessons Learned Contact Information

4 Support Information 4 Where to find Support Resources  --> Support Tab  – TestNav Technology Guidelines – TestNav Early Warning System Reference Manual – Proctor Caching Guide – Infrastructure Readiness Guide  FDOE website – Computer-Based Testing: Note: Most links are simply redirects to

5 Support Information 5 Contact Pearson Support Phone Number: 1-877-847-3043 Appendix C in the manual provides the following information: PearsonAccess  User Accounts – District assessment coordinators received instructions for setting up user accounts from FDOE.  Browser requirements  Logging in for the first time  Resetting passwords Training Center  Test Setup Exercise Appendix D in the manual is a CBT Test Administrator Quick Reference Guide. Note: PearsonAccess will timeout after 14 minutes of inactivity.

6 CBT Glossary 6 PearsonAccess – The website used for almost all test preparation (e.g., PreID), setup, administration, and reporting tasks. Verify that you are in the correct test administration each time you log in. Requires a username and password. Links to support materials:

7 CBT Glossary 7 PearsonAccess Training Center Accessed from the Training Center tab on PearsonAccess homepage or at Provides an opportunity to  Practice PearsonAccess tasks  Manage the Infrastructure Trial in preparation for testing Requires a username and password.

8 CBT Glossary 8 TestNav6.9 The computer-based platform that Florida uses for high-stakes assessments. TestNav6.9 is an application that is installed either on a file server or on each computer that will be used for testing.

9 CBT Glossary 9 TestHear The computer-based platform used to deliver CBT accommodated forms (large print, color contrast, zoom, screen reader, assistive devices). TestHear is an application that must be installed on each computer that will be used for testing. Only operates on Windows or Macs that are also running Windows.

10 System Specifications for TestNav, TestHear, and Proctor Caching 10 Operating System Specifications Windows/PC Windows XP (Service Pack 3)  Pentium III 733 MHz processor  512 MB RAM Windows (Service Pack 1)  Pentium III 1 GHz processor  1 GB RAM Windows 7  Pentium III 1 GHz processor  1 GB RAM Apple/Macintosh Mac OS X 10.4  G3, G4, G5 500 MHz processor  512 MB RAM Mac OS X 10.5  Intel, G4, G5 867 MHz processor  512 MB RAM Mac OS X 10.6  Intel processor  1 GB RAM Mac OS X 10.7  Intel processor  1 GB RAM Mac OS X 10.8  Intel Core 2 Duo processor  2 GB RAM General Specifications (Windows/PC and Apple/Macintosh) Each computer must meet or exceed the following General Specifications in addition to the applicable Operating System Specifications below:  500 MB available disk space  1024x768 screen resolution  Keyboard and mouse (or other pointing device)  High-speed internet connection

11 11 System Specifications for TestNav, TestHear, and Proctor Caching Additional Specifications for TestHear (Accommodated Forms)  TestHear will operate on Windows PC workstations and on Macintosh workstations that have Mac OS 10.5 or later installed and are running Windows (e.g., via Boot Camp). TestHear will not work on Mac OS X 10.4 or on Macs that cannot also run Windows.  For students requiring the screen reader, the computer must be equipped with an audio card and headphones. In addition to ensuring that workstations meet the minimum specifications, it is strongly recommended that you run an ePAT on any new workstations to ensure that the display size is appropriate for testing. For an optimal student experience, any computer that takes a noticeably long period of time (e.g., more than 10 seconds) to start and run applications, even computers which meet the requirements above, should not be used for high-stakes computer-based testing, if possible. The testing platform does not permit access to other applications during testing. This means that any applications that may automatically launch during testing will interrupt the student’s testing session, logging the student out of the test. Applications such as antivirus updates, power management software (laptops), screen savers, and email with automatic message notifications should be configured so they do not launch during test sessions. Even though the specifications state that each computer must have a mouse, touchpads are permitted for students who are comfortable using them.

12 Preparation Information 12 Infrastructure Trial Test The Infrastructure Trial Test must be run on each computer to be used for testing. (Not required to be part of district- or school-wide administration, although this is preferred.) Instructions are provided in the Infrastructure Readiness Guide posted to or Practice Tests/ePATs All students must complete a practice test prior to participating in any computer-based test administration. The ePAT Launcher and the test content must be downloaded on to each computer that will be used for the practice test. Instructions, the ePAT Launcher, and the test content are available at TestHear ePATs are available for students who will take accommodated CBT forms.

13 Proctor Caching – Network Diagram 13

14 Proctor Caching – How does it help? 14 Proctor Caching allows you to pre-cache test content to your local network before the test. Reduces burden on your ISP by eliminating redundancy in requests for test content. Stores an encrypted local copy of all pre-cached tests. A caching solution is required for Florida online testing and will deliver the best online testing experience.

15 Proctor Caching – Misc. 15 Runs on both Windows and Mac OS X. Does not require an underlying server-based operating system. TestNav must be configured through the installer or editing the file to communicate through Proctor Caching. TestHear must be configured through the installer. Proctor Caching should be set up first so the IP address can be entered during TestNav or TestHear installation. If all internet traffic must pass through an upstream proxy server, Proctor Caching will need to be configured to communicate through that device. TestNav and TestHear request test content from Proctor Caching on port 4480.

16 Proctor Caching Computer Placement 16 Can be at the lab- or the school-level. Should be as close as possible on the network to the TestNav or TestHear workstations and prior to any potential bottlenecks. Use the TestNav System Check to determine the appropriate ratio of Proctor Caching machines to student workstations.

17 Test Delivery – Local Installation 17 Download and install TestNav on each workstation used for test delivery. Must use local installation for TestHear. Configure each machine to communicate with the Proctor Caching machine(s). More challenging to manage than a server installation. System automation tools like SMS (Windows) and Apple Remote Desktop (Mac) make local installs of TestNav much more practical. TestHear cannot be deployed with system automation tools.

18 Test Delivery – File Share Installation 18 Download and install TestNav on a file share. Configure the file share installation to communicate with the Proctor Caching machine. Create a shortcut to the file share installation of TestNav on each workstation used for test delivery. Easier to manage than a local installation.

19 Local Installation vs. File Share Installation 19 ProsCons File Share + Single point of installation and configuration changes + Easier to implement in a large-scale testing environment + Centralized single location for log files - Adds a single potential point of failure Local + Quicker launch time + Limits potential points of failure - Increases installation time (Note: System automation tools, such as SMS [Windows] and Apple Remote Desktop [Mac] can make local installs much easier) – TestNav only - Requires that configuration changes be made on each machine

20 Wireless Networks Best Practices 20 DO use a local installation of TestNav or TestHear A local install for wireless testing increases the odds of success. Local installations reduce network traffic on access points to just test content and student responses. DO NOT overload access points with too many clients. The bandwidth curve of online testing is different than normal internet usage. Use common sense wireless networking principles and past wireless performance as a guide. Reducing the client to access point ratio for online testing can avoid the access point bottleneck. NOTE: The size of the accommodated tests (TestHear) may cause further delays if administered over a wireless network.

21 TestNav and TestHear Installation Best Practices 21 The TestNav file is the only configurable settings file. This file can be edited with Notepad or TextEdit. Editable variables in Proxy_Host - Designates a proctor caching or proxy machine IP address Proxy_Port - Designates a proctor caching or proxy machine port number Primary_Save_Location & Alternate_Save_Location - Designates the Early Warning save locations Student machine logins will need full access to these directories TestNav/temp TestNav/Logs gh\TestHearPearson\Data Early Warning Save Locations (primary and secondary) TestNav or TestHear installation directory (read-only access)

22 TestNav and TestHear Installation Best Practices (contd.) 22 Local Installation - If you use hard drive imaging tools like Deep Freeze, you must exclude the TestNav/Logs, gh\TestHearPearson\Data and Early Warning System save locations. Network Installation Do not run the TestNav installer on the file server itself. Run the installer on a client workstation and install TestNav to a shared folder on a network drive. Once installed to the network drive, ensure the file has valid file paths for the save locations.

23 TestNav and TestHear Installation Best Practices (contd.) 23 Firewalls/Content Filters The following domains and ports must be allowed to pass through your Internet firewall or proxy system. Port 443 is for admin access only. Student level traffic is port 80. Hash encryption can inadvertently form a word.

24 TestNav and TestHear Installation Best Practices (contd.) 24 Configure Applications That Launch Automatically Any applications that may automatically launch on a computer should be configured not to launch during testing sessions. Common applications that may launch automatically include: Anti-virus software performing automatic updates Power management software on laptops warning of low batteries Screen savers Email with auto message notification.

25 TestNav and TestHear Installation Best Practices (contd.) 25 Screen resolution All tests are authored to a screen resolution of 1024x768 so make sure that your testing machines are capable of 1024x768 resolution. Screen Resolutions below this setting will cause an error as TestNav tries to load the test. Screen Resolutions above this setting will be reset to 1024x768 when the test loads when using TestNav. TestHear does not automatically resize the screen resolution so ensure TestHear machines are set to 1024x768

26 System Check for TestNav 26 The following steps will guide you through the process of using System Check for TestNav. The System Check tool can be found by going to and clicking on Support > Additional Resources. The specific URL is Click the TestNav 6 tab and follow the instructions provided. Once you see the “Congratulations” screen in the TestNav window, click the Network User Capacity tab.

27 System Check for TestNav (contd.) 27 Click Add Caching Server. Enter a generic name for the Proctor Caching computer to be tested, the IP address of the Proctor Caching computer, and port 4480. Click Save.

28 System Check for TestNav (contd.) 28 Click Start and System Check will perform a bandwidth test. Once the test has been run, System Check will show an estimate for how many students can be tested on the specified Proctor Caching computer. For non-accommodated tests (TestNav) and TestHear Math tests, select the “TestNav (All Sub)/TestHear (Non-Reading)” administration. For accommodated Reading tests, change to “TestHear Accommodated Reading Test” and click Start again to run the check for accommodated numbers.

29 System Check for TestNav (contd.) 29 Click the Testing Volume Calculator tab. This tab will be used to estimate how many users can be tested with the bandwidth that is available.

30 System Check for TestNav (contd.) 30 Enter the number of students that will be testing concurrently on a single caching server. Slide the green bar under “Available link speed between workstations and Proctor Caching workstations” to specify the available bandwidth between the testing workstations and the Proctor Caching computer.

31 System Check for TestNav (contd.) 31 Now slide the green bar under “Average network utilization for the network between workstations and Proctor Caching workstations” to indicate the percentage of bandwidth normally used at this site (excluding the bandwidth congestion for testing). Once this is done, the “Outputs” box will now either be white, yellow, or red.

32 System Check for TestNav (contd.) 32 In order for computer based testing to be successful, it is highly recommended that the Outputs box display a white background. If anything other than a white background is displayed, odds are that you will encounter difficulties during testing. Once all the tools within System Check for TestNav have been used, you have successfully established a plan for your testing environment.

33 Demonstration 33 Proctor Caching Downloading Proctor Caching Installing Proctor Caching Verifying Proctor Caching is Running TestNav 6.9 Downloading TestNav Installing TestNav Launching TestNav TestHear Downloading TestHear Installing TestHear Launching TestHear

34 Mac Proctor Caching 34 There are two files to be used for installing Proctor Caching software on a Mac: a template file and a command file.

35 Mac Proctor Caching 35 Double-click the command file and click Open on the security window. This will bring up another security window which prevents you from running the installer. The executable bit on the command file is not set so the OS will not allow you to execute it.

36 Mac Proctor Caching 36 You must first correctly set the executable bit. Open Terminal and type “sudo chmod +x “ and drag the command file to the window to complete the path. Hit Return and you will be prompted for your admin password. Enter the password and hit Return and the executable bit is set.

37 Mac Proctor Caching 37 Double-click the command file again and you are presented with the install screen. Type 1, then hit Return to begin the installation. Answer the proxy server questions appropriately and the install will complete.

38 Pre-Caching Test Content 38 Disable Popup Blocking Software (for PearsonAccess) A pop-up blocker will block the pre-caching screens from opening on administrative workstations. School assessment coordinators are responsible for setting up test sessions in PearsonAccess, and technology coordinators are responsible for pre- caching test content prior to testing. Test content will be available to be pre-cached at least one week prior to testing. Demonstration Configure browser settings Pre-cache test in PearsonAccess

39 Pre-Caching Test Content (contd) 39 Check Proctor Caching application to confirm cached content. – Windows – Mac

40 TestNav and TestHear Early Warning System 40 The TestNav™ Early Warning System (EWS) is designed to save student responses locally in the event of a network interruption. EWS saves the student's responses to an encrypted backup file so the student can either continue testing or exit the system without losing data. Designate two (2) file save locations for student responses in the event of a connectivity loss to the testing servers. Best Practice: Primary response location should be a shared location because it allows access to stored student responses from one location. The alternate response location should be a location on the local workstation. Students must have full access to the designated “save locations.” When connectivity is restored and the students are resumed to continue testing, the locally saved responses are transmitted to the testing server and added to the responses already stored there. This activity occurs in the background of the test delivery software while the software continues to provide test questions to the student.

41 TestNav and TestHear Early Warning System 41 TestNav or TestHear will find the correct response file. A combination of the test ticket ID combined with the session token is used to uniquely identify a Student Response File (SRF). A SRF can only be used the next time the student resumes into a test. TestNav or TestHear will only delete a SRF if it just successfully uploaded it.

42 Reasons Why TestNav EWS Triggers 42 1)TestNav or TestHear client determines that neither Early Warning Save Location is viable. 2)TestNav or TestHear is unable to download portions of a test. The two above situations will result in immediate notification of the student. 3)TestNav or TestHear is unable to upload responses. This situation will result in notification of the student at the time of test submission.

43 TestNav Early Warning – Screenshots 43 Invalid Save Locations

44 TestNav Early Warning – Screenshots (contd.) 44 Invalid Save Locations

45 TestNav Early Warning – Screenshots (contd.) 45 Unable to download test content

46 TestNav Early Warning – Screenshots (contd.) 46 Unable to download test content

47 TestNav Early Warning – Screenshots (contd.) 47 Unable to upload responses

48 48 Unable to upload responses TestNav Early Warning – Screenshots (contd.)

49 49 TestHear login used in TestNav software TestNav Early Warning – Screenshots (contd.)

50 50 Invalid Save Locations TestHear Early Warning – Screenshots (contd.)

51 51 Unable to download test TestHear Early Warning – Screenshots (contd.)

52 52 Unable to download test content TestHear Early Warning – Screenshots (contd.)

53 53 Unable to communicate with server TestHear Early Warning – Screenshots (contd.)

54 54 Unable to communicate with server TestHear Early Warning – Screenshots (contd.)

55 55 TestNav login used in TestHear software TestHear Early Warning – Screenshots (contd.)

56 TestHear Software Version Error 56 If you have not downloaded and installed the latest version of TestHear on workstations, students will receive this error message when signing into the test.

57 Common Technical Errors/Solutions 57 Proctor Caching Configuration error – Looping Not pointed to a proxy server to reach the internet Pre-caching Not changing browser settings before pre-caching Java JRE not installed TestNav Windows Firewall – Allow javaw.exe in the TestNav folder Network Local Congestion Errors Test loads slowly Percentage indicator increments slowly Note: See the latest Technology Coordinator Guide for a table of common error codes and solutions for TestNav and TestHear.

58 Lessons Learned 58 Screen resolution must be set to 1024 x 768 on student workstations. Students must have full permissions to the TestNav/Temp, TestNav/Log, gh\TestHearPearson\Data folder. A primary save location must be set and students have read/write access to the save location. Screen savers, power management, and pop-up update notifications must be disabled on student workstations. Proctor Caching software must be installed and must be checked on each day of testing to ensure it is functioning correctly. Test content must be pre-cached prior to student testing. The test session must be started in PearsonAccess.

59 Contact Information 59 Pearson Support – 877-847-3043 – – Monday thru Friday, 7:00 am - 8:30 pm (EST) FDOE Bureau of K-12 Assessment CBT Specialists – Jenny Black, 850-245-9470, – Tracy Woodward, 850-245-0085,

Download ppt "Technology Coordinator Training FCAT/FCAT 2.0/EOC Computer-Based Testing."

Similar presentations

Ads by Google