[UPDATE 2015-05-13]: Pearson is getting DDoS’d again.
Pearson experienced intermittent issues with PearsonAccess and TestNav beginning at 7:13 a.m. this morning. These issues continue to occur.Pearson has confirmed that a Distributed Denial-of-Service (DDoS) attack to Pearson?s firewall is causing degraded performance issues. Pearson is actively monitoring the issue and working to resolve.
[UPDATE 2015-05-05]: Don’t use full screen with TestNav. See below from Pearson:
…If the browser is set to Full Screen mode prior to students logging in, it will create a conflict with TestNav that may cause students to experience difficulty logging into their tests, being exited from TestNav unexpectedly or cause students to not be able to use built-in tools. This applies to all browsers on all operating systems…
Minnesota Department of Education Temporarily Suspends Minnesota Comprehensive AssessmentsEducation Commissioner Brenda Cassellius announced today that the state will temporarily suspend administration of the Minnesota Comprehensive Assessments, until all technical problems with the testing system are resolved.Over the past week there have been three days during which students have experienced issues logging into the testing system. The testing window has been open since March 9 without major incident, with nearly 400,000 tests completed. As the number of students testing neared its peak today, Pearson has identified some technical problems with their system and are currently working to resolve them. These technical problems have not adversely impacted the 400,000 tests that have already been completed.“Students already give up precious instructional time for annual accountability tests,” said Cassellius. “We cannot allow these disruptions to further impact student learning.”Pearson is working on identifying the technical issues that are causing the problems. The department has informed Pearson that testing cannot resume until they assure the state that students will encounter an error-free and smooth testing experience.“We hold our students to high standards and we expect no less of Pearson. Students deserve a worry-free testing experience without interruptions,” said Cassellius.
[UPDATE 2015-04-21]: In addition to the problems we face every day on our end, Pearson is having trouble, too.
At approximately 08:55 AM Central Time on 4/21/2015, Pearson detected that the TestNav online delivery system was registering an unknown issue resulting in degraded test delivery. Primary symptoms of this condition included user difficulty in logging on, slow test item download, slow test submissions, and a warning screen to notify their teacher or test proctor.
While such conditions are frustrating, online testing may continue at this time. Iowa City Technology Operations is working diligently to correct the issues.
[Update 2015-04-15]: Java 8u45 and Flash 184.108.40.206.
[UPDATE 2015-03-16]: Java 8u40 has been updated to Java 8u40.
[UPDATE 2015-03-13]: Flash 220.127.116.11 is out. Hooray. X-protect hasn’t been updated yet, but I’m certain it will soon, at which point TestNav will break.
[UPDATE]: Pearson recently discovered that an active Dropbox sync process, including those that may be running in the background, will cause a 7037 error when TestNav attempts to launch.
[UPDATE]: Useful resource: TestNav Error Messages.
[UPDATE]: Download the Safari.plist, which can be used to create a Configuration Profile. This is the .plist I use in my environment. You may need to run this command before uploading it:
plutil -convert xml1 ~/Downloads/com.apple.Safari.plist
The .plist has the settings to
- let the TestNav URLs to run in unsfafe mode
- disable Autofill
- allow pop-ups
[UPDATE]: Xprotect disables all but the latest version of Flash (18.104.22.1686), so if you do not have that version installed, you may end up with Message 7037: Internal Communication Error.
[UPDATE]: Representatives from Pearson, Apple, the Minnesota Department Of Education (MDE), as well as technology staff from school districts attended a meeting today to discuss the issues with TestNav, Java, and the Safari “unsafe mode.”
Here are the highlights I heard while listening via Webinar:
- A config profile can be created to allow Java to run in unsafe mode but this does not disable the “Do you want to run this Java applet” dialog; it just eliminates the “Trust this site” sheet that Safari displays
- System Check tool has been updated
- TestNav documentation won’t be overhauled for spring, but it is planned
- TestNav 8 (2015-16) is being built from the ground up and has “mobile-first” design
- does not need Flash or Java if using the app
- will work on Chromebooks
[UPDATE]: Calculator crashing your test? Pearson won’t fix it, but here is their solution:
There has been an issue reported when using the calulator [sic] during testing. Sometimes the test will hang or crash if the calculator is opened and the next button is selected soon after. Pearson recommends that the calculator be closed before student’s press the next button.
[UPDATE]: Disable Java updates via script
[UPDATE]: MDE reps will meet with school technology staff at TIES.
[UPDATE]: Pearson released a PDF saying they understand people are having difficulty with TestNav and are holding seminars about how to use the software. Nothing yet on a fix.
[UPDATE]: The Java exception list script no longer seems to work on the new versions. The System Check was 22.214.171.124 at the time of this article and now it is 126.96.36.199. I tried modifying the script a few different ways, but to no avail. The actual TestNav site also has an updated version. Maybe the hack no longer works.
If possible, you should get a signed certificate and create a DeploymentRuleset.jar (well-worth the price)!
[UPDATE]: Even though Chrome became supported by Pearson, you will still have issues because Google is eliminating NPAPI plugins, but you can work around them.
[UPDATE]: Update your Flash again.
[UPDATE]: There is an article in the Pioneer Press about the hardships with Pearson’s TestNav
[UPDATE]: I wrote a post on how to set up TestNav for Windows machines
[UPDATE]: Pearson posted a technical bulletin detailing the manual steps of getting their software to run.
Minnesota gave Pearson a $33.8 million contract for student testing, but their Website/software, TestNav, is a hardship for the technology staff getting it setup. It uses both Java (outdated version) and Flash. Just trying to go to the site or run the TestNav System Check, you are prompted with a bunch of annoying dialogs:
I recently had to set up over 500 computers for this test and I wasn’t about to spend my time going around to each computer, logging in, navigating to the site, clicking through all the dialog boxes, and then running the system check. And if I just left it as-is, students would not be able to log into the test, or they might click “Never trust this site,” which would just make problems worse. I also wanted to run the system check prior to testing to make sure the computers would work before the students arrived. All of this was repetitive and mundane, which humans are not good at–but computers are.
Best Option (Buy A Signed Certificate And Create A DeploymentRuleset.jar)
This has worked very well for our district.
- Create a signed DeploymentRuleset.jar with all the Java exceptions for the TestNav site
- Create a config profile using this Safari template, which allows the site to run in unsafe mode
- Optionally, create a Bookmarks.plist with the TestNav sites (cannot be made into a config profile)
Free Option (Complex Shell Scripts)
- add the URLs to the Safari exception list (set to run in unsafe mode)
- add the URLs to the Java Control Panel exception list
- log into the GUI from the login window as the student user
- if the Java and Safari exceptions scripts don’t work, click through the warning dialog boxes that appear saying things like: “Trust this developer,” “Run this applet,” or “Ignore this update.”
This is certainly not easy to do, but was better than spending a few days going around to each computer to do this manually. Plus, my computer labs were already set up for GUI scripting. There might be easier methods of doing this, but here is what I did.
Add TestNav To Java and Safari Exception Lists
This is really the crux of the issues with TestNav–getting the warning dialogs to never show up. I strongly recommend using a signed DeploymentRuleset.jar if possible as it will save you a massive headache, but if your District won’t do that, you can try to use the scripts provided below to dismiss the dialogs.
This script will add the URL TestNav URLs to Safari’s exception list and set them as “Run in unsafe mode.” You may need to adjust the username or additional URLs per your environment.
I tried to just open the URLs I needed on one machine and manually added them to the list, then looked at the Safari .plist to determine what URLs should be included in the script.
This script (modified from Rich Trouton’s script) will add the TestNav URLs to the Java Control Panel exception list. The domains in the script below are the ones we deployed in our DeploymentRuleset.jar, but there may be others you need to add.
Another Java Problem
TestNav relies on Java to work, but Oracle is always updating it. So if they happen to release an update during a testing session, the pop-up can disrupt the test while students are taking it.
Upon receiving this pop-up notification, TestNav immediately closes the testing session. To resume testing, an administrator must accept the update. The test monitor must then resume the test-taker’s session in the testing administration platform before testing can resume.
but they do not offer an automated solution to disable updates.
It is issues like these that makes it difficult to believe Minnesota dished out 33.8 million for this software. To avoid this, you can run this script (as root) to disable Java from checking for updates automatically.
How-to Automate More Of This Process
To be sure things are working, you may want to log into the System Check Website to make sure it will work for students. If you want to check this on a lot of computers, automation is the way to go. If you got the Java and Safari exception lists working, you have already saved yourself a ton of time. But if you are looking to do more automation and verification, you will need a few things:
- tccutil.py (optional, but helpful if using Mavericks or Yosemite)
click( direct download) click or MouseTools
- Apple Remote Desktop
Install Utilities To Lab Computers
On the computers that will be running the test, install tccutil.py and click , using your Desktop Management software. We use Casper, so I just made two packages using Composer that install the utilities to /usr/sbin and /usr/bin Once the software is on the computer, you will be able to use them via ARD. You will need to make sure the utilities are executable by running these commands as root:
chmod 755 /usr/sbin/tccutil.py chmod 755 /usr/bin/click
Enable Access To Assistive Devices
This is what allows you to script the GUI login, click buttons, open windows, and perform other GUI tasks. Without this step, you won’t be able to click the dialog buttons as easily or instruct the computers to open the URL and type in the username. You will also not be able to send a UNIX command to log a user in from the OS X Login Window.
Snow Leopard through Mountain Lion
If you are running 10.6-10.8 you can enable this on each computer with a single command sent as root through ARD’s Send UNIX Command:
sudo touch /private/var/db/.AccessibilityAPIEnabled
Reboot to apply the change and you are ready to go.
Mavericks and Yosemite
Starting in 10.9, these settings were moved to a per-app basis, so each app that needs access, must to be added manually by dragging-and-dropping the app into the Accessibility tab under Security & Privacy settings within System Preferences. But don’t worry, you can automate this, too, thanks to tccutil.py. Just run these commands as root from ARD once the utility is installed:
/usr/sbin/tccutil.py --insert com.apple.systemevents /usr/sbin/tccutil.py --insert com.apple.RemoteDesktopAgent
Alternatively, you can run these commands (as root) without installing tccutil.py, but they are a little more complex and more prone to error.
sqlite3 /Library/Application\ Support/com.apple.TCC/TCC.db "INSERT INTO access VALUES('kTCCServiceAccessibility','com.apple.systemevents',0,1,1,NULL);" sqlite3 /Library/Application\ Support/com.apple.TCC/TCC.db "INSERT INTO access VALUES('kTCCServiceAccessibility','com.apple.RemoteDesktopAgent',0,1,1,NULL);"
Log In As The Student User
The rest of the settings are user settings, so it will be easiest to just log in as that user on each computer, then the commands can be as from ARD as the current user. Use the script below, sent via ARD as root, while the computers are at the loginwindow, to log in the user (adjust the username and password per your environment).
osascript -e 'tell application "System Events" keystroke "student" keystroke tab keystroke "student" keystroke return keystroke return end tell'
I have found that this works best right after a reboot so that the cursor is focused on the username field. There is also no screensaver to contend with.
Run System Check
The system check will not detect Flash (even though it is installed) until the URLs are added to the exception list and Java is working properly.
Open the System Check URL
Run this script as the current user via ARD. It will open Safari and navigate to the System Check URL.
Click the Start Button
This is where the click program comes in handy. It will click at an X, Y coordinate. This means you don’t have to go to each computer and click the start test button. Fortunately, all of my Macs had the same screen resolution, so it was easy to set a static coordinate to click.
Finding the Coordinates to Click
You can use the screenshot tool to find out where to click on the screen. Just press Command+Shift+4 and you will get a little crosshair. Hover over the place where you want to click and take note of those coordinates. Press Escape when done. If you are using MouseTools, you can find the coordinates of the mouse by running this command:
which will return an X and Y coordinate. Useful if you can not see the little crosshair that easily.
Open Sample Test Site
If the system check passed, you may want to open a sample test site to verify functionality. Use the script below to do this. You can use the other script to enter the test user credentials.
Open the Real Test Site (And Bookmark It)
Next, you will probably want to open the real testing URL and bookmark it so students can get back to it easy without your assistance. Or you can try sending out the bookmarks via a script:
If The Spinning Indicator Never Goes Away…
If you get the endless spinning indicator the most likely cause is that the sites are not configured in the Java exception list properly. You may also get this error message:
7022 – “Failed to load applet. Your test administrator will need to make sure this computer is running the correct versions of necessary software and try again.”
The error or spinning dialog could also mean the site is not on the “run in unsafe” list, but you may also need to empty the Java cache (per Pearson support). I did so with this command:
find /Users/student/Library/Application\ Support/Oracle/Java/Deployment/cache -type f | xargs rm
I’m not sure if this helps or not, but I also delete any Java-related files from the regular cache folder.
find /Users/student/Library/Caches -name *java* | xargs rm -rf
I have also started getting this error dialog after emptying the cache (even emptying it manually). Pearson support said to add the root domain to the exception list, which is already implemented in the script provided earlier.
Disable Java Cache
You may want to just completely disable Java cache to try and avoid these problems. I tried scripting this, but the setting seems to disappear after a reboot on my machine running Mavericks.
Chrome is supported according to Pearson, but since Chrome is disabling NPAPI plugins (Java) it’s probably not a good idea to invest your time into it. However, here is what you can try.
If you are using Chrome , you will need to deploy a .plist to allow Java to run (and allow pop-ups). However, since Google is disabling NPAPI plugins, using Chrome may not be the best choice. You can copy the file, or deploy it using a script (run as root) like this:Once deployed, open Chrome and navigate to chrome://policy. Your settings should show up here if it was successful.
Opening The URLS
There is only a slight difference in using Chrome to open a URL:
# Open system check site killall Safari > /dev/null osascript -e 'tell application "Google Chrome" open location "https://proctorcaching.pearsonaccess.com/ems/systemCheck/systemCheck.jsp?acc=mn" end tell'
Below is a screenshot of the workflow I use in ARD using saved templates. Each one runs the scripts from above so I can quickly deploy it to the computers necessary.
Jeffery Johnson came up with a similar process, but instead of scripting everything, he just packaged everything up and deployed it to the machines (download files):
- Testing user is logged in as testing account.
- Launch the TestNav app built by me that executes a shell script…
- Verifies Java and Flash version and then copies and overwrite the Java and
- Safari settings to work as needed and the launches the testing URL
- Login as testing user, go through the motions and verify testing is
- with correct browser and Java settings. You can use the temp testing URL
- I do the above so I don’t run into hiccups later on.
- I used an app such as InstallEase or Composer to automagically capture the
changed items needed… They can be grabbed them manually too.
- You can get an idea what to from the scripts ToInstall.sh