TestNav System Requirements
For details on most recent support changes, see the Recently Updated page.
These reflect minimum and recommended requirements; however, some customers slightly vary requirements for their specific organizations. TestNav does not prevent usage of older OS versions. Our team will provide full support to organizations that find the need to use an older OS that is not listed below.
Hardware Requirements (2024-25 School Year)
Do not use devices that take 10 seconds or more to start/run applications.
Requirement | Details |
|---|---|
Processor | x64 - AMD, ARM, ARM64, or Intel™-based* |
Memory | 4 GB RAM; Minimum - 2 GB RAM Linux and iOS - 2 GB RAM; Minimum - 1 GB RAM |
Screen Size | 9.5-in |
Resolution | 1024 x 768 |
Other | - External keyboard and mouse (or touchpad) for touchscreen devices
- Local File access to home directory
- Wired keyboards (recommended) - Tablet mode not supported |
Virtual Environments
| |
*Devices with ARM-based processors running Windows must be running Windows 11 to install TestNav.
Software Requirements (2024-25 School Year)
Annually, Pearson updates support requirements based on the TestNav System Requirement Policy. Districts should use this policy to determine annual purchasing needs and prepare devices. See Upcoming Support Changes below this section for more info on coming changes.
Use supported operating systems as they appear on this page. Attempting to use an unsupported or beta version of an OS can result in TestNav error, as well as security issues during high-stakes tests. Pearson tests all beta and newly released OS versions to ensure functionality and security with TestNav BEFORE support is added in the tables below.
We understand many of our customers are automatically downloading Chrome OS versions as soon as they become available. Due to Chrome OS frequent release cycles, Pearson continually tests beta versions of Chrome OS to efficiently add support. Any concerns with early testing will be communicated via a Technical Bulletin. We do not recommend betas to be used for interim or summative testing. See Beta Testing In-Progress section below for betas currently being tested.
TestNav Apps (kiosk-mode available)
When necessary for some tests, TestNav apps can run in kiosk mode, which prevents students from accessing any other web pages or applications while testing.
Devices/OS | Supported Versions | Download TestNav | Setup Instructions |
|---|---|---|---|
Tablets, Chromebooks, Chromeboxes | |||
Chrome OS | Stable Channel (S)
Long-term support (LTS)
| ||
iPadOS | 16.x, 17.3+, 18.x | ||
Laptops, Desktops | |||
Linux |
| ||
macOS |
| ||
Windows |
| ||
Beta Testing In-Progress
| Operating Systems |
|---|
chromeOS 135 beta |
Important Notes
- For practice/non-secure tests, you can use a TestNav app OR access TestNav through a browser link (for example, samplecustomer.testnav.com).
- Practice tests/non-secure tests using Dynamic Text to Speech (DTTS) must be taken using Chrome, Edge or Firefox browser on Windows.
- Web extensions on non-secure tests are supported only on Chrome browser.
TestNav supports audio-recorder interactions only through the TestNav app on these OSs*:
Windows
Mac
iOS
Chrome OS
*These interactions are not supported on any browser.
- You can use TestNav on Android only for practice/non-secure tests.
- Remote testing, dynamicTTS (DTTS), Audio Recorder, Read&Write and Co:writer are not supported on Linux.
Upcoming Support Changes
Pearson aligns support requirements with changing technologies. See the TestNav System Requirement Policy for details.
When operating system updates are released, Pearson first tests a beta version and reports bugs to developers. When the final version is publicly released, Pearson also tests this version to ensure TestNav compatibility before supporting it. When hardware or software deprecates, Pearson drops support for it.
Pearson pushes major TestNav upgrades twice a year—in summer and in winter. See TestNav App Updates for more information.