一键在 Manus 中运行任何 Skill

gdunit4-test-runner

星标11

分支0

更新时间2026年7月12日 10:45

Run gdUnit4 tests for Godot projects and report results (read-only). Use to verify test status after code changes. USE PROACTIVELY to check test results.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

minami110

minami110/claude-godot-tools

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

GDScript Test

Run GDUnit4 tests using the gdunit4-test-runner binary.

CRITICAL: Read-Only Operation

This is a read-only operation.
Run the binary and report results. DO NOT edit files or attempt to fix failing tests.
If tests fail, report file path, line number, assertion details — then STOP.
NEVER use addons/gdUnit4/runtest.sh or direct godot commands.

When to Use

After implementing new features
After modifying GDScript files
When you need to verify test coverage
When running CI/CD validation locally

Setup

The binary is installed automatically on first use (via a skill hook). To install manually:

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/scripts/install.sh

Test Execution

Run tests using the binary directly.

Run All Tests

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner

Scans entire project for tests.

Run Specific Test File

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner tests/test_foo.gd

Run Multiple Tests

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner tests/test_foo.gd tests/test_bar.gd

Run Tests in Directory

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner tests/application/

Verbose Mode

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner --verbose

Shows all Godot logs (useful for debugging test issues).

Custom Godot Path

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner --godot-path /path/to/godot

Understanding Results

The binary outputs test results in JSON format for easy parsing.

Success

{
  "summary": {
    "total": 186,
    "passed": 186,
    "failed": 0,
    "crashed": false,
    "status": "passed"
  },
  "failures": []
}

Failure

{
  "summary": {
    "total": 10,
    "passed": 8,
    "failed": 2,
    "crashed": false,
    "status": "failed"
  },
  "failures": [
    {
      "class": "TestClassName",
      "method": "test_method_name",
      "file": "res://tests/test_file.gd",
      "line": 42,
      "expected": "expected_value",
      "actual": "actual_value",
      "message": "FAILED: res://tests/test_file.gd:42"
    }
  ]
}

Crash

{
  "summary": {
    "total": 5,
    "passed": 3,
    "failed": 0,
    "crashed": true,
    "status": "crashed"
  },
  "crash_details": null,
  "failures": []
}

Godot crashed during test execution. Only tests completed before crash are reported.

Exit Codes

0: All tests passed
1: Some tests failed
2: Crash or error (e.g., Godot crashed, report file not found)

Notes

Binary automatically changes to project root before running tests
Test reports are saved in reports/ directory
Uses gdUnit4 framework (configured in project.godot)
Compatible with CI/CD environments
Binary handles Godot existence check and error handling internally

同仓库更多 Skills

同仓库

gdscript-format

minami110/claude-godot-tools

Format and lint GDScript files using gdscript-formatter. Use after editing GDScript files to ensure code style consistency.

2026-07-2511

gdunit4-test-writer

minami110/claude-godot-tools

Write gdUnit4 test code with type-specific assertions, signal testing, and scene runner support. Use when creating or updating tests for GDScript files.

2026-07-2011

godot-cache-refresh

minami110/claude-godot-tools

Regenerate Godot caches (class_name registry and .uid files). Use after creating or renaming GDScript files with class_name.

2026-07-2011

godot-resource-resave

minami110/claude-godot-tools

Re-save Godot text resources (.tscn/.tres) through the editor pipeline to inject UIDs and validate that they load. Use after creating or editing .tscn/.tres files by hand.

2026-07-2011

open-godot-editor

minami110/claude-godot-tools

Launch the Godot editor GUI in the background so its stdout (print / push_warning / push_error) is directly readable. Use when the user explicitly asks to open the Godot editor, or when a change needs hands-on verification in the running editor/game.

2026-07-0411

gdscript-diagnostics

minami110/claude-godot-tools

Validate GDScript changes by refreshing Godot cache and checking diagnostics. Use after creating or editing GDScript files.

2026-04-2811

name	gdunit4-test-runner
description	Run gdUnit4 tests for Godot projects and report results (read-only). Use to verify test status after code changes. USE PROACTIVELY to check test results.
allowed-tools	["Bash"]
hooks	{"PreToolUse":[{"matcher":"Bash","hooks":[{"type":"command","command":"${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/scripts/ensure-binary.sh","once":true}]}]}

GDScript Test

Run GDUnit4 tests using the gdunit4-test-runner binary.

CRITICAL: Read-Only Operation

This is a read-only operation.
Run the binary and report results. DO NOT edit files or attempt to fix failing tests.
If tests fail, report file path, line number, assertion details — then STOP.
NEVER use addons/gdUnit4/runtest.sh or direct godot commands.

When to Use

After implementing new features
After modifying GDScript files
When you need to verify test coverage
When running CI/CD validation locally

Setup

The binary is installed automatically on first use (via a skill hook). To install manually:

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/scripts/install.sh

Test Execution

Run tests using the binary directly.

Run All Tests

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner

Scans entire project for tests.

Run Specific Test File

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner tests/test_foo.gd

Run Multiple Tests

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner tests/test_foo.gd tests/test_bar.gd

Run Tests in Directory

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner tests/application/

Verbose Mode

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner --verbose

Shows all Godot logs (useful for debugging test issues).

Custom Godot Path

${CLAUDE_PLUGIN_ROOT}/skills/gdunit4-test-runner/bin/gdunit4-test-runner --godot-path /path/to/godot

Understanding Results

The binary outputs test results in JSON format for easy parsing.

Success

{
  "summary": {
    "total": 186,
    "passed": 186,
    "failed": 0,
    "crashed": false,
    "status": "passed"
  },
  "failures": []
}

Failure

{
  "summary": {
    "total": 10,
    "passed": 8,
    "failed": 2,
    "crashed": false,
    "status": "failed"
  },
  "failures": [
    {
      "class": "TestClassName",
      "method": "test_method_name",
      "file": "res://tests/test_file.gd",
      "line": 42,
      "expected": "expected_value",
      "actual": "actual_value",
      "message": "FAILED: res://tests/test_file.gd:42"
    }
  ]
}

Crash

{
  "summary": {
    "total": 5,
    "passed": 3,
    "failed": 0,
    "crashed": true,
    "status": "crashed"
  },
  "crash_details": null,
  "failures": []
}

Godot crashed during test execution. Only tests completed before crash are reported.

Exit Codes

0: All tests passed
1: Some tests failed
2: Crash or error (e.g., Godot crashed, report file not found)

Notes

Binary automatically changes to project root before running tests
Test reports are saved in reports/ directory
Uses gdUnit4 framework (configured in project.godot)
Compatible with CI/CD environments
Binary handles Godot existence check and error handling internally