# Game Test Design - Validation Checklist

---

## Prerequisites

- [ ] Game design documentation reviewed
- [ ] Core mechanics identified
- [ ] Target platforms known
- [ ] Risk areas assessed

---

## Context Gathering

- [ ] GDD or feature specs located
- [ ] Core gameplay loop understood
- [ ] Progression systems identified
- [ ] Multiplayer requirements known (if applicable)
- [ ] Platform certification needs identified

---

## Test Categories

### Gameplay Tests

- [ ] Core loop scenarios created
- [ ] Combat/interaction tests defined
- [ ] Movement/physics tests defined
- [ ] UI/UX tests defined

### Progression Tests

- [ ] Save/load scenarios created
- [ ] Unlock system tests defined
- [ ] Economy tests defined
- [ ] Achievement tests defined

### Multiplayer Tests (if applicable)

- [ ] Connectivity scenarios created
- [ ] Sync validation tests defined
- [ ] Latency tests defined
- [ ] Matchmaking tests defined

### Platform Tests

- [ ] Certification requirements covered
- [ ] Input handling tests defined
- [ ] Performance criteria established
- [ ] Accessibility tests defined

---

## Scenario Quality

- [ ] All scenarios use GIVEN/WHEN/THEN format
- [ ] Scenarios have clear expected outcomes
- [ ] Priorities assigned (P0-P3)
- [ ] Categories assigned
- [ ] No duplicate scenarios
- [ ] Edge cases considered

---

## Prioritization

- [ ] P0 scenarios cover ship blockers
- [ ] P1 scenarios cover major features
- [ ] Priority distribution is reasonable
- [ ] Risk-based ordering applied

---

## Documentation

- [ ] Test design document created
- [ ] Overview section complete
- [ ] Risk assessment included
- [ ] Coverage matrix generated
- [ ] Automation recommendations provided
- [ ] Next steps defined

---

## Completion Criteria

- [ ] All critical systems have test coverage
- [ ] Scenarios are actionable and testable
- [ ] Document is ready for team review
- [ ] Automation candidates identified

---

**Completed by:** {name}
**Date:** {date}
**Scenario Count:** {count}