Rules and regulations: Assuring you’ve constructed a Certification ready game
summary
Start reading platform requirements by Alpha and maintain a single source of truth (spreadsheet) that tags every requirement as yes/no/unknown, maps test cases to where they occur, and guides internal and outsourced CQA. Expect 3–4 unplanned passes that each take 5–10 business days; passing first time is rare (about 2 passes in 17 years). Focus engineers on save/load and suspend/resume, account linking, localization/terminology and online/UGC flows; run internal certification passes early to catch design-level rework.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:56Certification preparation importance
- 11:52Risks of unprepared attempts
- 12:13Read requirements at Alpha
- 17:42Internal QA testing
- 23:51External certification QA
- 29:40Prioritizing certification fixes
- 33:22Best testing timing practices
- 35:16Problematic certification systems
- 38:44Automated testing and waivers
- 40:54Waivers: small vs large projects
- 42:40Passed and failed examples
- 44:53Q&A
related talks
35mQA in GameDev. How to: build outsource processes, hire right people, successfully release projects
45mSame Old Story: Foundation of the QA Department. Tips and Tricks
16mStrategy for Acing Continuous Testing
38mA Game of Testing
49mOptimizing QA Flow to Minimize Time to Release While Meeting Quality Standards
44mTaking CI and automated testing seriously
48mWeb — The Magic of QA Processes in (Super) High-Load Systems
43mCan you Test it