Service level agreements
The following table details the service level agreements (SLAs) for XBOX Requirement testing against games releasing on XBOX consoles and XBOX on PC.Product types that require certification
All XBOX product types are subject to XBOX Requirement testing and must pass XBOX Certification before they can be released. Depending on your product and submission type, different requirements and processes might apply. The following types of products must go through XBOX Certification. Product types:- Full games
- Game previews
- Betas
- Demos
- Digital download only
- Disc only
- Disc and digital
- Content update
Certification test pass types
Consider the intent of the submission. If you are looking for directional feedback on release readiness, consider an optional submission. If you intend to release the submission on the XBOX network as a final product, choose a final submission.Optional submissions
Optional submissions are a paid testing service provided by XBOX Certification. They provide an opportunity to validate how a title is doing from a Certification perspective before submitting your release-candidate build. Optional submissions are recommended but not required. They give you a chance to discover show-stopping XR issues ahead of final submission and improve your chances of passing the first time. Optional testing is not a replacement for good QA, which is still essential throughout development. Optional submissions are per package and fees are applied accordingly. For example, if you have both XBOX One and XBOX Series X|S versions and want an optional submission for both, you must pay for each individually. For complete details on the Optional Submissions paid service, refer to the XBOX Certification Paid Services Program documentation. Optional submissions are only tested in the CERT.DEBUG sandbox, which is a Microsoft-controlled sandbox that only individuals in Certification have access to. It is a developer sandbox where only red-signed content is permitted to run (similar to yours). Discs are not created for optional submissions. For additional details and a list of the different tiers of optional testing, refer to the Optional Submissions documentation.Final submissions
Final submission is the last certification test pass before a product is released to the public or a disc is Released to Manufacturing (RTM). Communicate with your Microsoft contacts to plan and coordinate your final submission. Final submissions on console are entirely tested in the CERT sandbox, which is a Microsoft-controlled sandbox that only individuals in Certification have access to. It is a Retail sandbox where only green-signed content is permitted to run. A limited set of tests may be completed in the CERT.DEBUG sandbox with red-signed content, but the majority of testing of Final submissions is in the CERT sandbox. Certification consoles are retail consoles running the current OS Recovery that is published in RETAIL. PC final submissions are also tested in the CERT sandbox. Unlike optional submissions, final submissions are entirely tested on retail devices with green-signed binaries and discs. When a product passes final submission, a pass report is published and the product can be released. If a product fails final submission, a fail report detailing the Conditions for Resubmission (CFRs) is published. All CFRs identified in a fail report must be fixed before a resubmission. Resubmissions must be made the same way as the previous final submission.Add-on content
Games that support add-on content (durables and consumables) must have at least one product for each type of supported downloadable content (DLC) certified alongside the main game. For example, a racing game that plans to release tracks, cars, and packs of virtual currency would need to certify at least one track, one car, and one virtual currency pack add-on. Work with your Microsoft contact to ensure add-on content is published to the Certification sandboxes prior to optional and final submissions.Test disc verification
Products releasing on physical discs must have test discs ordered and approved by the XBOX Certification team. It is recommended, but not mandatory, that you place a disc order alongside the product being submitted for final certification. Test discs are ordered by the XBOX Certification team when a disc product has been submitted in Partner Center and BVTs have passed. Test discs are shipped to up to three destinations and to internal Microsoft addresses. These are silver discs, without artwork, that only contain basic information such as the BinaryID and manufacturing date. The product name and other information are not included for security reasons. Discs come in two formats: BD25 and BD50. Multi-disc format is supported but uncommon; work with your Microsoft contacts if that applies. All test discs require verification by XBOX Certification and the partner before they will be approved to Release to Manufacturing (RTM). It is critical that partners perform all necessary testing before providing approval to RTM. The disc tests performed by XBOX Certification are available in the Media Validation Test Steps document.Certification testing stages
When a submission is received by XBOX Certification, it is tested in three main stages:- Submission checks cover submission validator review and malware scanning.
- Build verification testing (BVTs) verify that the title is in a testable state and that any previously issued CFRs have been resolved.
- XBOX Requirement (XR) testing is the bulk of the testing and is where all applicable XR test cases are validated against your title.
1
Build a clean release build
Produce a fresh release build from source control with no local modifications.
2
Test the deployment of loose files
Deploy the loose files to a devkit and verify basic launch and functionality.
3
Build a submission package with MakePkg.exe
Use
MakePkg.exe with the appropriate switches so Submission Validator runs.4
Publish a build for sandbox download
Publish a build that can be downloaded from the Store in your development sandbox. Only users with sandbox access can download the build. This lets you acquire and test the title the same way Certification does.
Submission checks
There are two submission checks: Submission Validator and Malware scan.Submission Validator
Submission Validator gives feedback to developers and lets them address common problems that would cause titles to fail ingestion into Partner Center and/or Certification. When you runMakePkg Pack to produce a package for submission or testing, Submission Validator performs several error checks. Always use the most recent Submission Validator component to benefit from the latest validation and ensure that your title’s submission proceeds smoothly. Submission Validator is not a standalone tool; it is called automatically whenever the MakePkg Pack command is used with the /L or /LT switch. Submission Validator runs before the title package is created.
For detailed information about Submission Validator, refer to the Submission Validator GDK documentation.
Malware scan
To prevent viruses and other malware from contaminating your product, run a malware scanner of your choice against the package before submission. Confirm that the malware scanner has up-to-date definitions before scanning. There is no need to provide a log or other attestation from your malware scanner. Microsoft runs its own malware utilities against your submission when it is received. Running a malware scanner before submission ensures that you identify accidental infections early rather than waiting for Microsoft to find them.Build verification testing
Build verification testing (BVTs) is a reduced test pass designed to make sure a product is fully testable and properly configured before entering full certification testing. This is done by running a suite of test cases in the main areas of a product. All products must pass BVTs before they are scheduled for full certification testing. For an in-depth look at BVTs and additional guidance on how to avoid failing them, refer to:XBOX Requirement testing
Once a product has passed BVTs, it is scheduled for XBOX Requirement (XR) testing. The intent of the XR test pass is to validate product compliance with all applicable XRs for that submission and product type. XRs consist of the policies, technical requirements, and product-component requirements to which all developers and publishers of XBOX products must conform. XRs ensure that products created for XBOX are not only stable and reliable, but also provide a user experience that is consistent, safe, secure, and enjoyable.XBOX Requirements
A comprehensive list of XRs for each platform and product type:- Console: XBOX Requirements for XBOX Console Games
- PC: XBOX Network Policies for PC and Mobile (applies to all XBOX PC and mobile titles)
- Game Preview and Beta: XBOX Requirements for Open Betas and Game Previews
XBOX Requirement test cases
Each XR tested in Certification has a detailed test case that covers how the requirement is tested. Test cases include test steps, expected behavior, and pass/fail examples.- Console test cases: Certification Tested XBOX Requirements for XBOX Console Games
- PC test cases: XBOX Network Test Cases for PC, Mobile, and Creators Program (applies to all XBOX PC titles)
Certification issue types
Issues found during a Certification test pass are categorized by severity, probability, and repeatability.- Standard Reporting Issue (SRI): Typically related to an XR but not deemed severe enough to fail a title. Should be fixed in a future submission, but not required.
- Condition for Resubmission (CFR): Title-failing issues that violate the intent of an XR and are severe enough to prevent release. CFRs must be fixed before resubmission.
- Issue of Note (ION): Not related to an XR or XR test case. A developer may want to fix these, but they are not required.
- Non-Tested: If any XRs or test cases could not be tested during a test pass, a list is included in the report.
Placing submissions on hold
If an issue is found that blocks the Certification team from testing, a title is placed on Hold. Holds introduce delays that neither partners nor Certification want. Certification will inform your Microsoft contact of the reasons for the hold and work with you to resolve the issue. Common reasons a title may be placed on Hold:- Missing or non-functioning partner accounts that are required for testing.
- Partner services that do not support the CERT.DEBUG and CERT sandboxes.
- Multiplayer that does not work as expected.
Requesting exceptions
If your title is not fully compliant with any XBOX Requirement (XR), you can request an exception for that XR. This might occur if your title is introducing innovative features or if strong technical limitations prevent the title from meeting the XR. Work with your Microsoft contacts well in advance of submitting to Certification if an exception is needed. Approval is not guaranteed; obtaining advanced feedback gives you time to resolve any issues. You must close all outstanding exception requests before submitting your title for certification. Allowing time to discuss exceptions and resolutions can prevent delays. Microsoft does not want to block new or innovative features. If you are creating something new, please tell us in your exception request. To request an exception, reach out to your Microsoft contacts before submitting to Certification.Certification reports
All titles receive a report at the conclusion of test. Report type varies by Certification test pass type:- Optional Complete report
- Final Pass/Fail report
- Interim report