Game Test Design

<!-- Powered by BMAD-CORE™ -->

# Game Test Design

**Workflow ID**: `_bmad/bmgd/gametest/test-design`
**Version**: 1.0 (BMad v6)

---

## Overview

Create comprehensive test scenarios for game projects, covering gameplay mechanics, progression systems, multiplayer functionality, and platform requirements. This workflow produces a prioritized test plan based on risk assessment and player impact.

---

## Preflight Requirements

- ✅ Game design documentation available (GDD, feature specs)
- ✅ Understanding of target platforms
- ✅ Knowledge of core gameplay loop

---

## Step 1: Gather Context

### Actions

1. **Read Game Design Documentation**
   - Locate GDD or game-design.md
   - Identify core mechanics and features
   - Note target platforms and certification requirements

2. **Identify Critical Systems**
   - Core gameplay loop
   - Progression/save systems
   - Multiplayer (if applicable)
   - Monetization (if applicable)

3. **Assess Risk Areas**
   - Player-facing features (highest priority)
   - Data persistence (save/load)
   - Platform certification requirements
   - Performance-critical paths

---

## Step 2: Define Test Categories

### Core Gameplay Testing

**Knowledge Base Reference**: `knowledge/playtesting.md`

| Category           | Focus                      | Priority |
| ------------------ | -------------------------- | -------- |
| Core Loop          | Primary mechanic execution | P0       |
| Combat/Interaction | Hit detection, feedback    | P0       |
| Movement           | Physics, collision, feel   | P0       |
| UI/UX              | Menu navigation, HUD       | P1       |
| Audio              | Sound triggers, music      | P2       |

### Progression Testing

**Knowledge Base Reference**: `knowledge/save-testing.md`

| Category     | Focus              | Priority |
| ------------ | ------------------ | -------- |
| Save/Load    | Data persistence   | P0       |
| Unlocks      | Content gating     | P1       |
| Economy      | Currency, rewards  | P1       |
| Achievements | Trigger conditions | P2       |

### Multiplayer Testing (if applicable)

**Knowledge Base Reference**: `knowledge/multiplayer-testing.md`

| Category        | Focus               | Priority |
| --------------- | ------------------- | -------- |
| Connectivity    | Join/leave handling | P0       |
| Synchronization | State consistency   | P0       |
| Latency         | Degraded network    | P1       |
| Matchmaking     | Player grouping     | P1       |

### Platform Testing

**Knowledge Base Reference**: `knowledge/certification-testing.md`

| Category      | Focus               | Priority |
| ------------- | ------------------- | -------- |
| Certification | TRC/XR requirements | P0       |
| Input         | Controller support  | P0       |
| Performance   | FPS, loading times  | P1       |
| Accessibility | Assist features     | P1       |

---

## Step 3: Create Test Scenarios

### Scenario Format

For each critical feature, create scenarios using this format: