gdUnit4 Test Writer

gdUnit4 tests use type-specific assertions to verify GDScript code behavior. Create test files in res://tests/ with test_*.gd naming, then apply assertions like assert_that() and assert_signal() to validate expected outcomes. This Skill provides templates and guidance for structuring these tests correctly.

Yes, gdUnit4 supports signal testing through dedicated assertion methods. This Skill guides you through signal-specific test patterns, helping you verify that signals emit correctly and carry the expected data within your test workflow.

gdUnit4 tests follow a standard structure: place files in res://tests/, use test_*.gd naming, import the gdUnit4 library, and organize assertions with clear, descriptive names. This Skill provides templates that enforce this structure and best practices for readable, maintainable tests.

Scene runner workflows in gdUnit4 let you test scenes in isolation by loading and interacting with them during test execution. This Skill covers scene runner integration patterns, helping you verify scene behavior and node interactions within your test suite.

Yes, you should understand GDScript syntax and the code you're testing. This Skill assumes GDScript familiarity and focuses on applying gdUnit4-specific assertions and test patterns, not teaching the language itself.

After authoring tests with gdUnit4, validate them using gdscript-validate verification, then run the tests through Godot's test runner to confirm they pass. This Skill coordinates test creation with validation and execution workflows.