القائمة
Write gdUnit4 test code with type-specific assertions, signal testing, and scene runner support. Use when creating or updating tests for GDScript files.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | gdunit4-test-writer |
| description | Write gdUnit4 test code with type-specific assertions, signal testing, and scene runner support. Use when creating or updating tests for GDScript files. |
| allowed-tools | ["mcp__context7__resolve-library-id","mcp__context7__query-docs","Read","Write","Edit","Glob","Grep"] |
Write gdUnit4 test code for GDScript files with proper assertions and test structure.
/websites/godot-gdunit-labs_github_io_gdunit4) if neededres://tests/ directory with test_*.gd naming (e.g., test_player.gd)extends GdUnitTestSuite
func test_example() -> void:
assert_int(1).is_equal(1)
assert_int(value).is_equal(10)assert_float(value).is_equal_approx(3.14, 0.01)assert_str(text).contains("hello")assert_array(items).has_size(5)assert_object(node).is_not_null()await assert_signal(emitter).is_emitted(emitter.my_signal) (Signal reference preferred; string name also accepted)func test_with_node() -> void:
var node: Node = auto_free(Node.new()) # Auto-freed after test
assert_object(node).is_not_null()
| gdUnit4 | Godot |
|---|---|
| v6.x | 4.5+ |
| v5.x | 4.3 – 4.4.1 |
| v4.4.0+ | 4.2+ |
These references target gdUnit4 v6. Pre-v6 array-style arguments (e.g. contains([1, 2]), is_emitted("sig", [args])) are still accepted for backward compatibility, but prefer the v6 variadic style shown here.
For detailed gdUnit4 documentation:
/websites/godot-gdunit-labs_github_io_gdunit4Format and lint GDScript files using gdscript-formatter. Use after editing GDScript files to ensure code style consistency.
Regenerate Godot caches (class_name registry and .uid files). Use after creating or renaming GDScript files with class_name.
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.
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.
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.
Validate GDScript changes by refreshing Godot cache and checking diagnostics. Use after creating or editing GDScript files.