Skip to main content

Installing the CAASPP and ELPAC Secure Browser on ChromeOS

Use this overview to prepare a standalone Chromebook for California online testing. Secure-browser requirements change with ChromeOS releases, so begin with the official California technology resources every year.

Do not use the former installation procedure

The older procedure instructed users to wipe the Chromebook, enable Developer Mode, open chrome://extensions, and enter a hard-coded AIRSecureTest application ID. That Chrome App kiosk process is obsolete for current ChromeOS releases and can erase local data.

Do not enable Developer Mode or powerwash a device solely to install the current secure browser. Follow the current basic-installation or managed-device directions published for the ChromeOS version in use.

Before installation

1. Identify ChromeOS

Open Settings > About ChromeOS and record the installed version and update channel. Confirm that the version is currently supported for student testing.

2. Choose the correct path

Determine whether the Chromebook is standalone or managed through the Google Admin console. These device types use different deployment instructions.

3. Gather essentials

Have the Wi-Fi network information, a permitted device account if required, and access to the current California Secure Browsers page.

Current installation workflow

  1. Verify current support. Review the supported operating systems and secure-browser information before updating ChromeOS. A newly released operating-system version may not be supported immediately.
  2. Open the official Secure Browsers page. Select ChromeOS, then use the current instructions and installation option displayed for that operating-system version.
  3. Use the current application. ChromeOS 139 introduced a secure-browser progressive web application (PWA) that replaced the legacy Chrome App on newer releases. Do not reuse an application ID copied from an older article.
  4. Follow the appropriate deployment directions. For a standalone device, use the official ChromeOS Basic Secure Browser Installation procedure. For an LEA-managed fleet, use the Google Admin console deployment instructions in the Technology Guide.
  5. Restart or sign out as directed. The secure testing application should be launched from the device's designated secure-testing or application screen, not from an ordinary signed-in browsing session.
  6. Confirm the California testing site. Launch the secure browser and verify that it reaches the California student testing interface without an unsupported browser or operating-system message.
  7. Run a practice or training test. Check audio, keyboard, mouse or touch input, display, and any assigned accessibility resources before operational testing begins.

Version awareness

Environment Direction
Current ChromeOS releases Use the current secure-browser PWA and the installation method shown on California's Secure Browsers page.
Older ChromeOS devices Do not assume the legacy secure browser remains supported. Check the current support table before testing or retaining an older operating-system version.
Managed Chromebooks Deploy and configure through the Google Admin console using the current managed-device instructions.
Standalone Chromebooks Use the current ChromeOS basic-installation instructions. Do not substitute the former Developer Mode and Chrome App process.

Pretesting checklist

  • ChromeOS and the secure-browser application are on the current supported list.
  • Automatic updates will not move devices to an unsupported release during the testing window.
  • Required California testing URLs and network traffic are allowed.
  • Headphones, microphones, cameras, and text-to-speech resources work where required.
  • Students and staff know how to launch and exit the secure testing environment.
  • A practice or training test has been completed on representative devices.

Official resources

This article intentionally does not reproduce an annual application identifier or vendor screen sequence. Those details can change between test administrations. Use the live official instructions when installing or reconfiguring a device. Reviewed August 4, 2026.