Florida Computer-Based Assessment District-wide Infrastructure Trial Training

1. Florida Computer-Based Assessment District-wide Infrastructure Trial Training Spring 2013

2. Clarification of On-line Test Content • Infrastructure Trial • Invalid sample of test-like material • ePat Practice Tests in TestNav and TestHear (accommodated forms) • FCAT 2.0 Reading (Grades 6, 7, 9, 10, and Retake) • FCAT 2.0 Mathematics (Grade 5) • FCAT Mathematics Retake • Algebra I End-of-Course (EOC) • Biology I EOC • Geometry EOC • US History EOC • Civics EOC • Full Test Content

3. Infrastructure Trial vs. ePat Practice Tests • Please remember that the content in the Infrastructure Test is NOT appropriate for student practice.

4. Infrastructure Trial vs. ePat Practice Tests (contd.) • Please remember that the content in the Infrastructure Test is NOT appropriate for student practice.

5. Infrastructure Trial:Schedule of Activities

7. PearsonAccess “Operational” and PearsonAccess Training Center • PearsonAccess (www.PearsonAccess.com/fl) • “Operational” BlueHeader • A website used for almost all test preparation (e.g., preID, test setup, administration, and reporting tasks. • Verify you are accessing the correct administration every time you log in. • Training Center BrownHeader • Access the Training Center Tab on the PearsonAccess home page • Provides an opportunity to practice PearsonAccess tasks and means of managing the Infrastructure Trial Note: User accounts are required for school assessment coordinators to access both sites. Technology coordinators can work with school assessment coordinators to access sites, as needed.

8. SCHOOL ASSESSMENT COORDINATOR RESPONSIBILITIES

9. Before Trial: Creating Sample Students • Sample students must be created within the Training Center in order to administer the Infrastructure Trial. • Not actual students in your school • The number of sample students to be created should be based on the maximum number of computers that will be used concurrently during testing. • Creating at least ten percent more students that you plan to test concurrently to have extra Student Authorization Tickets in the event of any login complications. • Each ticket is valid for one login attempt, unless the student is resumed in PearsonAccess. • Instructions for resuming students are provided on pages 21-23 of the Infrastructure Guide.

10. Before Trial: Creating Sample Students • 1. Log in to the Training Center. • 2. Go to the home page and click Create Students. • 3. Ensure that you see your school listed under the Organization drop-down menu.

11. Before Trial: Creating Sample Students (contd.) • 4. Next, you must • designate a CLASS NAME (create a new class or select an existing class from the drop-down menu) and USE ALL CAPS • test name (Florida Infrastructure Trial), and • the number of sample students you would like to create. Up to 99 sample students can be created at a time. • 5. Click Create Students

12. Before Trial: Creating Sample Students (contd.) • 6. A prompt will then appear to continue with creating students. Select Yes – Create Students to continue, or No – Cancel Create to cancel. • 7. A confirmation screen will appear once the sample students have been created. • 8. Repeat the steps above until you have created sample students for the number of computers that will be tested concurrently, plus at least 10% additional students.

13. Before Trial: Creating a Sample Test Session • 1. In the Training Center, Go to the Test Management tab and click on Manage Test Sessions. • 2. Click on New Session. • 3. Enter the Session Name, School, Test to be Administered (“Infrastructure Trial”), Default Form Group Type (“TestHear Reading Test” or “TestNav”), Scheduled Start Date, Scheduled Start Time, and Location/Room. Entering a date and time for a session is for planning only. A session has to manually be started on the Session Details screen.

14. Before Trial: Creating a Sample Test Session (contd.) • 4. Click View By: Classes to see a list of classes. Click the box next to the name of the class to be added. (View By: Students can also be used and individual students can be selected.) • 5. Click Save to create the session. A confirmation page will be displayed once the session has been created.

15. Before Trial: Printing Student Authorization Tickets Authorization tickets include a Login ID and test code for each individual sample student. This information is necessary in order to log in to the Infrastructure Trial. • 1. In the Training Center, go to the Test Management tab and click Manage Test Sessions. • 2. Click the session name to go to the Session Details screen for that test session. • 3. To print authorization tickets, click on Authorizations > Student Authorizations and then select the format in which you would like to download tickets. • The authorization tickets can be downloaded in three different formats: Detail View, Grid View, and List View. • a. Detail View only shows one authorization ticket per page. • b. Grid View shows six authorization tickets per page in a three row/two column layout. • c. List View displays three authorization tickets per page separated horizontally.

16. Before Trial: Printing Student Authorization Tickets (contd.) • Once you have selected the file you want, open it and print the authorization tickets. Note: It is strongly recommended that you select one format and use it consistently at your school.

17. Before Trial: Printing Seal Codes (TestNav Only) • 1. In the Training Center, go to the Test Management tab and click Manage Test Sessions. • 2. Click the session name to go to the Session Details screen for that test session. • 3. To print seal codes, click on Authorizations > Seal Codes. • 4. Open and print the seal code.

18. Before Trial: Configuring Browser Setting for Caching Content (Technology Coordinator) • Once the Infrastructure Trial test session has been created, content can be cached. • Notify your technology coordinator to Configure the Browser Setting for Caching Content and cache the content (see instructions in Technology Coordinator Guide posted at www.PearsonAccess.com/fl under Support tab. Disregard any references to completing tasks in PearsonAccess; the Infrastructure Trial is managed via the Training Center.

19. Before Trial: Configuring Browser Setting for Caching Content (Technology Coordinator) • 1. The Proctor Caching Software must be enabled and running. • 2. The Web browser must be configured (see Technology Coordinator Guide). • 3. Java version 1.4.2_, 1.5.0_x, or 1.6.0_x must be installed. (A caching applet requires a Sun-compatibleJava Plug-in to run. To determine your Java version, visit http://javatester.org and click “Test the version of Java your browser is using.” Once clicked, your Java version will appear in a pink box. Go to http://java.sun.com to download a newer version, if necessary.) • 4. Pop-ups must be enabled for etest.pearson.com. • 5. The site https://www8.etest.pearson.com should be added to the list of Trusted Sites in your browser.

20. Before Trial: Configuring Browser Setting for Caching Content-Windows (contd.) Important Note: • The test content cannot be cached from the Proctor Caching computer; instead use any other computer on the same network as the caching computer. • In order to cache a test, change the proxy settings within the browser using the applicable set of instructions based on the browser you are using. The proxy settings only have to be changed on the computer being used to cache test content. The browser settings do not need to be adjusted on the student workstations. Take note of proxy setting in your browser; after caching, you will need to change your setting back to resume access to internet sites. • The Infrastructure Trial is now ready to be cached.

21. Before Trial: Caching Test Content • Log in to the Training Center and navigate to Test Management > Manage Test Sessions. Select a session to cache and click on the Session Name to go to the Session Details screen. Then click the Proctor Caching button. • Then, a page will be displayed with instruction, click Next.

22. Before Trial: Caching Test Content (contd.) • A page will be displayed with the contents to be cached. Click Next. • A page will then be displayed showing the progress of the caching process.

23. Before Trial: Caching Test Content (contd.) • After all test items have been retrieved, the status page on the workstation used to cache test content will present a confirmation message. • At this point, the Proctor Caching computer is ready for the Infrastructure Trial. Click Return to Session Details to return to the Session Details screen. • Note: The main reason a test may not be cached properly is if Pearson’s sites have not been allowed through a district’s or school’s content filter or firewall. Refer to the Additional Configuration Requirements section of the Technology Coordinator Guide pages 33–37 for instructions on allowing Pearson’s sites through content filters and firewalls.

24. Before Trial:Starting a Test Session The session must be started before sample students are able to log in to the Infrastructure Trial. • 1.In the Training Center, go to the Test Management tab and click Manage Test Sessions. • 2. Click the session name to go to the Session Details screen for the test session. • 3. Click Start in the top left corner of the Session Details screen. • 4. A confirmation screen will appear. Select Yes – Start Session to start the session or No – Cancel if you don’t want to start the session yet. • 5. A confirmation page will be displayed once the session has been started successfully.

25. Conducting the Infrastructure Trial • Volunteers log in to complete the Trial test. • Volunteers will simulate the testing process. • Students or adult volunteers can be used - not necessary that computer-based testing students are used. • Trial is NOT appropriate for student practice. • One volunteer can log in on multiple computers (5-8 tickets per volunteer is recommended) because volunteers supply a random answer every 10 seconds. • Once Student Authorization Tickets have been designated for each volunteer and seal codes have been posted (for TestNav Infrastructure Trials), call the volunteers into the room. • Ensure that volunteers sign into TestNav or TestHear according to which software you are using for the Trial. • They will need to be in the correct session and assigned the correct Form Group Type to be able to successfully sign into the software (see pages 13-14 in the Infrastructure Readiness Guide). • Once the Infrastructure Trial has started, a volunteer must log into each computer to be used for testing. • Each volunteer should be provided a pen or pencil to log issues on back of the Student Authorization Tickets. • Use the script provided in the Infrastructure Readiness Guide pages18-20. • Estimated time for Trial is approximately 30 minutes.

26. Launching TestNav 6.9 • TestNav 6.9 is launched by double-clicking the TestNav 6.9 icon on the desktop. • Enter the URL for the Infrastructure Trial in the Address line. This URL can be found on the Student Authorization Tickets. (Note: The URL is case sensitive.) • Click Go and TestNav will present a login page.

27. Logging in to the Infrastructure Trial via TestNav • Enter the Login ID and Test Code and click Login. • TestNav will load the test items and the welcome screen will appear.

28. Launching TestHear • TestHear is launched by double-clicking the TestHear icon on the desktop. • Enter the URL printed on the Student Authorization Tickets and click GO to proceed to the student login screen.

29. Logging in to the Infrastructure Trial via TestHear • Enter the Login ID and Test Code and click Login. • TestHear will load the test items and the welcome screen will appear.

30. During the Trial:Monitoring Test Sessions • Once a session has been started, there are a number of actions that may need to be carried out in order to complete the Infrastructure Trial. • These actions may include: • resuming sample students, • resuming sample students with saved responses, and • marking tests in completed status.

31. During the Trial:Monitoring Test Session (contd.)

32. During the Trial:Resuming a Student • 1. To resume a sample student, go to the session page and check the box next to the Student Name that needs to be resumed. Then click Resume Test.

33. During the Trial:Resuming a Student (contd.) • 2. After Resume is clicked, a confirmation page will display. Select Yes – Resume Tests to start the session or No – Cancel if you don’t want to resume the student yet. • 3. Another confirmation page will be displayed once the student has been successfully resumed. • 4. Go back to the session page and the student’s status will now show “Resumed” and the sample student will now be able to log back in to the session. • 5. If a student logs back into the test, but none of their responses appear, the student will need to exit the test again. • In order for the responses to be populated again, the student will need to be marked in “Resumed-Upload” status. • To mark the student in “Resumed- Upload” status, the student will need to be resumed twice.

34. During the Trial: Common Error Codes / Solutions

35. Exiting the Infrastructure Trial • Once all test items have been viewed and tools have been tested in the Infrastructure Trial, the test can be submitted. • Submit the test by clicking click Submit, “Yes, submit my test” and Yes once more. • Responses will now be submitted and the student status will show as “Completed” on the Session Details screen.

36. After the Trial: Stopping the Test Session • 1. Before a session can be stopped, students must be either in “Completed” or “Marked Complete” status. To stop the session, select Stop in the top left corner of the session page. • a. To mark a student’s test complete, the student must be in “Exited” status. • b. Go to the session page and check box beside the student to be marked complete. • c. Click Mark Test Complete. • d. A confirmation page will be displayed and the student’s status will now show “Marked Complete”. • 2. After Stop is clicked, a confirmation page will display. Select Yes – Stop Session to stop the session or No – Cancel if you don’t want to stop the session. • 3. Another confirmation page will be displayed once the session has been stopped successfully.

37. After the Trial: Purging Test Content (Technology Coordinator) • Notify your technology coordinator to purge test content • To purge test content (Windows): • 1. Go to Start > Programs > Proctor Caching > Purge Cache. • 2. Click Delete to confirm that you would like to purge the contents of the cache.

38. After the Trial:Infrastructure Trial Survey • To assist Pearson and the FLDOE to identify areas of need and to direct resources and support • One representative (School Assessment Coordinator or Technology Coordinator) from each school: • Review all notes on Student Authorization Tickets to provide school-level response • Provide feedback to District Staff by completing a comment form online available at http://www.surveymonkey.com/s/3C2MLX3 by April 3, 2013.

39. COMPUTER PREPARATIONS SCHOOL TECHNOLOGY COORDINATOR

40. Proctor Caching – Network Diagram

41. Proctor Caching – How does it help? • Proctor Caching allows you to 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.

42. Test Delivery – Local Installation • Download and install TestNav 6.9 and/or TestHear on each workstation used for Test Delivery. • Configure each machine to communicate with the Proctor Caching machine. • More challenging to manage than a server installation. • System automation tools like SMS (Windows) and Apple Remote Desktop (Mac) make local installs much more practical.

43. TestHear Installation Best Practices • The updated TestHear software (released September 13, 2012) must be downloaded to each workstation that will be used for accommodated forms • Available at: www.FLAssessments.com/Downloads • Review minimum specifications • TestHear can only run on computers using Windows or Macs that are running Windows • Only local installation is available for TestHear

44. TestNav/TestHear Installation Best Practices Each student user profile to be used for testing must meet the following requirements: • Enable student permissions. • Students must have read-access to the TestNav or TestHear installation directory. • Students must have full permissions for the TestNav\Logs and TestNav\Temp directory. • Students must have read- and write-access to the Student Response File save locations whether they are located on the workstation or on a network share. • Students who will be testing using the TestHear software must have full permissions to the TestHear C:\Program Files\gh\TestHearPearson\Data directory.

45. TestNav/TestHear Installation Best Practices • Configure applications that launch automatically. • Ensure that any monitoring software (e.g., LanSchool, Altiris, Netop, SynchronEyes) that would allow student workstations to be viewed from another computer during testing is turned off. • 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 (low battery warnings), • Screen savers, and • Email with auto message notification. • Disable Popup Blocking Software (for PearsonAccess) • A pop-up blocker will block the pre-caching screens from opening on administrative workstations.

46. TestNav/TestHear Installation Best Practices • Set screen resolution. • All tests are authored to a screen resolution of 1024 x 768; ensure that your testing machines are capable of 1024 x 768 resolution, and set testing workstations to this resolution. • Screen resolutions below this setting will cause an error as TestNav tries to load the test. • Screen resolutions above this setting will be auto-adjusted in TestNav to 1024 x 768 as the test loads for the students. If the test does not cover the entire desktop, the screen turns black, or you receive an “out of range” error message, follow the steps below for disabling the auto-adjust screen resolution feature. • TestHear does not resize the screen resolution, so monitors should be adjusted to 1024 x 768 prior to testing.

47. TestNav/TestHear Installation Best Practices 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.

48. TestNav/TestHear Installation Best Practices • Configuration for Specific Proxy Environments • The TestNav 6.9 proxysettings.properties file is the only configurable settings file. This file can be edited with Notepad or TextEdit. • Editable variables in proxysettings.properties: • 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

49. System Check for TestNav 6.9 • The TestNav 6 tab provides instructions for verifying that TestNav has been installed and configured correctly. TestHear configuration cannot be verified using the instructions on this tab. • The Network User Capacity tab is used to test the bandwidth among student testing workstations, the Proctor Caching computer(s), and Pearson servers. This tool will provide an estimate of how many students can be tested on the designated Proctor Caching computer. • The Testing Volume Calculator tab is a tool for estimating how many students are able to test concurrently while taking the amount of available bandwidth and network traffic volume into account.

50. System Check for TestNav 6.9 • The following steps will guide you through the process of using System Check for TestNav 6. • 1. Click the TestNav 6 tab and follow the instructions provided. • 2. Once you see the “Congratulations” screen in the TestNav window, click the Network User Capacity tab.