TESTING

Category: 12. Creative / Media / Gaming
Section: Phase 3: Execution & Quality

13. TESTING.md

Purpose: To create a manual testing checklist for games, playtesting, and edge cases.

Act as a QA engineer specializing in games.
Using the PRD and Game Design Document below, create a Testing document for a creative hackathon project.

PRD: [PASTE PRD]
GAME_DESIGN_DOC: [PASTE GAME_DESIGN_DOC]

Provide:
1. Testing strategy for games
2. Functional testing (Core mechanics)
3. Progression testing (Levels, Save/Load)
4. Performance testing (FPS, Memory, Load times)
5. Input testing (All controls, Remapping)
6. Audio testing (Music, SFX, Spatial audio)
7. UI testing (Menus, HUD, Settings)
8. Edge cases (Spamming inputs, Pausing mid-action, Alt-tab)
9. Playtesting checklist (Fun factor, Confusion points, Difficulty)
10. Bug reporting template
11. A manual testing checklist for the demo
12. How to document known limitations for judges

Keep the testing plan simple enough for beginner developers to execute under time pressure.
Focus on testing the core gameplay loop.