Data & AssessmentDnA System Admin Assessment ManagementSetup: Locked-browser Online Testing on a Chrome Device

Setup: Locked-browser Online Testing on a Chrome Device

This lesson will guide you through setting up a locked-browser kiosk app for online assessments on a Chrome device.

NOTE: This how-to assumes you are an administrator of your Google Apps domain, and you have the ability to add apps via the Chrome device policy settings in the Google Apps admin panel.

Where to Start

Where to Start

1. Download and modify the app code. Zip file here:

Inside the file, there are 2 files that need to be modified. You can extract the contents of the zip file(right-click, then click “Extract All...”) to a folder to modify the code. You can use notepad, or a similar text editor, to make changes.

The first is manifest.json. This is the file that tells Google what your app is named, what version it is, and the description of the app(lines 2, 3, and 8). The name and description can be anything you want, but don’t omit the quotation marks. Once you publish your app, which we will go over later, any changes to the code need to be marked as a new version before it can be republished, i.e version 0.1 becomes 0.2. If this is your first time publishing the app to your Google panel, you can leave this file as-is, granted you are okay with the name and description.

Shown Above: Inside the manifest.json file

The second file is main.js. There is one line of code in this file that needs to be changed. It is the district’s IlluminateHC address, found on line 3. This will be in the form of “”. Don’t omit the quotes.

Shown Above: Inside the main.js file

2. Once those files are updated, you will need to zip the files back up. To do this, select all the files, right-click on them and select “Send to -> compressed (zipped) folder”.  You can name the zip file anything you’d like.

Publishing the App to your Google Developer Dashboard

Publishing the App to your Google Developer Dashboard

Go to If you are not already signed in to your Google Apps account, it will prompt you to do so. It will bring you to the following dashboard you see above.

1. Click the blue Add new item button. You will be prompted to accept the Developer Agreement. Review the agreement and accept the terms.

2. Click the Choose file button. You will be prompted with a file selection window.

3. You will need to select the zip file you created earlier, and click the upload button.  It will upload the file to Google and bring you to the next page.  

There are numerous changes we need to make. Options not listed can be left as is. Here they are in order of appearance on the page:

Detailed Description- Enter a description for the application. This is the description that you will see in the Chrome Web Store.

Icon- You will need to upload the icon.png file that was in the zip file. Alternatively, you could use any other 128 x 128 graphic file for the application icon.

Screenshots- You will need to provide a 640 x 400 or 1280 x 800 screenshot that will be used in the Chrome Web Store. It can be anything, as no one will see the app store page.

Promotional tile images- A 440 x 280 screenshot, similar to the above item. It will never be seen.

Websites- Leave as “None."

Category- Can be anything, but we recommend “Academic Resources."

Regions- Can be anything, but we recommend exclusively selecting “United States."

Language- Can be anything, but we recommend “English (United States)."

Visibility Options- This needs to be set to “Unlisted”. This is the only option that can be set here.

At the bottom of the page Google will ask for a fee. You do not need to pay the developer fee to publish apps to your own Google Apps domain. You can ignore this warning.

4. Click the Publish changes button in the bottom-right corner. If everything was entered correctly, you should be brought to a Chrome Web Store preview of your newly published app.

When you return to the Developer Dashboard your app will now be listed.

It won’t be available to assign to Chrome devices until the status reads published.

Congratulations! You’re ready to push the app to your Chrome devices now.