Page tree

This documentation is not intended to be read independently of the main documentation.

Please refer to the site home page for a list of our documentation instead of the documentation in this space.


You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

When a student responds to a test question, TestNav saves the response in a saved response file (SRF) and sends response bundles to the Pearson server. After the responses successfully save to the Pearson server, TestNav deletes the SRF. By default, TestNav automatically creates a Pearson folder in the user's home directory (the user account or login typically determines the directory name). The SRF saves in a SRF folder within that Pearson folder.

TestNav also writes to a log file during the testing session. These files help Pearson troubleshoot issues, if they occur. TestNav saves these log files in a Logs folder within the Pearson folder, as well. 

For Windows and Mac OS X, you must configure student accounts to have complete read, write, and delete access in all save locations.  Pearson strongly recommends that you configure a shared network folder that can be accessed from all testing computers as a secondary save location for SRFs to ensure that you do not lose responses, even if a student cannot continue to test on the same computer. You must verify that you can access the location from multiple testing computers.

You cannot configure the log file save location.

Secondary Save File Location

You can place backup SRFs in a directory on the network file server or on the student's testing computer. The following table outlines the pros and cons of each option; however, as a best practice, Pearson recommends using both location options - one for the primary save location and the other for the secondary save location. You must use a Secure File Transfer Protocol (SFTP) address to ensure that TestNav saves backup SRF files for all computers and devices. If you set a non-SFTP address as a secondary save location, TestNav saves backup SRFs for students testing on ONLY browser-based TestNav and TestNav Desktop.
Back up location options
Pros
Cons
Directory on network computerBackup file is accessible from other computers.
  • Uses more internal network bandwidth.
  • Responses save to local directory slower than to the network drive, and test items load faster as a result.
Local directory on testing computer (TestNav client)
  • Uses less internal network bandwidth.
  • Responses save to local directory more quickly than to the network drive, and test items are presented more quickly as a result.
Backup file is not accessible from any other computer.

Whether or not you cache your test content, you should familiarize yourself with response file backup locations and configure them.

If you use a network file server as a backup location, whether primary or secondary:

  • Do NOT use spaces in the save location path.
  • Do NOT use a location that requires authentication. If authentication is required, TestNav cannot access the shared location.

Pearson recommends that you: 

  • Specify a mapped drive location, such as D:\TopDirectory\NextDirectory\SaveLocation.
  • Unless necessary, do not use a Windows UNC (Uniform Naming Convention) or network path, such as \\ComputerName\SharedFolder\Resource.


  • No labels