Certification week is the worst time to discover that your regression pass and the platform holder's requirements have drifted apart. Sony's TRC, Microsoft's Xbox requirements (XRs, formerly TCRs) and Nintendo's Lotcheck guidelines are all under NDA, so I won't quote them here. But the shape of what they care about is well known, and you can build a short, repeatable regression set around it so the last week before submission is confirmation rather than discovery.
This is the set I'd want any team to run on every candidate build in the fortnight before submission.
1. Suspend, resume and power states
Most cert failures I've seen discussed publicly are not crashes in gameplay. They're edge cases around the system.
- Suspend mid-load, mid-save, mid-cutscene and mid-match, then resume after a few minutes and after a long gap.
- Put the console into rest mode during an online session and resume. Does the game recover the session or fail gracefully with a clear message?
- Pull power during a save (on a dev kit you're happy to abuse) and confirm the save is either intact or cleanly rejected.
2. User and account changes
- Sign the active user out from the system menu during play.
- Switch profiles at the title screen and mid-game.
- Start the game with no user signed in, a guest, and a child account with restrictions.
- Check that saves, entitlements and achievements/trophies follow the correct user after every switch.
3. Network loss
- Disconnect the cable or Wi-Fi during matchmaking, during a match and during a store or entitlement call.
- Throttle to a poor connection rather than cutting it entirely; partial failures produce the strangest bugs.
- Confirm every error message is readable, uses platform-correct terminology and doesn't leave the player on a dead screen.
4. Storage and saves
- Fill storage until the save fails, and check the message.
- Corrupt a save file (on a dev kit) and confirm the game detects it rather than crashing.
- Verify cloud save conflicts are handled when two consoles have played the same profile.
5. Controllers and input
- Disconnect the controller in every major state: menus, gameplay, cutscenes, loading screens. The game should pause and prompt.
- Reassign controllers between users.
- Check button glyphs match the platform everywhere, including tutorials and loading-screen tips that are easy to forget.
6. Platform terminology and UI
- Search your string tables for the wrong platform's terms. A stray "Xbox" in a PlayStation build, or the wrong name for the system's own features, is a classic failure.
- Check safe-area and text legibility on a TV at typical viewing distance, not just on a monitor.
7. Achievements, trophies and activities
- Unlock every one in a clean run and confirm they fire once, for the right user, at the right moment.
- Check behaviour when unlocked offline and synced later.
Making it repeatable
Keep each section as a tagged suite in your test management tool, so the whole set can be run on any build in a day by two testers. Log the build number, kit firmware and tester for every run; certification teams will ask for that evidence, and you'll want it when a failure report comes back.
If your team is porting a PC or mobile game to console for the first time, the pre-cert checklist for console ports we published covers the earlier, pre-submission side of this.
Disclosure: I work with Juego Studios, where we run platform certification testing as part of our QA work. The checklist above is general and not tied to any one project.
Top comments (0)