Meta Developers

Distribute

Test Users

Updated: Feb 7, 2025

As a Meta Quest developer, you can create and use test users to test your app before release.

Test user accounts are not connected to your personal Meta account, but test user accounts are automatically linked to a Meta test user account so you can test features that might require a Meta account. Because the test user has a Meta test user account connected to it, data generated based on the test user account activities will be used in accordance with the Supplemental Meta Platforms Technologies Privacy Policy, the Meta Privacy Policy, and the Meta Quest Privacy Policy Requirements.

What can you do with test users?

Almost any action you can perform with a Meta Quest account can be performed with a test user account.

Test users:

Can be used in place of a personal Meta account to sign in to a headset and test your apps.
Can test In-App Purchases (IAP) and subscriptions, and purchase them with test payment methods. For more information about testing IAP, see Add-ons Server APIs. For more information about testing subscriptions, see Server APIs for Subscriptions.
Can test entitlement checks, and be added to release channels. For more information about testing Entitlement Checks, go to engine-specific documentation: Unity, Unreal, and Native.
Can test your app’s support of parent-managed Meta accounts. Parent-managed test users are the recommended way for adults to test their app’s experience for children under 13.
Can playtest your app before release (including multiplayer functionality), can be created and deleted in bulk, and do not provide further access to your organization’s Developer Dashboard, making them ideal for QA testing.

Requirements for working with test users

These steps must be completed prior to working with test users:

Enable Developer Mode.
Verify your developer organization.

Creating test users

Use the following steps to create test users in the Developer Dashboard:

Open your browser and navigate to the Developer Dashboard.
From the left-side navigation, choose Test Users. If you don’t see the option, choose the dropdown menu at the top of the left-side navigation bar and click View All to open the Org Manager.
Click Add Test User.
Fill out the Create Test User form with the following:
- Username prefix: (required): The prefix you choose will be used to generate a username. For example, if you choose the prefix “testing,” we will generate a username like testing_a1b2c3 for your test user account. The prefix must be between 4 and 12 alphanumeric, underscore, or dot characters. It cannot have consecutive special characters and cannot start or end with them. We recommend not using externally identifying information for the username prefix.
- Email prefix (required): This is the prefix for the email address that will be automatically generated for the test user. For example, if you choose “testing” as the prefix, we will generate an email address like testing_1xYz23@tfbnw.net for the test user account. The prefix must be between 4-10 alphanumeric, underscore, or dot characters. It cannot have consecutive special characters and cannot start or end with them. We recommend not using externally identifiable information for the email prefix. Note that you will use this email address to log in to your headset.
- Password (required): Must be at least 8 characters long. Be sure to remember this, as it’s not visible on the dashboard. You will need to use this password to log-in to your headset.
- Pin (optional): The PIN can be used for buying items in the Meta Horizon Store. Must be 4 numeric characters long. Defaults to 1234 if nothing is entered.
- Locale (optional): If you don’t provide a locale, en_US will be used.
- Country (optional): If you don’t provide a country,** United States** will be used.
- User Count (required): This count is the amount of Test Users that are created with these settings. An integer between 1 and 5. Defaults to one.
- Inherit my organization entitlements (optional): By default, new test users will inherit the Role-based app entitlements granted to the developer who created the test user. (For instance, if the creator’s Role only allows access to certain apps, the test user’s entitlements will reflect that.) This includes only app entitlements granted as part of the developer’s Role in the organization, and does not include other apps the test user creator has purchased, or any in-app purchases.
- Make test user a Parent-managed Meta account (optional): By default, test users are configured to be adult accounts. Selecting this option creates a parent-child pair of test user accounts. The child account will have a “_youth” suffix added to its email address. This allows you to test parent and child flows on your app. Note that the parent test account and the child test account will use the same password and pin that you create here.
- Friend test users with each other (optional): When creating multiple users, click this checkbox to automatically make users friends.
Click Submit to create the test user(s).

After you click Submit, information about the test user(s) will appear as an item in the Test User table, including a randomly generated Name, Alias, and Email Address.

Note: You cannot access any emails sent to the test account’s email address.

Add test accounts to your headset

After you’ve created a test account, use the following steps to add it to your headset.

Note: If you wish to add a child test account, you’ll have to go through the following steps twice. First, add the parent test account, then add the child test account.

Start the following steps on your computer:

Navigate to https://auth.meta.com/device
Click the menu option in the upper right corner and click Log out.
Click Continue with email.
Type in the email address for the parent test account you created in Creating test users and click Next.
Click Enter password instead.
Type in the password for the parent test account you created in Creating test users and click Log in.
Choose your cookies option for the test account. After you’ve finished this step, you’ll need to power on your Meta Quest device and wear it for the next few steps.
Switch to your headset:
Select Settings.
Select Accounts.
Select Add Account. Note that you can only have 4 accounts on your headset at one time.
Select Skip to skip sharing apps. Note that test accounts can’t share apps on a headset.
You will either see a prompt to ensure your headset is connected to the internet or a box to enter an email address.

If you see the prompt

