Testing as a production discipline
Test the rules, the experience and the failures.
A layered test plan
Cover rule examples with automated checks where practical, then test complete sessions and platform integration. Include legal moves, invalid moves, ties, scoring, restart and repeated input. Online modes additionally require authorization, reconnect and hidden-information checks.
A useful defect record
Record build identity, device, reproducible steps, expected result, actual result and evidence. Rate impact separately from how frequently the team has observed it. Do not hide a crash or lost progress among cosmetic issues.
Independent disciplines
Aarohi covers QA governance, Ananya inclusive design, Rutuja responsible play and Simran integrity. These reviewers remain under Eleanor, not Games management. Development test results support their review but do not replace their decisions.
Exit criteria
Retest fixed issues on the corrected build, run targeted regression and document unresolved limitations. Require no unresolved release-blocking defects under the agreed policy. Publish measured results only with dates, methods and candidate identity; there are no invented pass rates in this book.