engine-tests

Runs headless Godot test suites and reports a compact pass/fail summary.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/rpmcdougall/claude-skills --skill engine-tests-rpmcdougall
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engine-tests
Source: https://github.com/rpmcdougall/claude-skills/tree/main/skills/engine-tests
Command: npx skills add https://github.com/rpmcdougall/claude-skills --skill engine-tests-rpmcdougall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running the turnipsim Godot test suites manually requires remembering the correct headless invocation, the platform-specific Godot binary path, and how to parse verbose output. This Skill standardizes the whole run so you get a compact pass/fail summary every time. ## Core Features & Use Cases - Platform-detected Godot path: Automatically selects the Godot 4.6.2 binary on Windows or macOS, and stops with a clear message if none is found. - Dual suite execution: Runs both tests/test_game_engine.gd and tests/test_runner.gd headlessly and parses their Passed: N / Failed: M lines. - Compact reporting: Outputs a single totals line and lists only FAIL lines, never dumping full logs. - Use Case: After editing engine code on a feature branch, ask to run the tests and immediately see something like "42 engine + 18 types = 60 total, 0 failing" before opening a PR. ## Quick Start Ask the assistant to run the engine test suites from the turnipsim repo root and report the pass/fail summary.

Frequently Asked Questions about engine-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Godot tests headlessly from the command line?▼

Invoke the Godot binary with --headless --path godot -s followed by the test script path, such as tests/test_game_engine.gd. Each suite prints a final Passed: N / Failed: M line that you can parse for results.

How to run GDScript test suites on Windows and macOS?▼

Detect the platform-specific Godot binary first: /c/tools/Godot/Godot_v4.6.2-stable_win64.exe on Windows or /Applications/Godot.app/Contents/MacOS/Godot on macOS. Then run the same headless command from the repo root on either platform.

What if the Godot binary is not found on my machine?▼

The run stops immediately with a clear message that the Godot binary was not found for the platform. It does not attempt to download or install Godot, so you must install Godot 4.6.2 yourself and retry.

Can I use scripts/test-stack.sh to run the turnipsim tests?▼

No. scripts/test-stack.sh launches a manual-play stack with a headless server and windowed clients, which is not a test run. The actual test suites are tests/test_game_engine.gd and tests/test_runner.gd run headlessly.

Why does the test output only show failing lines instead of full logs?▼

The summary is intentionally compact: it reports total counts and greps only FAIL lines when failures exist. This keeps results readable without dumping full logs, while still surfacing exactly which tests failed.