Skip to main content

TestNav Lockdown Browser Installation

Daryl Weinstein
  • Updated

Sections in this article

 

Download TestNav

 

Set Up TestNav on ChromeOS

Pearson supports only managed Chromebooks for secure testing. Both before you install TestNav AND prior to each testing session, you should check each device to ensure it is in managed status.

To check the managed status of each device:

  1. When the student turns on the ChromeOS device, check the screen where the account icon appears. If the student has signed in to the device, instruct them to sign out to see this screen. 
  2. Below the account icon and the start arrow, a managed device will display the managed device icon ( Managed Device Icon.png) and the domain that manages it. The example below shows Chromebook managed by your-domain_here

Chrome_Domain.png

You can also see the managed icon at the bottom-right of the screen in the status bar before the student signs in to the device. The status bar includes the time, the managed icon (if managed), and more. Selecting anywhere in the status bar opens its menu, where you can also see that the device is managed.

Managed Testing Device.png

Assign the student a different, managed testing device or re-enroll the device as managed if: 

  •  The managed icon does not appear, indicating that the device is unmanaged. 

  • More than one account appears on the account icon page, indicating that the device might also contain an unmanaged profile.

 

Install TestNav

Add TestNav as a kiosk app.

Content filters and TestNav... 

If your content filters are activated when a student signs in to the Chrome device, contact Pearson Support for additional URLs to add to your kiosk settings for URL blocking. TestNav does not require that the student sign in to the Chrome device. As a result, these content filters do not filter as intended during a TestNav test.

Step-by-Step

  1. Uninstall the legacy TestNav Chrome App, if applicable.
  2. Install the new TestNav Web App for ChromeOS. This app is not available on the Chrome Web Store. It is installed using the Google Admin Console.
    • Sign in to TestNav
    • On the left side, navigate to: Devices > Chrome > Apps & extensions
    • Select the Kiosks tab at the top of the page.
    • Select the organizational unit for which you want the TestNav app & extension to be added. If you want to add for all users, select the top-level organizational unit.
    • Select the yellow + (plus) button at the bottom right corner to expand to see additional yellow buttons. Select the Add by url button and enter https://home.testnav.com/. 
    • Select Save. Google will then prompt you to allow permissions to this app. Select Agree.

Add by Url.png

  • The new TestNav Web App for ChromeOS appears in the app list.

Home TestNav.png

Select the TestNav app and scroll down the right-side bar to enable Allow new windows to open (full screen). 

New Windows Screen.png

  • Scroll down further on the right-side bar to Additional URL origins field to add the following URLs.  Note: Additional URLs must be added to allow the TestNav Web App for ChromeOS access to functions outside of the scope of the app URL.  

[*.]testnav.com 

adamexam.com

[*.]actonline.act.org

clever.com

[*.]classlink.com

[*.]schoology.com

[*.]act.org

[*.]actaspire.org

 

Additional URL.png

  • Scroll down further on the right-side bar to Extension section.
    • Click ADD EXTENSION and from the pop-up list, select Add from a custom URL and the Add Chrome app or extension by ID dialog box opens. 
    • Select From the Chrome Web Store, which will expand the menu to show an additional selection of From a custom URL. Select From a custom URL. 
    • Enter the following Extension ID and the URL and then click Confirm: 
      • Extension ID: gjhfdhjfmmgldldpmfdmbddbegbachgo 
      • URL: https://download.testnav.com/chrome-extension/update-manifest.xml

 

Add Chrome App.png

  • Click the SAVE button located at the top right corner.

Save button.png

  • The new TestNav Web App for ChromeOS and its extension will now be installed for users in the selected organizational unit as a kiosk app the next time they start their ChromeOS device. 
     

Running the App Check

After completing the TestNav installation, run App Check from the TestNav login screen to confirm that the device meets system requirements and has proper network connectivity.

App Check verifies that the device is prepared for testing and will display green indicators when all checks pass. If any issues are identified, follow the on‑screen instructions or use a different device if needed.

Running App Check in advance helps reduce the risk of disruptions during testing and ensures the device meets Pearson’s technical requirements.

 

Important Note for iPads

When running App Check from within the TestNav app on an iPad, you may see a browser‑related warning similar to the following:

iPad App Check Error.jpeg

This message can be safely ignored on iPads.

The browser check portion of App Check is not compatible with the TestNav iPad app, and the warning does not indicate a problem with the device or TestNav installation. TestNav will function as expected on iPads despite this message.

 

Verifying Lockdown Browser / Kiosk Mode Functionality

After installing the TestNav Lockdown Browser or configuring TestNav to run in kiosk mode, schools should verify that the secure testing environment works as expected before test day.

To confirm functionality, launch TestNav and start the Maine Science Student Tutorial - Kiosk Mode, Test Code: D66463. When configured correctly, the device should:

  • Launch TestNav in a secure, full‑screen mode 
  • Prevent access to other applications, websites, or device features
  • Display a confirmation message indicating the device is locked to TestNav
  • Exit locked‑down mode automatically when the test is submitted or exited

If the device does not lock as expected, or if students can access other applications while TestNav is running, the device should not be used for operational testing. Use a different device or review configuration settings before testing.

Validating lockdown or kiosk mode in advance helps ensure test security and reduces the risk of disruptions during live testing.

 

Log in to TestNav

  1. Power on the device, but do not log in. If before a secure testing session, check the device's managed status.
  2. In the lower left of the screen, select Apps > TestNav to launch TestNav.
    A message appears, informing you that you can use <ctrl><alt>s to exit Chrome OS when you first launch TestNav. This works only while the message displays. 

  3. If you have not already done so, scroll down on the list to choose the Maine tile. 

    Maine Tile.png

    TestNav Homepage.png

  4. Use a test ticket from your proctor to start your test. 
  5. After a test session has been submitted, start by clicking the Close button. Then, click the X in the top‑right corner of the screen to fully exit TestNav.
  6. In the unusual circumstance that a student needs to exit before completing the test session, there are a variety of ways depending on the device and the device setup.  If the most commonly used method doesn’t work, we recommend turning off the device.  In order for the student to resume the assessment they will need to be reseated by the proctor. Please note that each of the three Maine Science Assessment sessions needs to be completed on the day it was started. Incomplete sessions will auto-submit at 11:59 PM.

Related articles

Comments

0 comments

Article is closed for comments.

Powered by Zendesk