TestNav SOL refers to the use of Pearson's TestNav platform for administering Virginia's Standards of Learning assessments — the state-mandated tests that measure student achievement in reading, mathematics, science, history, and other core subjects across elementary, middle, and high school grades. Virginia has been using online testing for SOL assessments for many years, and TestNav is the platform through which the vast majority of Virginia students now complete their required state tests.
Virginia's SOL program is one of the most comprehensive state testing systems in the country, with assessments at multiple grade levels testing mastery of the Virginia curriculum standards. SOL tests are used for school accreditation, student performance reporting, and in high school, for meeting graduation requirements. The stakes of these tests — for individual students who need to pass certain SOLs to graduate, and for schools whose accreditation depends on passing rates — make understanding the TestNav platform relevant not just for test day navigation but for reducing the anxiety that can affect performance.
For most Virginia students, the first encounter with TestNav SOL happens in third grade when reading and mathematics assessments begin. The platform experience is consistent across grade levels — the same login process, the same navigation tools, and the same item types appear whether a student is taking a grade 3 reading test or a high school end-of-course science test. This consistency is intentional: students who are familiar with the platform from early grades should feel comfortable navigating any SOL assessment they encounter later in their school career.
One aspect of TestNav SOL that distinguishes it from paper-based testing is the way the platform handles different item types within the same test. A single SOL assessment might include traditional multiple-choice questions alongside technology-enhanced items that require dragging objects, clicking hot spots on images, or entering short text responses.
Students who haven't encountered these formats before test day can spend a disproportionate amount of time figuring out how to interact with an unfamiliar item — time that should be spent on the content itself. The platform's practice portal exists precisely to eliminate this problem: when a student already knows that clicking a hot spot means clicking on a specific region of an image (not just anywhere near it), that interaction becomes automatic rather than a source of confusion.
The relationship between Virginia's testing program and the TestNav platform reflects a broader national shift toward computer-based standardized assessment. States across the country have migrated away from paper answer sheets and hand-scanning operations toward online testing platforms that can deliver results faster, accommodate richer item types, and support accessibility features more consistently. Virginia's transition to online SOL testing happened gradually over several years, and TestNav has been the consistent platform throughout — which means teachers, test coordinators, and students across Virginia have accumulated experience with the system that makes each successive testing cycle smoother than the one before.
It's also worth noting that TestNav is built with educational assessment security in mind. The platform's lockdown mode prevents students from accessing other browser tabs, running other applications, or copying test content. This security infrastructure is part of why Virginia's SOL results carry the validity they do — the testing conditions are controlled consistently across thousands of testing sites statewide.
Students should understand that screenshot attempts, browser switching, or any attempt to exit the secure testing mode is automatically flagged and reported to the test coordinator, so staying within the TestNav interface throughout the session is both a practical and procedural requirement.
Virginia students access TestNav SOL through a process managed by their school's test coordinator. On the day of an SOL test, students receive a session token — a unique code that grants access to the specific test they're scheduled to take. Students enter this token on the TestNav login screen, which can be accessed through the TestNav app installed on the testing device or directly through a web browser navigating to the TestNav URL provided by the school.
Schools are responsible for ensuring that testing devices meet the technical requirements for TestNav. The platform supports Windows and Mac computers, Chromebooks, iPads, and Android tablets, with specific operating system and browser version requirements that Pearson updates before each testing window. Schools typically use a specific Chrome-based kiosk mode or the TestNav app in locked-down testing mode during actual SOL administrations to prevent students from accessing other applications or the internet during the test.
For practice purposes outside of formal testing, the TestNav app and the study.testnav.com practice portal provide access to sample items and practice tests without requiring a session token. Students can use these resources from home or school to familiarize themselves with the platform at any time, not just immediately before test day. The practice items are organized by subject and grade level, making it easy to find relevant examples for an upcoming assessment.
Students who experience technical problems during an SOL test should raise their hand immediately to alert the proctor rather than attempting to troubleshoot the problem themselves. Proctors are trained in TestNav technical recovery procedures and can handle most common issues — frozen screens, accidental exits, connectivity interruptions — without affecting the student's test data. TestNav saves responses automatically as students progress, so technical interruptions typically don't result in lost work if the problem is handled promptly by trained staff.
One practical detail students should know before their first SOL test: the session token is single-use and time-limited. Tokens are distributed by proctors at the start of the testing session and are only valid for the test being administered at that time.
Students who are absent on a scheduled testing day receive a new token when they make up the test — they can't reuse a previous token, and the makeup test is administered under the same controlled conditions as the original. Knowing this in advance prevents confusion on test day about why a token from a previous test day doesn't work.
Virginia's SOL testing program covers a wide range of subjects across grade levels, and TestNav is the platform for virtually all of them. Understanding which tests your grade level includes helps you prioritize practice and preparation. Reading and mathematics assessments run through nearly every grade level from 3 through 8, with additional end-of-course tests in high school. Science assessments are given at grades 5 and 8 and in high school. History and social studies assessments are administered at grades 3, 4, and high school.
High school end-of-course SOL tests are the most consequential for individual students because passing certain EOC tests is required for an advanced diploma. The affected tests include reading, writing, mathematics courses (Algebra I and II, Geometry), science (Biology and Earth Science or Chemistry), and history (World History and US and VA History). Students who don't pass these tests on the first attempt can retake them during subsequent testing windows, but Virginia's retake options and graduation requirements create real stakes for students who approach these tests without adequate preparation.
Virginia's VDOE provides released SOL items — actual questions from previous test administrations — that are publicly available and directly useful for preparation. These released items are the best available resource for understanding what the tests actually ask, how items are worded, and what conceptual understanding each test demands. Combined with the TestNav practice interface, working through released items in the actual testing platform is the most authentic preparation experience available outside of a formal test administration.
Students who are preparing for multiple SOL tests in the same school year — which is common in middle school, when reading, mathematics, science, and history assessments may all fall within the same testing windows — benefit from consolidating their TestNav practice across subjects rather than treating each test as a separate preparation task.
The platform mechanics are identical across all SOL tests, so becoming fluent with navigation, flagging, and tool use in one subject carries over directly to every other test. What differs by subject is the specific embedded tools available and the item type distribution — a math test might lean heavily on technology-enhanced calculation items while a reading test emphasizes evidence-based multiple-choice and short-answer formats.
Parents supporting SOL preparation at home should understand that test content knowledge and platform familiarity are two separate preparation dimensions. A student can know all the material perfectly but still lose time on test day struggling with an interface they've never practiced on.
Conversely, a student who is deeply comfortable with the TestNav interface can pace themselves more efficiently, use the review and flagging features strategically, and maintain confidence even when they encounter difficult items. Study.testnav.com is available at home with no login and no special setup — it runs in any modern browser and gives students the same experience they'll have in school on test day. Teachers who send home a simple note at the start of SOL testing season pointing parents to study.testnav.com consistently report that their students arrive on test day more confident and less distracted by platform mechanics.
Log in to study.testnav.com to try practice items for your subject and grade level before your actual SOL test. The practice portal looks and feels identical to the real test platform — same navigation, same tools, same item types. Work through at least one complete practice section timed under the same conditions you'll face on test day. If the TestNav calculator is available for your test, practice using it for the problems where it's permitted. Raise any technical concerns with your teacher or test coordinator before test day so they can be resolved without affecting your actual assessment.
Virginia's SOL testing schedule is published by the school at the start of the year. Check which SOL tests your child is taking and in what testing window. Encourage use of the study.testnav.com practice resources at home — they're free and require no login. Make sure your child gets adequate sleep the night before testing and arrives to school on time. If your child has an IEP or 504 plan with testing accommodations, confirm with the school that accommodations are set up in TestNav before the test window opens, not the morning of the test.
Incorporate TestNav practice into your regular classroom routine in the weeks before testing windows — even one practice session on actual Chromebooks or laptops navigating study.testnav.com items familiarizes students with the platform mechanics. Review the technology-enhanced item types that appear on your subject's SOL test and make sure students have practiced interacting with them. For students with accommodations, verify with the test coordinator that testing mode settings are correct in the test management system before the testing window opens.
Technical issues during SOL testing are rare but do happen, and knowing the standard recovery procedures helps students and educators respond efficiently without disrupting the testing session unnecessarily. The most common issues are: the TestNav session freezing or becoming unresponsive, the student accidentally exiting the secure browser mode, a device running out of battery during testing, and network connectivity interruptions that cause a session to drop.
For frozen screens, the standard procedure is to wait 30 seconds to see if the application recovers, then alert the proctor. Proctors have authorization codes that allow students to resume a paused session after a technical interruption — this is important because returning to TestNav after an unexpected exit requires a proctor-authorized resume code, not just re-entering the original session token. Students who try to log back in on their own without proctor involvement may create complications that take longer to resolve than the original problem.
Battery and power issues are preventable — testing devices should be fully charged before every testing day, and schools should have charging protocols for morning-of-test preparation. A device dying mid-test is avoidable with basic preparation but creates significant administrative burden when it happens. Students using personally provided devices for remote testing should confirm battery status and power adapter availability before starting any TestNav session.
Network connectivity issues are most common in schools with aging wireless infrastructure or in students' homes during virtual testing scenarios. The TestNav platform is designed with some offline tolerance — it saves responses locally and syncs when connectivity is restored — but extended connectivity loss can trigger a session drop that requires the proctor's assistance to resume. Schools that have experienced connectivity issues during testing should work with their IT staff to ensure adequate wireless bandwidth during testing windows, as multiple simultaneous TestNav sessions demand consistent network performance.
Test coordinators play a critical role in preventing technical problems before they start. Before every testing window, coordinators should verify that all testing devices are updated to the supported operating system and browser versions, that the TestNav app (if used) is updated to the current version, and that device management profiles are correctly configured for secure testing mode.
Schools that do a brief technology check on the morning of testing — confirming each device loads TestNav's login screen and accepts a test token — catch device issues before they become mid-test emergencies. A five-minute morning check-in protocol prevents the kind of cascading problems that happen when a student sits down to test on a device that hasn't been updated or properly configured.
After any technical interruption that requires proctor involvement, the test coordinator should document what happened and report the incident to the VDOE through the standard irregularity reporting process. This documentation protects students in cases where technical errors might have affected their test experience and gives the state visibility into systemic issues — if ten schools in the same district experience the same connectivity problem during the same testing window, that's information the VDOE and Pearson need to address the root cause before the next testing window.