Even in the hot Italian July, we are not stopping; in fact, we are speeding up!
New this week is browser event logging, which is just one part of a larger feature: real-time monitoring of tasks in progress.
We wrote “new” because that is what this is all about.
For the first time within QuestBase, it will be possible to see if a user has had any suspicious behaviors other than filling out a test, assessment, or quiz within their browser.
What are these suspicious behaviors that QuestBase can identify?
- Hidden tab ⇨ the user has opened another tab within the browser and is no longer viewing the assigned task
- Loss of focus (foreground) ⇨ the user has opened another window above the browser on which they are performing the task or has moved the pointer to a second screen associated with the device.
- Resizing the browser ⇨ the user has minimized the browser.
Although the description mentions “minimizing” or “windowing” (and thus takes a PC/Mac performance as an example) the browser event logging was also designed and tested for mobile devices such as iPhones, iPads, tablets, and smartphones in general.
It goes without saying that QuestBase will record user events whatever browser the user is using: Google Chrome, Mozilla Firefox, Opera, Microsoft Edge, Safari.
In addition, QuestBase will record and list any suspicious behavior only when it is completed.
What will you display if suspicious behavior has been recorded on a user’s response?
Through an alert icon in the response status column, you can quickly know which users have had suspicious behavior recorded.
We have designed and implemented this feature for anyone who needs more control over their users but does not wish to use our secure browser, the Safe Exam Browser.
For the time being, the feature does not allow any actions other than those listed in this article; therefore, it will not be possible to change the outcome of a run if QuestBase registers suspicious behavior, and it will not be possible to block in real time a user who is having suspicious behavior.
Of course, all your suggestions regarding improvement and implementation of changes or enhancements are welcome, as are any bug or malfunction reports.
