Oct 4, 2022

Scale E2E On-Device Testing with Meta Quest Scriptable Testing

End-to-end (E2E) testing provides a preview of your app’s functionality and performance in a live setting by running your app in-headset. E2E testing is critical to app development, but a handful of Meta Quest system features, such as auto-sleep, have prevented efficient testing at scale. We’ve heard your feedback on these common pain points, and now we’re excited to share a built-in solution with Platform SDK v44.

Meta Quest scriptable testing is a series of services that streamline the E2E testing process by letting you remotely disable certain system features, configure device setup, log in with test user accounts, and more. These services can help you scale on-device testing using ADB commands without opening separate desktop apps or being in-headset. Let’s dive deeper into what this means for you.

Adjust System Features for Free Reign Testing

Some Meta Quest system features that were designed to help preserve the integrity of the device for users also prevented easy, automated testing. This applied for both small and large batch testing, creating workplace inefficiency and bottlenecks. With v44, you now have the ability to temporarily enable and disable the following features using the GET_PROPERTY and SET_PROPERTY commands:

Certain modal (blocking) system dialogs, including the MTP dialog

Guardian: The play area defined by users that triggers visualization cues when in close proximity to the boundary

Auto-sleep: The headset automatically goes into sleep mode when inactive for a designated length of time

Disabling these features will allow you to conduct uninterrupted testing in a variety of scenarios. After your test ends, remember to re-enable all of the features listed above to avoid battery drainage and return the device to its normal state. You can also factory reset your device manually to restore all feature defaults.

The main benefit of this service is being able to quickly adjust these features using ADB commands at scale. While the ability to enable and disable some of these features already exists in Oculus Developer Hub (ODH) or in-headset via Settings, these methods are burdensome when conducting high-volume tests involving multiple devices.

Streamlined Device Setup

In addition to adjusting system features, Meta Quest scriptable testing services enable you to use the WIPE_DEVICE and SETUP_FOR_TEST commands to prepare your devices for testing and ensure subsequent tests don’t interfere with each other. These commands allow you to:

Factory reset your device

Configure and connect to WiFi

Whether you’re testing multiplayer features using multiple headsets or running tests on one device, we want to reduce the amount of friction you encounter when testing. Configuring your device for testing no longer requires starting up a desktop app like ODH or physically putting on your headset.

Prepare for E2E Testing

Before you dive into E2E testing, make sure that you have all of the necessary tools and permissions:

Install ADB and fastboot on your development workstation if it’s not already installed (e.g., by installing the relevant Android SDK Platform Tools⁠ package).

On Windows workstations, also install the Oculus ADB drivers.

Make sure your headset(s) are updated to OS v44 or later.

Log into your headset(s) with your Verified Oculus Developer account or a test user account. Test users are ideal when multiple accounts and headsets are used in your testing. Take note of the test user’s email, password, and PIN.

Ready the device for first use by logging in with either your developer account or one of your test user accounts. You can do this by either putting on the headset and following the standard user setup flow, or by using the “Setup New Device” feature in ODH.

While the new built-in service prepares your devices for automated testing, it does not run or validate the test itself. You have multiple options to help you prepare a driver or framework for testing regardless of your preferred engine. These tools can help you prepare, record, and validate your test:

AutoDriver: a Meta-developed, engine-agnostic framework for recording user inputs and playing them back on a headset (e.g., to drive an E2E test).

Unity Testing Framework⁠: a Unity-specific framework for creating, running, and validating tests.

Unreal Engine Gauntlet Automation Framework⁠: a UE-specific framework for creating, running, and validating tests.

To get started using Meta Quest scriptable testing services, visit our documentation.

Please note that using these features for non-developers or for purposes other than the development of Meta Quest software is not supported and may degrade the lifetime of the headset.

Automation

ODH

Platform SDK

Quest

Unity

Unreal

Did you find this page helpful?

Explore more