Select Continue to add an account to the headset.
Make a note of the eight digit code to connect your test account to your headset, remove your headset, and return to your computer.
Switch to your computer:
Navigate to https://auth.meta.com/device.
Choose the test account you created in step 3 above.
Enter the 8 digit code you got from your headset in step 13 above.
Click Connect your device and put on your headset again.
Switch to your headset:
Use your Meta Quest device to complete the account setup prompts.

If you see a box to enter an email address

Enter a valid email address and click Send link to receive a login link in your email. Note: Do not enter the test account’s email address, which is inaccessible. You should enter any email address that is accessible from the computer that is logged into the test account. It does not need to be associated with any Meta account.
Switch to your computer:
Open your email and click the Continue button in the email to open the link in a browser.
Choose the test account you created in step 3 above.
Click Add account and then put on your headset again.
Switch to your headset:
Use your Meta Quest device to complete the account setup prompts.

Test users will be visible to non-test users in social / multiplayer settings. However, they cannot be friended. Test users can be configured to be friended with other test users in your organization. See Manage Friends for more details.

Manage test accounts

Most controls for test accounts are managed in the Developer Dashboard. Additional controls for child test accounts are managed by logging into Family Center with their parent test account. In all other cases, navigate to Test Users in the developer dashboard to manage test user settings:

View test user data
Manage Friends
Configure App Entitlements
Manage Add-on entitlements
Manage Test Credit Cards
Bulk Delete Test Users
Export Test Users to a CSV File

View test user data

The View test user data modal displays detailed information about a test user, such as their country and the account that created that test user.

Open your browser and navigate to the Developer Dashboard and click on your app.
Expand Development in the left-side navigation, and click Test Users.
Click the ellipses (...) menu on a test user.
Click View test user data.

Manage Friends

The Manage Friends modal allows you to view and modify friend relationships with other test users in your organization.

Open your browser and navigate to the Developer Dashboard and click on your app.
Expand Development in the left-side navigation, and click Test Users.
Click the ellipses (...) menu on a test user.
Click Manage Friends.
- Users not connected will have an Add Friend button that can be clicked to make Test Users friends.
- Users already connected will have a green check mark with friends. Click the Friends button to unfriend users.

Configure App Entitlements

The Configure App Entitlements modal allows you to determine whether test users should inherit the app entitlements granted to the developer who created the test user.

Open your browser and navigate to the Developer Dashboard and click on your app.
Expand Development in the left-side navigation, and click Test Users.
Click the ellipses (...) menu on a test user.
Click Configure Entitlements.
- Check the Inherit my organization entitlements check box to have this test user inherit the app entitlements granted to the developer who created the test user. (For instance, if the creator’s Role only allows access to certain apps, the test user’s will only receive entitlements to those apps.) The test user’s creator can be seen in the View test user data modal.
- Clearing the Inherit my organization entitlements check box will revoke developer app entitlements. When this is cleared, the test user won’t inherit the test user owner Organization developer entitlements. However, if the test user has purchased an item, it will still be in their entitlements.

Adding Entitled Apps to Library

Use the following steps to add apps to the test user’s library on the Meta Quest device you are using to test the experience:

Open the Meta Horizon app on your phone.
Sign to the app using the test users email and password.
Navigate to the Store tab.
Tap Add to Library for the apps the test user needs access to.

Manage Add-on Entitlements

Test users can grant/revoke add-on entitlements using the Manage Add-on Entitlements modal.

Open your browser and navigate to the Developer Dashboard and click on your app.
Expand Development in the left-side navigation, and click Test Users.
If you already have a test user, click the ellipses (...) menu on a test user. Otherwise, create a test user to continue.
Click Manage Add-on Entitlements from the drop-down menu.
Select both the App and the Add-ons that you want to modify the entitlement of in the Add-ons Entitlements modal.
Click Submit to confirm.

Manage Test Credit Cards

Open your browser and navigate to the Developer Dashboard and click on your app.
Expand Development in the left-side navigation, and click Test Users.
Click the ellipses (...) menu on a test user.
Click Manage Test Credit Cards.
- Click the checkbox next to a test credit card to make it a saved payment method for the test user. Click ‘Set Default’ to make it the test user’s default payment method.
- Test credit cards can only pass purchases with test users.
- Do not use a real credit card with test users, it will be charged as a regular transaction.
- Test credit cards can be added during a test user’s purchase flow. To do so, in addition to the test credit card number, provide any 5-digit zip code, any expiration date in the future, and 111 for the security code.

Bulk delete test users

Open your browser and navigate to the Developer Dashboard and click on your app.
Expand Development in the left-side navigation, and click Test Users.
Select multiple test users by clicking checkboxes.
Click the “[] selected” drop-down and then Delete.

Export test users to a CSV file

Test users can be downloaded to a CSV file to easily manage test user data for an org. For example, test users must be added to release channels in order to test Entitlement Checks and In App Purchases. You can use this generated CSV to create a list of test users’ email addresses rather than adding them to the channel one by one.

Open your browser and navigate to the Developer Dashboard and click on your app.
Expand Development in the left-side navigation, and click Test Users.
Select multiple test users by clicking checkboxes.
Click the “[] selected” drop-down and then Export CSV. The file will automatically download to your browser.

Note: The ID field might appear incorrect due to rounding by the software used to open the CSV.

Did you find this page helpful?