Achievement District Test Coordinator Updates for AASA and AzSCI - March 11, 2024 |
Achievement District Test Coordinators (DTCs),
Please save this email to reference during the AASA and AzSCI test windows for troubleshooting tips and test irregularity guidance. The details included in this email are specifically for AASA and AzSCI. For technical issues or other assistance for ACT or ACT Aspire, please use the following contact information during the test windows.
ACT Aspire - Contact Pearson at 1-888-705-9421, Option 4
ACT - Contact ACT at 1-319-337-1567 (this is an Arizona-specific number)
- General Questions: 1-800-553-6244, Ext. 2800
- Accommodations Questions: 1-800-553-6244, Ext. 1788
Contact Pearson for AASA or AzSCI Customer Support:
AzSCI - 1-888-705-9421, Option 1 (For technical assistance, ask to speak with Level 2)
AASA - 1-888-705-9421, Option 3 (For technical assistance, ask to speak with Level 2) |
TestNav Information
If you experience "The installed app is out of date" or "TestNav has detected another application," please update and/or disable programs following the instructions below.
Minimum Version Requirements for TestNav during Spring 2024 Testing
Please use the following link for the most current TestNav version information:
- The TestNav app automatically updates when it is opening in the following OS:
- Chrome
- iOS
- Windows (from the store)
- Manually download from download.testnav.com for the following OS:
- macOS
- Linux
- Windows (if downloaded directly from download.testnav.com
TestNav Installation and Sign In
Pearson offers instructions for various OS to install and sign into TestNav.
Disabling Programs and/or Applications Prior to Testing
- App Check can be found on the TestNav sign in page.
- App Check confirms the device/computer can connect to TestNav and is configured to start TestNav in kiosk mode.
If there is Lag in TestNav:
- Check to see if the devices being used are wireless. This could cause a strain on the system, depending on the number of students testing at one time. There may be a limit on the wireless access point. It may be possible to spread students throughout the building so different access points can be used.
- If a minimal number of students are testing, even on Wi-Fi, have IT personnel check to see if there is a content filter or packing shaping / QoS (Quality of Service) solution in place.
TestNav Error Codes (when "kicked out" of testing)
Use the link above to view error messages and information about how to resolve the error. The most common error codes are in the following ranges.
- 1000s: Connectivity-based issues, often experienced when students encounter lag or are kicked out of testing.
- 3000s: Application errors, often in conjunction with connectivity errors
|
Exiting the Test
Student Test Exited and Resumed
Student Signs out of TestNav - To exit a test for a bathroom break or an emergency, the student must sign out of TestNav prior to leaving the room. To exit the test, the student clicks on the Save and Return Later button. The Test Administrator will need to resume the student's test in PAN before the student signs back into TestNav. (See Test Administration Directions)
Student Test Completed - Final Answers Submitted
Student in "Completed" Status - Student has completed and submitted the test unit. The test unit will not be eligible to be reopened. Before students submit their final answers, they can go back and review the questions that are unanswered. The screen "Exit Warning" will show. Once the test is submitted, it cannot be reopened. |
Most Common Achievement Test Security Violations to Avoid
- Personal electronic devices, including but not limited to cell phones, smart watches, and other electronic devices, are the single largest source of test security violations. Students are not permitted to use resources on the Achievement tests. The use of unacceptable resources during testing is a test security violation and will result in the student's test being invalidated. Unacceptable resources, including but not limited to unacceptable reference materials, cell phones, Bluetooth headphones, smart watches, or other electronic devices, must be removed.
- Testing tickets contain student information and should be treated as secure test materials. Do not allow students to test with incorrect testing tickets. Students provided an incorrect testing ticket for AASA or AzSCI will not have the option to reset test. The use of an incorrect testing ticket is a test security violation and will result in the student's test being invalidated. Testing tickets are considered secure test materials and must be stored securely when not in use.
- Test Administrators may not log into TestNav as a student, except in the case of Special Paper Version tests where the Test Administrator must key enter student responses into TestNav.
- Group or class stretch breaks are not allowed. Students cannot be stopped from testing by the Test Administrator for a stretch break. Once a class leaves the testing room, the test session will be over. This would exclude an emergency or other unusual situation that occurs during testing. Students may not leave a test session to attend lunch until the completion of the test session; however, students may have their lunch brought to them, if necessary.
- Providing unacceptable accommodations to students who may receive accommodations, providing accommodations to students who may not receive them, or failing to indicate that accommodations were provided are test administration errors.
- All visual aids displayed in the testing room that could assist students while testing must be removed or covered completely. Any motivational signs for testing must be removed or covered completely.
- Calculators are permitted on AASA Grades 7 and 8 Math Unit 1 only. Calculators are permitted for AzSCI testing as outlined in the Calculator Guidance.
|
Follow these steps to report an AASA or AzSCI Testing Violation:
- Test Administrators should record the incident and allow the student to continue testing. Do not allow the student to leave the testing environment.
- Test Administrators should be instructed to report any test irregularity that may arise during testing to the School Test Coordinator immediately.
- The School Test Coordinator must notify the Achievement District Test Coordinator of any test irregularities that are reported.
- The Achievement District Test Coordinator must report the incident within 24 hours by logging into PearsonAccess Next and entering the test irregularity in the Student Tests tab > Manage Irregularities task on the student's test attempt. Indicate what happened that caused the test irregularity. Refer to the PearsonAccess Next User's Guide for detailed instructions to submit a test irregularity.
- ADE will review the test irregularity submission in PearsonAccess Next.
- ADE will email the Achievement District Test Coordinator with any initial questions, if needed.
- Once the test irregularity is reported in PearsonAccess Next, ADE will review it in the system and will add a comment in PearsonAccess Next if a test is invalidated.
- District Test Coordinators should use the Do Not Report Tests operational report in PearsonAccess Next to check if a test unit has been invalidated.
- One week after the test window closes, a final Do Not Report Tests operational report can be run for a school or district. If a submitted test irregularity is not on the final report, then the test unit was not invalidated.
|
Bethany Spangenberg
Deputy Associate Superintendent of Assessment
Arizona Department of Education
|
|
Joseph M. Guzman, Ph.D.
Associate Superintendent of Standards, Assessment, Accountability and Research
Arizona Department of Education |
|
|
|
|
|
|
