Review guidelines, and install and sign-in pages for your specific operating system(s) within this section. On this page, you can also find details on wireless best practices, App Check, and saved response file (SRF) and log files.

Wireless testing best practices

If you're testing wirelessly, use the following best practices:

  • Use the most wireless access points (WAPs) possible.
  • Limit the number of computers per WAP.
  • Limit distance and obstructions between devices and the WAPs.
  • Run an infrastructure trial to test capacity and performance.

Understand App Check

You can find App Check on the TestNav Sign In page. App Check confirms that the device or computer can connect to TestNav and that it is configured to start TestNav in kiosk mode. An optional configuration identifier may be entered to validate additional TestNav configurations from the assessment management system.

See the Run App Check section on each setup page for basic step-by step instruction.

App Check does not check screen size or resolution. If a student attempts to sign in to a test on a device that does not meet support minimums, TestNav may display an error. See TestNav System Requirements for support minimums.

Understand SRF and log files

When a student responds to a test question, TestNav sends the response to the Pearson server. If the network experiences a connectivity issue, or the student encounters an error, TestNav saves the response to a saved response file (SRF).

TestNav also creates a log file during the testing session. These files help Pearson troubleshoot issues, if they occur. After connectivity is reestablished, and responses successfully save to the Pearson server, TestNav deletes the SRF.

For Windows and Mac, you must configure student accounts to have complete read, write, and delete access in all save locations. You cannot configure the log file save location.

Secondary save location (PearsonAccess Next users only)

This section is not applicable to ADAM or Pearson Access assessment management systems. This section pertains only to customers using PearsonAccess Next (PAN) as their assessment management system.

PAN users can place backup SRFs in a directory on the network file server, on the student's testing computer, or on a secure file transfer protocol (SFTP) site. The following table outlines the pros and cons of each backup save location. 
Back up location options
Directory on network computerBackup file is accessible from other computers.
  • Uses more internal network bandwidth.
  • Responses save to the network drive more slowly than to the local directory. As a result, test items take more time to load.
  • Does not provide secondary save for the devices below:
    • Android devices
    • Chromebooks
    • iPads
Local directory on testing computer (TestNav client)
  • Uses less internal network bandwidth.
  • Responses save to local directory more quickly than to the network drive. As a result, test items take less time to load.
  • Backup file is not accessible from any other computer.
  • Does not provide secondary save for the devices below:
    • Android devices
    • Chromebooks
    • iPads


Note: SFTP configuration is not supported by all assessment management systems. Consult your assessment management system user guide to determine whether the SFTP option is available.

Provides secondary save location for all supported testing computers and devices.Requires SFTP site setup.

You should familiarize yourself with default response file backup locations. Some save locations are configurable. See each setup page for details and instructions.

If you set a network file server as a primary or secondary backup location, do not use:

  • Spaces in the save location path.
  • A location that requires authentication. If authentication is required, TestNav cannot access the shared location.
  • A Windows UNC (Uniform Naming Convention) or network path, such as \\ComputerName\SharedFolder\Resource on a Mac or Linux. Pearson recommends that you specify a mapped drive location, such as D:\TopDirectory\NextDirectory\SaveLocation.

Tiny link: