Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This topic describes features that are only available to Managed Creators with appropriate permissions. For details, speak to your Microsoft contacts.
Use prerelease testing to ensure that your product is of high quality, its service interactions are robust, and it's ready for release.
Overview of prerelease testing options
You can test your product in your own sandboxes or in the RETAIL sandbox. The following options are available.
Sideloading (Console)/Local Install (PC): Manually install your product on your PC or console in a development sandbox by using the Game Development Kit (GDK) development tools. You can install a package generated with makepkg or deploy loose files.
Development sandbox download: Publish a package to your development sandbox using Partner Center. Make the package available for download from the Microsoft Store app using an Xbox development kit or a PC configured with user access to the sandbox.
Closed Beta: Publish your game to the RETAIL (production) sandbox such that it's hidden from the public and can only be acquired from the Microsoft Store via redemption of a promotional code.
Open Beta: Publish your game to the RETAIL sandbox such that it’s available to all players for free, via a download from the Microsoft Store.
Xbox Insider Program: The Xbox Insider Program lets you distribute a beta product securely via the Xbox Insider Hub app and only to the audiences you define. Through the program you can also gather feedback and bug reports that will help you prepare for the full release of your game.
For full definitions, requirements, and restrictions for game betas on any Microsoft platform, review the Xbox Games Store Policy, available from the Xbox Publisher Guide.
Sideloading (Console) and Local Install (PC)
Use sideloading (for Xbox console games) or local installation (for PC games) to immediately deploy Xbox packages that have been created with an /LU or /LT flag. There's no need to publish this package via your Partner Center product because the build is deployed directly to your device. You can deploy your content by using the GDK Tools.
Sideloading offers the fastest iteration time but might be less scalable than other options.
| Advantages | Disadvantages |
|---|---|
| Build deployment is directly in the hands of the development team. | An Xbox Development Kit is required for console games. |
| Builds can be deployed immediately after a build is completed, and there's no need to wait for publishing or for uploads to Partner Center. | Audience's scope is limited to users with development kits, development tools, and access to your development sandbox. |
| Debugging tools are functional in development environments. This helps troubleshoot issues with game clients. | Microsoft Store download process can't be tested for the base game or for Content Updates. |
Developer sandbox download
Packaged builds can be uploaded to your product in Partner Center and published to your development sandboxes, for download directly from the Microsoft Store app on your devkit or PC. This approach enables deployment to larger audiences, and it avails a more accurate simulation of the end-user experience than that which is possible using sideloading.
To maintain a high level of security, you must have an Xbox test account that has permissions to access the sandbox you’re using, and you must have access to the title itself.
Each Partner Center account has its own specific set of sandboxes and options for configuring access to these sandboxes. A sandbox name consists of a publisher's moniker of four or six characters, followed by a number from .0 to .99 (for example, XDKS.1). You can choose from any of these sandboxes for your development and testing needs. For more information, see Sandboxes.
For more information about publishing to your development sandbox, see Review and Publish.
| Advantages | Disadvantages |
|---|---|
| User management and build deployment are controlled by the development team. Xbox test accounts can be created or deactivated quickly and easily, and in bulk. | This option is available only to internal individuals and to groups with access to development consoles and your development sandbox. |
| Builds can be uploaded and published via Partner Center, and they are available for download within a few hours. | For console games, this option requires a development kit–enabled console. |
| Build iteration can be accomplished quickly, by uploading and publishing a new build in Partner Center. This also allows for accurate testing of Content Update and Intelligent Delivery downloads. | The speed and frequency with which new updates to the published packages can be made available is dependent on the upstream bandwidth and integrity of your internet connection and the ingestion and processing time for packages on Partner Center. |
| Debugging tools are functional in development environments. This helps troubleshoot issues with game clients. |
Testing of beta products in RETAIL
PC and Console games can be configured for two types of beta releases: closed to a curated audience, and open to the public. The audience type and size of your audience determines the limitations, distribution types, and Xbox Requirements (XRs) that apply.
A beta should be a separate product from the full game release, with its own Xbox services, pricing and availability configuration, and Microsoft Store Product Details Page (PDP). In some scenarios, you might be able to use your full game product. For more information, speak to your Microsoft contacts.
The Xbox Insider Program complements your beta release and can be used as both a distribution and a feedback platform. More information about this program is provided in the following sections.
Closed beta
A closed beta is available only to users you select.
- Work with your Microsoft contacts to entitle players based on ownership of another product (for example to offer access to a beta product as part of a pre-order)
- Create and distribute Promotional Codes, which can be generated directly through Partner Center or via the Microsoft Token Specialist. For more information, see Ordering promotional codes.
- Tokens must be distributed in accordance with the Xbox Games Store Policy, available for download from the Xbox Publisher Guide.
Closed betas that are distributed to fewer than 10,000 users must comply with the Certification Requirements for Betas, but they are not tested by Xbox Certification. A Microsoft review is completed for all submissions. Closed betas that are distributed to 10,000 or more users are subject to both testing of the Beta Requirements by Xbox Certification and Microsoft review. If you are distributing your closed beta using the Xbox Insider Program, a closed beta can target up to 50,000 users before being subject to testing of the Beta Requirements by Xbox Certification (Microsoft Review is still completed).
For information about the policies that apply to a closed beta, including those for monetization and availability of the beta product, refer to the Xbox Games Store Policy in the Xbox Publisher Guide.
Open beta
An open beta is distributed as a free offer through the Microsoft Store, and must be available to everyone for download and play. All open betas are subject to testing of the Certification Requirements for Betas by Xbox Certification. The beta must pass Certification before it can be released to the public. With the exception of Free-to-Play titles, an open beta must be configured as a Game Demo product in Partner Center and be separate from your full game product.
For information about the policies that apply to an open beta, including those for monetization and availability of the beta product, refer to the Xbox Games Store Policy in the Xbox Publisher Guide.
Xbox Insider Program: Testing in RETAIL
You can start using the Xbox Insider Program as soon as you have a package that can be published to the RETAIL sandbox. This process is referred to as Flighting. The packages you use do not need to pass Certification before they can be used with the Xbox Insider Program unless you exceed the thresholds described in the Certification Requirements for Betas. Flighting can be used for base game products or for Content Updates (CUs). It's a convenient and secure way to test your product in the RETAIL sandbox.
Some benefits of the Xbox Insider Program include:.
Security: Make your product available only to select audiences. Grant access to the product using Promo Codes that are redeemed through the Xbox Insider Hub app such that the code is never shown to the user. You can also keep Flights private using Private Audience.
Flexibility: Target audiences as small as your development team or studio, or invite millions of Xbox Insiders to participate in your Flight. With Partner Center, you can also Flight multiple builds simultaneously, at any time and to anyone you choose. Scale or change your offering as you need to. For more information about publishing Content Updates and multiple builds, see Updating your title in the RETAIL sandbox later in this topic.
Custom Reporting: Gather feedback and bugs from Xbox Insiders by using Surveys and Report a Problem options available in the Xbox Insider Hub app, and receive summary reports regularly.
For example, you can use this option to conduct take-home test sessions among members of your studio, without having to bring your office development kit consoles home. To join, use separate production Microsoft Accounts. Use a combination of Private Audience (see Visibility - Audiences) and Xbox services Embargo to keep your product and Xbox services configuration hidden from other users.
With the Xbox Insider Program, you can follow your early development time frame and continue to expand your audience into your beta phases. This will help you keep your testing streamlined and methodical as your product matures and gets ready for testing by more users.
For more information about the Xbox Insider Program and onboarding.
- Contact your Microsoft representative or the Xbox Insider Program team
- View the steps to get started at Xbox Insider Program flighting
| Advantages | Disadvantages |
|---|---|
| Involves little or no console configuration. Uses retail consoles, or development kits with developer mode disabled. | Iteration is slower, because all updates are submitted through the standard release pipeline (including Certification if applicable). |
| Hides Promo Codes, preventing users giving them away or selling them. | Debugging tools are not supported in RETAIL. |
| Has reduced Xbox Certification requirements (up to 50,000 users). | |
| Exercises production services from end to end. | |
| Lets you securely target a much wider audience than that possible with sideloading or development sandbox downloads. In some scenarios, audiences can be targeted according to the developer-designated criteria, such as playing a previous game in a franchise. | |
| Offers optional, ready-made feedback mechanisms. |
Comparing beta distribution options
This table shows the differences between the various methods of testing and distributing your beta title.
| Feature | Closed Beta | Open Beta | Insider Program Closed Beta | Insider Program Open Beta | Xbox Game Preview |
|---|---|---|---|---|---|
| Participation | Limited - Invitation-only friends and family - Selected public participants - Might require an NDA (for example, click-through) - Might be capped to a finite number of participants - Might be bound to preorder or other bounty |
Everyone | - Limited audience, such as friends and family, or select member of the public - Criteria for selecting an audience automatically are available and involve the console type, engagement level, and existing entitlement's ownership - Common Terms of Use available - Can be capped to a specified number of participants - Can be bound to a preorder or other bounty - Can be monitored for leaks and leak vectors. |
Everyone | Everyone |
| Distribution | Promo codes or hidden offers | Microsoft Store app via a publicly available offer | Secure assignment and redemption of promo codes via the Xbox Insider Hub app | Secure assignment and redemption of promo codes via the Xbox Insider Hub app | Microsoft Store app via a publicly available offer |
| Monetization | Not permitted | Not permitted | Not permitted | Not permitted | Permitted in line with the policies defined in the Xbox Games Store Policy and Xbox Game Preview program documentation available in the Xbox Publisher Guide. |
| Xbox Certification | < 10,000 users: Microsoft Review only >= 10,000 users: Microsoft Review and Beta Xbox Requirements |
Microsoft Review and Beta Xbox Requirements | < 50,000 users: Microsoft Review only >= 50,000 users: Microsoft Review and Beta Xbox Requirements |
Microsoft Review and Beta Xbox Requirements | Microsoft Review and Game Preview Requirements |
| Product | Separate beta product. Entitlement can't be revoked. | Separate beta product. Entitlement can't be revoked. | Separate beta product unless an agreement to the contrary is reached with your Microsoft representative and Xbox Games Store Policies are adhered to. | Separate beta product unless an agreement to the contrary is reached with your Microsoft representative and Xbox Games Store Policies are adhered to. | Same product as a full release. |
| Feedback Mechanisms | None provided by Microsoft. Must be self-managed. | None provided by Microsoft. Must be self-managed. | Available built-in announcements, surveys, and bug filing. Daily summarization of surveys and bug reports. | Available built-in announcements, surveys, and bug filing. Daily summarization of surveys and bug reports. | None provided |
Securing the visibility and distribution of your title
The following sections explain how you can use features in Partner Center to ensure that your title is only discoverable and accessible by the players you choose.
For more information about security and confidentiality when Flighting with the Xbox Insider Program, see Xbox Insider Program flighting.
Private Audience
The Pricing and Availability module in Partner Center enables you to specify either a Public or Private Audience for your product. With Private Audience, your Microsoft Store Product Details Page (PDP) is only visible to user groups of your choosing. It offers the ability to schedule when the product's availability transitions from private to public (if required). You can manage the user groups that have access in Partner Center or, if you are Flighting with the Xbox Insider Program, have it managed automatically.
For more information about Private and Public audience, see Visibility - Audiences.
Hiding Xbox services information on the Xbox network
For any closed beta products you publish to the RETAIL sandbox, consider configuring Xbox Embargo. Xbox Embargo prevents elements of your Xbox services Gameplay Settings such as Achievements and Presence from being accessible outside of the game, for example in the Xbox shell UI or your Xbox user profile. See Configuring Xbox services for more information.
Creating and distributing promotional codes
Promotional codes are also known as promo codes, tokens or 5×5s. They are a 25-character sequence that's used to redeem content in the Store. To provide access to a closed beta product, you must distribute tokens to your intended audience.
- If you're testing or Flighting without the Xbox Insider Program, you can distribute promo codes directly to your intended audience. Options include, but aren't limited to: setting up a website and distributing promo codes from a sign-up flow, distributing tokens in a portal, distributing tokens via automated mail, or simply sending them via mail or message. The downside to this method is that the promo codes are visible to the user, who might publicly display or redistribute them.
- If you’re Flighting with the Xbox Insider Program, promo codes can be systematically and securely distributed through the Xbox Insider Hub, granting the entitlement to users without ever displaying the promo code. This eliminates the risk of the code being displayed or redistributed.
Note
If you don’t need your product to be hidden, for example, if you are distributing an open beta, you can offer it for free to all players via your Partner Center Pricing and Availability configuration. For details, see Create and release products that are visible and purchasable in the Microsoft Store.
Updating your title in the RETAIL sandbox
After you have released your game in the RETAIL sandbox, you will update it using Content Updates (CUs). You can test these updates in RETAIL before you make them available to the General Audience (GA).
Note
All CUs require Certification approval before they can be published to GA. Speak to your Microsoft contacts about the Certification requirements for your product.
Standard Content Update (CU) publishing
After your update receives Certification approval, you can proceed with publishing the update to RETAIL when you are ready. This will make the update to available to any players in GA that have access to your product. Any players with the previous package installed can update to the new package. Anyone who installs the product for the first time will download the updated package.
Package Flights
Package Flights to enable you to provide specific packages to a designated set of users or devices and without disrupting the experience of your other customers. Only the packages are different; the Microsoft Store PDP will be the same for all players. If you're creating a Package Flight for a console game, you can publish it to a Known Device Group. If you're creating a Package Flight for a PC game, you can publish it to a Known User Group. You can manage these groups via the Engage > Customer Groups UI, accessible from the Apps and Games dashboard. If you're Flighting with the Xbox Insider Program, the Xbox Insider Program team will work with you to populate these groups systematically through the Xbox Insider Hub.
Note
A considerable benefit of Package Flighting is that you can Flight different packages to different groups of players simultaneously. If you're participating in the Xbox Insider Program, players will receive the package that's available to their group and can provide build-specific feedback.
For more information, see How to configure package flights for game packages.
Retail Test Environments (RTEs)
RTEs are separate versions of a title, created as a Game Demo product in Partner Center, that are released after the full release of a title. RTEs let customers test and provide feedback on content and features that are in development, before they become available to the public. Speak to your Microsoft contacts if you are considering an RTE for your product.
For full information about the requirements to distribute an RTE, see the Xbox Games Store Policy in the Xbox Publisher Guide.
Prerelease testing of base game products
After your game has passed Final Certification, you're required to test it in the RETAIL sandbox by using promo codes and test discs (if your title supports a physical release). For more information, see RETAIL Publishing and Testing or reach out to your Microsoft contacts.