Teachers evaluating an online assessment platform reasonably want to know what it can see, what it can prevent, and where its technical limits lie. Here are straightforward answers to several questions we have received about student monitoring and secure testing.
Does the platform show all activity on a student’s computer?
No. Innovation Assessments is not remote-surveillance software and does not provide teachers with a complete view of a student’s computer.
It does not record the student’s screen, activate the webcam, inspect personal files, or produce a history of everything the student does on the device.
During a proctored Testapp assessment, the system can record browser events connected to the test, including:
- Leaving or returning to the test tab
- Moving focus away from the test window
- Exiting or entering full-screen mode
- Pasting or copying text
- Attempting certain blocked shortcuts or right-click actions
- Resizing the browser window
- Time spent away from the test
- Time spent on questions
- Restarting or resuming a session
- Test start, saving, and submission events
Teachers can review these events in the proctor log. The system also summarizes combinations of events that may deserve attention, such as repeated tab departures, long periods away, or a tab departure followed by pasted text.
These records provide context; they are not proof of misconduct. A focus change, for example, could result from browser controls, accessibility software, an input method, or an ordinary notification. Teachers should interpret logs alongside the student’s explanation and the circumstances of the assessment.
Do students have to install an application?
No. Students ordinarily use Innovation Assessments through a web browser. They do not need to install a separate monitoring application or browser extension.
This makes the platform easier to use on school-managed Chromebooks, conventional computers, and tablets. It also means the platform operates within the security boundaries imposed by modern browsers.
A browser-based application cannot inspect an entire device in the way that specially installed device-management or remote-proctoring software sometimes can.
Does Testapp include a lockdown browser?
Testapp includes a configurable secure-testing mode, but it should not be described as a traditional operating-system-level lockdown browser.
When strict security settings are enabled, Testapp can require students to remain in the test tab and, on supported devices, remain in full-screen mode. Leaving the tab, leaving the browser window for more than the allowed grace period, or remaining outside full-screen mode can automatically lock the test.
Once locked, the student cannot simply continue. The teacher must review the situation and readmit the student.
Testapp can also:
- Restrict an assessment to one active browser tab or device session
- Require single-use access codes
- Enforce time limits
- Automatically submit when secure time expires
- Limit audio playback when configured
- Preserve responses through autosaving
- Record security and session events
- Let teachers monitor progress in real time
- Block or readmit individual students
iPads use a compatibility mode because mobile Safari handles full-screen and focus events differently from desktop browsers. Brief keyboard or browser-interface changes are tolerated, while an extended app or tab departure can still trigger a lock when strict tab locking is enabled.
Can students go wherever they want during a test?
A web application cannot physically prevent a student from opening another application, using another device, or consulting material outside the browser.
What Testapp can do is establish consequences within the assessment. Under strict settings, leaving or hiding the test tab can lock the attempt. On supported desktop browsers, leaving the browser window or full-screen mode beyond the grace period can also result in a lock.
Teachers can choose settings appropriate to the situation. A low-stakes practice test may use monitoring without aggressive locking, while a controlled examination can use access codes, a timer, one-session enforcement, tab locking, and full-screen expectations.
Does it detect Google Lens?
Not directly.
A normal website cannot reliably ask a browser, “Is Google Lens being used?” Google Lens may be accessed in several ways:
- Through another browser tab
- Through another application
- Through a browser feature or extension
- Through a phone pointed at the screen
- Through functionality integrated into the operating system
Testapp can detect the browser consequences of some of these actions. If using Lens causes the student to leave the test tab, move to another application, exit full screen, or paste material into an answer, those events may be logged. Under strict security settings, leaving the test environment may lock the test.
However, Testapp cannot identify every use of Google Lens by name. Use on a second device would not be visible to the browser at all.
The accurate claim is therefore: Testapp can detect and respond to many browser behaviors associated with leaving the assessment, but it cannot guarantee detection of Google Lens itself.
Does it detect browser extensions?
It does not inventory or identify installed extensions.
Browsers deliberately prevent ordinary websites from obtaining a complete list of a user’s extensions. This is an important privacy and security restriction.
An extension may still produce detectable behavior. For example, its use might:
- Move focus away from the test
- Hide the test tab
- Exit full-screen mode
- Paste text into an answer
- Trigger a blocked shortcut
- Open a separate window
Those resulting events can be recorded, and some can trigger an automatic lock. An extension that operates entirely inside the page without generating a browser event may not be distinguishable from ordinary activity.
For this reason, schools seeking stronger control should combine Testapp with managed-device policies that disable unapproved extensions during testing.
What about language-setting changes?
Testapp does not directly monitor or forbid a student’s operating-system language, keyboard layout, or browser-language setting.
That restraint is important. Multilingual students may need an alternate keyboard or input method to type accented characters or non-English text. A language or keyboard change is not inherently suspicious.
If changing a setting requires the student to leave the test window, the resulting tab, focus, or full-screen event may be recorded. The platform records the browser event—not a claim about why it occurred.
Testapp also includes an accent-character toolbar for written answers, reducing the need for students to leave the page merely to enter common accented characters.
Would using Google Lens or an extension trigger a lock?
It may, depending on how the tool is used and how the teacher configured the test.
Examples:
- Opening Lens in another tab could trigger a tab-leave lock.
- Switching to another application could trigger a browser-leave lock.
- Leaving full screen for longer than the grace period could trigger a full-screen lock.
- Pasting generated or copied text would create a paste event, but paste alone is primarily logged and risk-flagged rather than treated as conclusive proof.
- Using Lens from a separate phone would not be detectable by the student’s test browser.
The lock is triggered by observable departures from the secure test environment—not by reliable identification of a particular product or extension.
What is the best way to use these protections?
Technical controls work best as one part of a larger assessment design. Teachers should consider combining secure Testapp settings with:
- Clear testing expectations
- School-managed browser and extension policies
- Thoughtfully randomized or individualized questions
- Questions requiring course-specific reasoning
- Short testing windows
- In-person supervision where appropriate
- Follow-up conversations when logs raise questions
- Comparison with a student’s established work
No browser-based platform can promise complete control over every device, application, extension, or second screen. Testapp instead provides a practical combination of deterrence, session control, automatic locking, event evidence, and teacher review—without pretending to provide invisible access to the student’s entire computer.
The goal is not to replace professional judgment. It is to give teachers better information and stronger control over the assessment environment while remaining honest about what browser technology can and cannot do.
AI-content disclosure: This article was generated by AI after reviewing the current Innovation Assessments application code. It is published under a separate account to distinguish AI-generated material from articles written by the site owner.