Candidate Log in
Candidate selects the login method (Regular Login or Log in with test code) and then the School or University they belong to.
Regular login
Test-code login
Candidate_login page
Based on the School or University selected, they are taken to the following Candidate login page. They can login using SSO or one-time user credentials.
Candidate Submission
After completing a test the candidate can click on Submit Now for a standalone test
or click on the Exit button (shown in the below screenshot) for a Composite test
How does a candidate Exit?
On Clicking Submit Now in the previous step for a standalone test, Candidate will land in the following Dashboard where on Clicking "Exit application", the application will close.
Candidate can also click on the top right burger menu during the test to land on the following page, from where clicking on "Exit application" will Exit the application.
Candidates will land on the following screen if they exit the application or test and wish to go back to the same test. The invigilator password would need to be entered by the invigilator to resume the test.
If internet connection is lost during the test, the candidate will be shown the following page, where clicking Exit now will close the application and download an offline submission file.
The Kiosk application will be closed and the session will be forgotten upon relaunch if the candidate uses any of the Exit routes as shown in the screenshot above, provided the Admins have installed an extension via Google Admin Console.
Check this article on How to install Companion Extensions for Chromebooks.
When the candidate is offline (For all the exit route screenshots above)
Due to technology limitations in PWA, Exit buttons (in different exit routes mentioned above) will not work. The candidate will have to press the physical power key on their keyboard, then Click on Sign Out to close the application successfully.
URLs present in the question
Candidate will have to use the physical back button on the Chromebook to go back to the test
Planner Experience in Chromebook
Select this checkbox in Deliver >Test to create a test to be taken only on Chromebooks.
Author Experience in Chromebook
Check this document to understand how Authors can add questions for a test to be taken on a Chromebook. It’s similar to how they create the tests to be taken on open browsers and IIB as well.
- Some URLs added as Additional resources on a Question Set level might not load for a test taker in PWA due to stricter Content Security Policies. Authors can use this tool for now to see whether the URL added will load for a Test taker or not.
A candidate can navigate to external links within the attached URL. Look at the original URL to see if it has additional resources listed on it.
- For Audio record question types, the tenancies where the tests using this question type are to be taken need to be whitelisted in the Google Admin console. Check this page to see how to whitelist if you have permission or get it whitelisted by the IT department.
Adding a URL through Add Link in Author > Editor UI
If an Author has used these target types (New window, frame, popup window) to add a link in question, it won’t open for a candidate. It will act like a dummy link. This was the behavior in legacy applications as well.
If an Author has used these target types: Topmost window, same window, or parent window to add a link in Question, it opens the attached URL in fullscreen, on top of the test window. The candidate will have to click the physical back button on the Chromebook, then the invigilator will enter the invigilator password and the test will be resumed for the candidate.
Candidate view of the 3 URLs with different target type
Any of the three URLs will open in full-screen mode as seen above.
Invigilator Experience in Chromebook
An invigilator password will be required if a candidate Needs to exit the test, Needs to resume the test,Any time the player reloads like the refresh button is used during the test or the candidate wants to go back to the test after viewing a URL attached in the question
1. If a candidate logs in using Google SSO and exits using any of the available exit routes, the Google session is not forgotten. The Google Session will not be cleared for these candidates when they exit the application. This is a known issue.
Mitigation: Use the Google Admin setting "Erase all local user data", in Devices > Chrome > Settings > Device Settings > Sign-in settings
The impact of enabling this setting
1.1 The Google session is forgotten.
1.2 Local device data is also deleted. This shouldn't be a concern for incenter tests.
1.3 If a candidate exits the application while he is offline (using the physical power key, that is the only way they can exit offline), the answers he gave while offline won't be saved if he logs back in.
The save submission as a file option inside the burger menu can still used when the candidate is still inside the application.This is a very edge case because in in-center tests, the probability of losing an internet connection is less.
2. Reload button
It did not work in the legacy application.
Due to the technology limitations in the PWA, the reload button works. If the candidate presses the reload button, it will require the invigilator password on refresh.
3. When a candidate navigates to a link used in a question during a test, he would require an invigilator password to resume his test.
4. If a candidate comes across the following screen
Use the following steps to restore
4.1 Use Ctrl+0 to reset the default Zoom value.
4.2 Press the Physical power key on the Chromebook, then select either signout or Sutdown to exit the application.
4.3 After this, you can log back into the application. The candidate will not see this error.