Game Testing Framework Runner

Execute comprehensive game testing suites including unit tests, integration tests, performance benchmarks, and automated gameplay validation.

When to Use This Command

Run this command when you need to:

• Run the full game testing suite including unit tests, integration tests, and performance benchmarks
• Execute automated gameplay tests that validate game mechanics, AI behavior, and progression systems
• Generate test coverage reports and performance regression analysis across target platforms

Consider alternatives when:

• You need to write new test cases rather than execute existing ones
• Manual playtesting is more appropriate for subjective quality assessments

Quick Start

Configuration

Copy
name: game-testing-framework-runner
type: command
category: game-development

Example Invocation

Copy
claude command:run game-testing-framework-runner --suite all --platform desktop

Example Output

Game Testing Framework: Unity Test Runner
Platform: Desktop (Windows x64)
Test Suites: unit, integration, performance, gameplay

Unit Tests:
  [+] Core mechanics: 142/142 passed (0.8s)
  [+] Data serialization: 38/38 passed (0.3s)
  [+] Utility functions: 67/67 passed (0.2s)

Integration Tests:
  [+] Scene loading: 18/18 passed (4.2s)
  [+] Save/load system: 12/12 passed (2.1s)
  [+] Networking: 8/8 passed (3.4s)

Performance Benchmarks:
  [+] Combat scene: 62 FPS avg (target: 60) PASS
  [+] Open world: 45 FPS avg (target: 30) PASS
  [WARN] Menu transition: 340ms (target: 200ms)

Gameplay Validation:
  [+] Tutorial completion: bot completed in 4m 12s
  [+] Level 1 clearable: bot cleared in 6m 44s
  [+] Save corruption check: 100 cycles, 0 failures

Results: 285 passed, 0 failed, 1 warning
Coverage: 74% of game systems tested

Core Concepts

Game Testing Overview

Aspect	Details
Unit Tests	Core game logic, math functions, data structures, state machines
Integration Tests	Scene loading, save/load, networking, asset management
Performance Tests	Frame rate benchmarks, memory profiling, load time measurements
Gameplay Tests	Bot-driven game progression, AI validation, balance verification
Platform Tests	Build verification on each target platform and device category

Test Execution Workflow

  Test Request
       |
       v
  +-------------------+
  | Select Test Suite |---> Unit / Integration / Perf / Gameplay
  +-------------------+
       |
       v
  +-------------------+
  | Setup Environment |---> Build test player, mock services
  +-------------------+
       |
       v
  +-------------------+
  | Execute Tests     |---> Run suites with timeout guards
  +-------------------+
       |
       v
  +-------------------+
  | Collect Metrics   |---> FPS, memory, timing, pass/fail
  +-------------------+
       |
       v
  +-------------------+
  | Generate Report   |---> Coverage, regression, recommendations
  +-------------------+

Configuration

Parameter	Type	Default	Description
suite	string	all	Test suite: unit, integration, performance, gameplay, or all
platform	string	current	Target platform: desktop, mobile, console, web
fps_target	integer	60	Minimum acceptable frame rate for performance tests
timeout_min	integer	30	Maximum time in minutes for the entire test run
coverage	boolean	true	Generate test coverage report after test execution

Best Practices

1. Run Unit Tests on Every Commit - Unit tests for game logic should complete in under 30 seconds. Include them in pre-commit hooks or CI triggers so regressions are caught immediately.

2. Benchmark Against Minimum Spec - Performance tests should run on hardware matching your minimum supported specification, not on high-end development machines. A test that passes on a developer GPU may fail on the target device.

3. Automate Gameplay Progression Tests - Create bot players that can complete tutorial flows and early levels. These tests catch softlocks, broken progression gates, and balance issues that unit tests cannot detect.

4. Track Performance Over Time - Store benchmark results from each test run and plot trends. A gradual 2% FPS decrease per week is invisible in individual test results but becomes a 25% regression over three months.

5. Test Save File Compatibility - Verify that save files from previous versions load correctly in the current version. Players who lose progress due to save incompatibility will leave negative reviews.

Common Issues

1. Tests Pass Locally But Fail in CI - The CI environment may not have a GPU or display server. Use headless rendering mode and software rendering fallbacks for CI environments that lack graphics hardware.

2. Performance Tests Show High Variance - Frame rate measurements fluctuate between runs due to background processes or thermal throttling. Run benchmarks multiple times, discard outliers, and report the median.

3. Gameplay Bot Gets Stuck - The automated player cannot navigate a particular section. Add waypoint hints or fallback behaviors to the bot, and flag sections where the bot fails as candidates for UX review.