Compliance 1, BVT: 0-1 XDB

[FearTheTJ]

Requirements The XDB file provided by the Publisher must work with the submitted build of the title.
Tools 1. API Monitor
Configuration None
Definition None
Steps 1. Connect API Monitor to the console using the following steps.
a. In API Monitor Select Settings > Select Development Kit and ensure the in use Development Kit is selected
b. Select Settings again, then select Set XDB Path and copy and paste the path of the XDB file into API Monitor
2. When launching the title press Start in API Monitor
Documentation Compliance runs Build Verification Tests to ensure that a title can be fully tested against the TCR test cases. BVTs are run against all submissions. Titles that are missing files or information are placed on hold for a maximum of 48 hours to resolve all issues. It is critical for titles that have complex XLSP features to resolve front end XLSP issues quickly so that all issues can be resolved within 48 hours.
Result In the Modules area of API Monitor, the output should read default.xex and show the correct path to the XDB file.
Pass Examples • The XDB (or PDB) files allow APIMon to connect to ALL of the title’s executables.
Fail Examples Final Submission Delayed Rejection*
• The XDB only allows APIMon to connect to some of the titles executables.
• The XDB does not allow APIMon to connect to any of the titles executables.
• No XDB has been provided.
• No XDB has been provided for DLC containing executables.
*Working files are requested via Mastering Lab and must be verified as working within 48 hours.

Optional Submission (Allow into test but must fix for Final Submission)
• The XDB only allows APIMon to connect to some of the titles executables.
• The XDB does not allow APIMon to connect to any of the titles executables.
• No XDB has been provided.
• No XDB has been provided for DLC containing executables.
NA Examples None
Analysis None
Faq None
Hardware 1. Development Kit