After you download TestNav Desktop for Linux and ProctorCache, complete the following:
These ordered steps correspond to sections below or a related setup page. You can click each link to go directly to the corresponding processes.
Install TestNav Desktop using the instructions below for either Ubuntu or Fedora.
- Run App Check for Ubuntu or App Check for Fedora to verify system readiness.
- Start TestNav Desktop on Ubuntu or Fedora. If you have issues starting TestNav Desktop on Fedora, see Other Possible Dependencies.
Set up ProctorCache on your proctor caching computer(s).
- Review the Set Up Response File Backups section to prepare yourself to find saved response files (SRF) and log files before the testing session.
Set up a secondary save location.
Install TestNav Desktop on Ubuntu
TestNav program files are saved in /opt/testnav.
Download the appropriate 32-bit or 64-bit Ubuntu .deb file from the TestNav downloads page, and double-click the .deb file.
The Ubuntu Software Center opens. Click Install.
Enter your password and click Authenticate.
The Ubuntu Software Center displays the Installed message.
Run App Check
To run App Check:
- Click or tap the appropriate icon for your test from the home page to go to the Sign In page.
Click or tap the user drop-down menu, and select App Check.
App Check (without optional Configuration Identifier)
On the App Check page:
Leave the configuration identifier field blank.
Click Run App Check.
You see green checkboxes for Kiosk Mode readiness and connectivity to TestNav, if the system passes. If one of these fails, you will see a Fail message and must check your connection and settings before running App Check again.
App Check (with optional Configuration Identifier)
If you have obtained a Configuration Identifier from your assessment management system:
Enter it in the Configuration Identifier field on the App Check page.
The configuration identifier allows TestNav to also check connection to ProctorCache computers. If your assessment management system allows, this configuration ID may also check for blacklist compliance. See your assessment management system documentation for additional information.
Click Run App Check.
If ProctorCache connectivity (or blacklist compliance) fail, TestNav provides information for possible resolutions. Use this information to troubleshoot, and run App Check again.
The screenshots below are examples of possible scenarios when running App Check with a configuration identifier.ProctorCache Pass
ProctorCache Fail
Blacklist Pass
Blacklist Fail
Sign in to TestNav Desktop on Ubuntu
- Click the Ubuntu logo and enter testnav in the search box to find TestNav Desktop.
- Double-click the TestNav icon to launch TestNav Desktop.
If you have not already done so, click the appropriate program icon to select your test. If your test was selected prior, you see the Sign In page, rather than the home page.
If you need to select a different test, click the user drop-down menu in the upper-right, and click Choose a different customer.
Click the appropriate program icon.
Start a test to ensure that you can do so without error.
- If you see a Practice Tests link on the Sign in page, click Practice Tests and start a test.
- If you do not see a Practice Tests link, use an authorization ticket from your student management system and start a test.
Install TestNav Desktop on Fedora
- Download the appropriate 32-bit or 64-bit Fedora .rpm file from the TestNav downloads page.
Click Activities in the upper left of the desktop to reveal the side menu icons, and click the Show Applications icon at the bottom of the list.
Enter terminal in the search box and double-click the icon to launch the terminal.
- In the Terminal, change to the directory containing the install file.
- Switch to the Root account.
Enter dnf install testnav-1.x.x.rpm and click Enter, using the exact filename of the TestNav install file you downloaded. This installs dependencies and then installs TestNav.
On Fedora, you may have to install additional software libraries for TestNav to properly install and/or work. The information below will help you with this task.
Other Possible Dependencies
Fedora 64
Install Dependencies (command-line only)
| Dependency | Met by installing | Example Commands for Resolution |
|---|---|---|
libc.so.6 libdl.so.2 libm.so.6 | glibc.i686 | sudo dnf install glibc.i686 |
| libX11.so.6 | libX11.i686 | sudo dnf install libX11.i686 |
| libXext.so.6 | libXext.i686 | sudo dnf install libXext.i686 |
| libXi.so.6 | libXi.i686 | sudo dnf install libXi.i686 |
| libXrender.so.1 | libXrender.i686 | sudo dnf install libXrender.i686 |
| libXtst.so.6 | libXtst.i686 | sudo dnf install libXtst.i686 |
| libasound.so.2 | alsa-lib.i686 | sudo dnf install alsa-lib.i686 |
| libgcc_s.so.1 | libgcc.i686 | sudo dnf install libgcc.i686 |
Runtime Dependencies
| Dependency | Met by installing | Example Commands for Resolution |
|---|---|---|
| libXss.so.1 | libXScrnSaver | sudo dnf install libXScrnSaver |
| libcrypto.so.1.0.0 | a symbolic link to latest matching libcrypto in /usr/lib64 | sudo ln -s /usr/lib64/libcrypto.so.1.0.1k /usr/lib64/libcrypto.so.1.0.0 |
Fedora 32
Runtime Dependencies
| Dependency | Met by installing | Example Commands for Resolution |
|---|---|---|
| libXss.so.1 | libXScrnSaver | sudo dnf install libXScrnSaver |
| libcrypto.so.1.0.0 | symbolic link to latest matching libcrypto in /usr/lib | sudo ln -s /usr/lib/libcrypto.so.1.0.1k /usr/lib/libcrypto.so.1.0.0 |
Troubleshooting
If you cannot open TestNav Desktop after meeting the dependencies above, enter the following command from {user_home}/.config/Pearson/TestNav/jxbrowser/{version} to find and install any additional Chromium dependencies:
LD_LIBRARY_PATH=. ldd libjxbrowser-chromium-lib.so
If you continue to have issues, find log files at {user_home}/Pearson/logs, and then contact Pearson support.
Run App Check
To run App Check:
- Click or tap the appropriate icon for your test from the home page to go to the Sign In page.
Click or tap the user drop-down menu, and select App Check.
App Check (without optional Configuration Identifier)
On the App Check page:
Leave the configuration identifier field blank.
Click Run App Check.
You see green checkboxes for Kiosk Mode readiness and connectivity to TestNav, if the system passes. If one of these fails, you will see a Fail message and must check your connection and settings before running App Check again.
App Check (with optional Configuration Identifier)
If you have obtained a Configuration Identifier from your assessment management system:
Enter it in the Configuration Identifier field on the App Check page.
The configuration identifier allows TestNav to also check connection to ProctorCache computers. If your assessment management system allows, this configuration ID may also check for blacklist compliance. See your assessment management system documentation for additional information.
Click Run App Check.
If ProctorCache connectivity (or blacklist compliance) fail, TestNav provides information for possible resolutions. Use this information to troubleshoot, and run App Check again.
The screenshots below are examples of possible scenarios when running App Check with a configuration identifier.ProctorCache Pass
ProctorCache Fail
Blacklist Pass
Blacklist Fail
Sign in to TestNav Desktop on Fedora
- Click Activities in the upper left of the desktop to reveal the side menu icons.
Click the Applications icon at the bottom of the menu.
Type Testnav in the search box to find the application.
Double-click the TestNav icon to launch TestNav.
If you have not already done so, choose the appropriate icon for your test on the home page. If your test was selected before the test session, you see the Sign In page, rather than the home page.
- If you need to select a different test, click the user drop-down menu at the upper-right of the page, and click Choose a different customer.
- Choose the appropriate icon for your test.
- Start a test to ensure that you can do so without error.
- If you see a Practice Tests link on the Sign in page, click Practice Tests and start a test.
- If you do not see a Practice Tests link, use an authorization ticket from your student management system and start a test.
If you have issues starting TestNav Desktop on Fedora, see Other Possible Dependencies.
TestNav Desktop Updates
TestNav program file updates are saved in {user_home}/.config/Pearson. You must give students write access to the update directory.
When you install TestNav Desktop, it creates the TestNav folder within the Pearson folder shown in the path above. The TestNav folder contains the following: The login preference stored in the default file can change if you select a different customer from the Sign In page. You can set the default file to read-only to prevent students from overwriting it after you set your test preference. If you encounter any issues during an update, you can find the errorlog folder within the update folder (for example: 1.4.1 > update > errorlog). The errorlog folder logs any issues TestNav may encounter when it attempts an update. You can also delete the Pearson folder to reset TestNav, clearing out any updates stored in that directory.
Set Up Response File Backups
TestNav has a default primary SRF save location for all computers and devices. Pearson strongly recommends setting a secondary save location for SRFs as a backup. For detailed information on saved response files (SRFs) and log files, see Understand SRFs and Log Files for Installable TestNav .
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.
Before testing, refer to your assessment management system user guide to configure TestNav and complete the following steps.
Configure primary and a secondary save location through your assessment management system.
Configure student accounts to have complete read, write, and delete access in these save locations.
Communicate SRF and log file locations to test proctors.
Give proctors access to SRF and log files by either of the following:
Grant admin rights to proctors on each testing computer.
Instruct proctors to access these files while the student is logged in to the testing computer.
Default Primary Save Location
| Operating System | SRF Location | Log File Location |
|---|---|---|
| Linux | {USER.HOME}/Pearson/srf/ | {USER.HOME}/Pearson/logs/ |
Secondary Save Location
You can set a secondary save location through your assessment management system. Set a secure file transfer protocol (SFTP) address as the save location to ensure that the secondary save applies to all testing computers and devices.
Pearson strongly recommends that you configure a network drive as a secondary save location to ensure that you do not lose responses, even if a student cannot continue to test on the same computer.
Run an Infrastructure Trial
Pearson strongly recommends running an infrastructure trial to verify the technology setup is complete and to familiarize teachers and students with the test.
Use your training site through your assessment management system to complete the trial before the actual test day.
Related Information
You can learn more about SRF and log files on the Set up and Use TestNav page.