When configuring an assessment the admin can enable tab proctoring that helps track the tab
switches made by the candidates while taking the test. Here the admin can also set a max allowed tab switches limit which sets a limit for tab switches after which the candidate would be flagged for cheating. The keyword here is “flagged”.
They will be flagged, but the system WON’T force-end their attempt.
Whenever the candidate switches a tab, they will be notified about the tab switch.
When the candidate crosses the max allowed tab switch limit, the test won’t end instead the
candidate can continue with the test.
Once the test ends, the candidate will be marked as failed based on the tab switch limit
once the results are generated.
Reasons for not force-ending the candidate attempt after crossing the max tab switches limit
It was a conscious decision to not force-end the candidate's attempt even after exceeding
The reason is that, say 1000 candidates take the test.
Then let’s say 500 of them got force-ended because they switched tabs too many times.
What if 500 of them emailed us saying that it was due to some unexpected behavior from the platform that the tab switching happened? Or what if they say that it's a browser issue etc.? Or what if they say it's an OS issue and the platform's incompatibility with that OS?
How can we prove whether the candidate is right or wrong?
Who will play the role of sending out emails to all these candidates regarding this query?
In order to avoid all these hassles, we allow them to continue the test.
The candidate will be marked as
failedbased on the tab switch limit once results are
generated. So for them, we can send rejection emails without specifying why they failed.