Explore

QA Policy

Quality Assurance (QA) Policy

QA Sign-Off → No feature is considered “done” until it has been fully tested and approved by the QA team.

Build Verification → Every build must be thoroughly tested and verified before any external release or submission.

Bug Prioritization → Bugs that impact player experience (such as crashes, blockers, or major gameplay issues) will always be treated with the highest priority.

Developer Responsibility →

Each developer must test their own feature or build before submitting it to QA.

Developers are required to review and complete the build checklist before handing it over to QA.

Producer Approval →

No build will go to QA without the Producer’s consent.

The Producer must review and approve the build for QA submission; otherwise, QA will not accept it.

QA Substitution →

If the QA team is unavailable, the Producer will temporarily act as QA and will have full authority over QA decisions during that period.

Collaboration → QA and Development teams must work together to ensure every build is stable, polished, and player-ready before release.

Build Versioning → Each testing version must have a unique version number (e.g., 0.0.3 → 0.0.31 → 0.0.32 → 0.0.33, etc.) to ensure clear tracking of all internal testing builds.

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.