Test Setup

Test Setup

Automated test runner configuration and setup for game engine testing environments

Category: content-creation Source: Donchitos/Claude-Code-Game-Studios

What Is the Test Setup Skill?

The Test Setup skill on the Happycapy Skills platform is an automated scaffolding utility designed to configure a robust testing environment for projects built with game engines. Its primary function is to set up the foundational pieces required for automated testing, including directory structures for tests, engine-specific test runner configurations, and continuous integration (CI) pipelines. By leveraging this skill, teams ensure their projects are equipped with the essential infrastructure for reliable automated testing and seamless integration with GitHub Actions from the very beginning of the development lifecycle.

The skill operates by detecting the selected engine, generating standardized test directories, and creating a ready-to-use GitHub Actions workflow for automated test execution. It is intended to be invoked once during the Technical Setup phase, before the start of active development and sprints, thereby embedding testing best practices into the project's DNA.

Why Use the Test Setup Skill?

Automated testing is a cornerstone of modern software engineering, particularly in game development where complex systems and rapid iteration are common. The Test Setup skill enforces the adoption of automated testing from the outset, delivering several key benefits:

  • Consistency: By generating standardized directory layouts and configurations, all team members work within a common structure, reducing friction and confusion.
  • Early Integration: Integrating testing and CI/CD pipelines early prevents costly technical debt. The SKILL.md notes that setting up the test framework at sprint start takes 30 minutes, while deferring until sprint four can cost three entire sprints.
  • Automated Quality Assurance: Establishing a GitHub Actions workflow ensures tests are run on every push, catching regressions early and maintaining code quality.
  • Engine Awareness: The skill tailors the setup based on the project's engine, ensuring compatibility and optimal configuration for tools like Godot, Unity, or Unreal.

By automating these tasks, teams are free to focus on feature development, confident that the foundational infrastructure for testing is robust and reliable.

How to Use the Test Setup Skill

The Test Setup skill is invoked during the Technical Setup phase, typically as a one-time command before any feature development begins. Here is a step-by-step breakdown based on the SKILL.md content:

1. Engine Detection

The skill reads the engine configuration from the .claude/docs/technical-preferences.md file, specifically extracting the Engine: value. This determines which test runner and configurations will be generated.

Example:

## .claude/docs/technical-preferences.md
Engine: Godot 4.2

If the engine is not yet configured (for example, the value is [TO BE CONFIGURED]), the skill halts and instructs you to run /setup-engine before proceeding.

2. Existing Infrastructure Check

Before making any changes, the skill audits the current state of the repository:

  • Checks whether the tests/ directory exists.
  • Checks for tests/unit/ and tests/integration/ subdirectories.
  • Checks for existing CI workflows in .github/workflows/.
  • Optionally, can detect engine-specific test runner files (for example, tests/gdunit4_runner.gd for Godot projects).

Example Check (Bash):

if [ ! -d "tests" ]; then
    echo "Creating tests/ directory"
fi

3. Directory and Configuration Generation

Depending on the detected engine, the skill generates:

  • A tests/ directory at the project root.
  • Subdirectories such as tests/unit/ and tests/integration/.
  • Engine-specific test runner configuration files (e.g., gdunit4_runner.gd for Godot, test_runner.cs for Unity).
  • A CI workflow file at .github/workflows/tests.yml that triggers automated test runs on every push.

Example Directory Structure:

tests/
  unit/
  integration/
.github/
  workflows/
    tests.yml

Example GitHub Actions Workflow for Godot:

## .github/workflows/tests.yml
name: Run Godot Tests
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Run GdUnit4 Tests
        run: godot --headless --script res://tests/gdunit4_runner.gd

4. Output Verification

After execution, you should see the new directory structure and workflow files in your repository. These provide the baseline for writing and running automated tests in your chosen engine.

When to Use the Test Setup Skill

Invoke the Test Setup skill once during the Technical Setup phase, before the first sprint or any code implementation. This is critical for maximizing the effectiveness of your automated testing strategy. Delaying setup until later sprints can result in significant technical debt and time loss, as highlighted in the SKILL.md:

  • At sprint start: 30 minutes
  • At sprint four: 3 sprints

Early adoption ensures that all subsequent development occurs within a well-defined, testable structure, and that quality gates are present from day one.

Important Notes

  • Prerequisite: Ensure the game engine is configured in .claude/docs/technical-preferences.md. If not, run /setup-engine first.
  • Idempotency: The skill checks for existing directories and CI workflows to avoid overwriting or duplicating infrastructure.
  • Engine Awareness: The generated test runner and workflow are tailored to your engine. If your engine is not yet supported, additional manual setup may be required.
  • One-Time Setup: Do not rerun the skill unless resetting the test infrastructure is desired.
  • Integration with CI/CD: The GitHub Actions workflow is created to automatically run tests on every push, enabling continuous quality checks.

By embedding automated test setup early and leveraging the Test Setup skill, teams gain a reliable, maintainable foundation for quality-driven game development.