godot-testing-patterns
Expert blueprint for testing patterns using GUT (Godot Unit Test), integration tests, mock/stub patterns, async testing, and validation techniques. Covers assert patterns, signal testing, and CI/CD integration. Use when implementing tests OR validating game logic. Keywords GUT, unit test, integration test, assert, mock, stub, GutTest, watch_signals, TDD.
What this skill does
# Testing Patterns
GUT framework, assertion patterns, mocking, and async testing define automated validation.
## Available Scripts
### [basic_unit_test.gd](scripts/basic_unit_test.gd)
Minimal GdUnit4 test structure for verifying simple logic and arithmetic.
### [signal_emission_test.gd](scripts/signal_emission_test.gd)
Expert pattern for monitoring and verifying signal emissions in decoupled architectures.
### [mock_dependency_test.gd](scripts/mock_dependency_test.gd)
Using Mocks and Doubles to isolate test subjects from external services or databases.
### [scene_integration_test.gd](scripts/scene_integration_test.gd)
Full scene lifecycle testing, verifying node interactions after instantiation.
### [performance_benchmark_runner.gd](scripts/performance_benchmark_runner.gd)
High-precision execution time measurement using microsecond-scale timers.
### [memory_leak_detector.gd](scripts/memory_leak_detector.gd)
Automated orphan node detection to catch memory leaks during long-running tests.
### [parameter_fuzz_tester.gd](scripts/parameter_fuzz_tester.gd)
Stress testing systems with randomized data ranges to catch edge-case crashes.
### [wait_for_frame_test.gd](scripts/wait_for_frame_test.gd)
Advanced async testing for logic that spans multiple frames or game ticks.
### [physics_collision_test.gd](scripts/physics_collision_test.gd)
Automated verification of physics layer interactions and collision resolution.
### [test_data_factory.gd](scripts/test_data_factory.gd)
Centralized data generation patterns for clean, schemas-compliant test objects.
## NEVER Do in Testing
- **NEVER test implementation details** — `assert_eq(player._internal_state, 5)`? Private variables = brittle tests. Test PUBLIC behavior, not internals [20].
- **NEVER share state between tests** — Test 1 modifies global variable, test 2 assumes clean state? Flaky tests. Use `before_each()` for fresh setup [21].
- **NEVER use sleep() for timing** — `await get_tree().create_timer(1.0).timeout` in tests? Slow + unreliable. Use GUT's `wait_seconds()` OR manual frame stepping [22].
- **NEVER skip cleanup in after_each()** — Test spawns 100 nodes, doesn't free? Memory leak + slow test suite. ALWAYS free nodes in `after_each()` [23].
- **NEVER test randomness without seeding** — `randi()` in test = non-deterministic failure. Use `seed(12345)` for repeatable tests [24].
- **NEVER forget to watch signals** — `assert_signal_emitted(obj, "died")` without `watch_signals`? Fails silently. MUST call `watch_signals(obj)` first [25].
- **NEVER perform tests without an explicit "Definition of Done"** — Vague tests like `assert_true(true)` provide zero value. Every test should verify a specific requirement.
- **NEVER rely on editor-only features for CI/CD tests** — Headless environments lack Viewports. Ensure tests are `headless`-compatible.
- **NEVER ignore the cost of "Integration Tests"** — Testing a whole level is slow. Favor narrow Unit Tests for logic and small Scene Tests for interaction.
- **NEVER hardcode file paths in tests** — Use `Path` constants or project-relative strings. If a resource directory moves, your suite shouldn't break.
- **NEVER test third-party plugins** — Trust the library; test YOUR integration of it.
---
### Installation
1. Download from AssetLib: "GUT - Godot Unit Test"
2. Enable in Project Settings → Plugins
3. Create `res://test/` directory
### Basic Test
```gdscript
# test/test_player.gd
extends GutTest
var player: CharacterBody2D
func before_each() -> void:
player = preload("res://entities/player/player.tscn").instantiate()
add_child(player)
func after_each() -> void:
player.queue_free()
func test_initial_health() -> void:
assert_eq(player.health, 100, "Player should start with 100 health")
func test_take_damage() -> void:
player.take_damage(25)
assert_eq(player.health, 75, "Health should be 75 after 25 damage")
func test_cannot_have_negative_health() -> void:
player.take_damage(200)
assert_gte(player.health, 0, "Health should not go below 0")
```
### Running Tests
```gdscript
# Via GUT panel in editor
# Or command line:
# godot --headless -s addons/gut/gut_cmdln.gd
```
## Assertion Patterns
```gdscript
# Equality
assert_eq(actual, expected, "message")
assert_ne(actual, not_expected, "message")
# Comparison
assert_gt(value, min_value, "should be greater")
assert_lt(value, max_value, "should be less")
assert_gte(value, min_value, "should be >= min")
assert_lte(value, max_value, "should be <= max")
# Boolean
assert_true(condition, "should be true")
assert_false(condition, "should be false")
# Null
assert_not_null(object, "should exist")
assert_null(object, "should be null")
# Arrays
assert_has(array, element, "should contain element")
assert_does_not_have(array, element, "should not contain")
# Signals
watch_signals(object)
assert_signal_emitted(object, "signal_name")
```
## Testing Signals
```gdscript
func test_death_signal() -> void:
watch_signals(player)
player.take_damage(100)
assert_signal_emitted(player, "died")
assert_signal_emitted_with_parameters(player, "died", [player])
```
## Testing Async
```gdscript
func test_delayed_action() -> void:
player.start_ability()
# Wait for timer
await wait_seconds(1.0)
assert_true(player.ability_active, "Ability should be active after delay")
```
## Mock/Stub Patterns
```gdscript
# Double (mock) pattern
func test_with_mock() -> void:
var mock_enemy := double(Enemy).new()
stub(mock_enemy, "get_damage").to_return(50)
player.collide_with(mock_enemy)
assert_eq(player.health, 50, "Should take mocked damage")
```
## Integration Testing
```gdscript
# test/test_combat_system.gd
extends GutTest
func test_player_kills_enemy() -> void:
var level := preload("res://levels/test_arena.tscn").instantiate()
add_child(level)
var player := level.get_node("Player")
var enemy := level.get_node("Enemy")
# Simulate combat
for i in range(5):
player.attack(enemy)
await wait_frames(1)
assert_true(enemy.is_dead, "Enemy should be dead")
assert_gt(player.score, 0, "Player should have score")
level.queue_free()
```
## Manual Testing Checklist
```markdown
## Gameplay
- [ ] Player can move in all directions
- [ ] Jump height feels right
- [ ] Enemies respond to player
- [ ] Damage numbers are correct
## UI
- [ ] All buttons work
- [ ] Text is readable
- [ ] Responsive on different resolutions
## Audio
- [ ] Music plays
- [ ] SFX trigger correctly
- [ ] Volume levels balanced
## Performance
- [ ] Maintains 60 FPS
- [ ] No stuttering
- [ ] Memory stable
```
## Validation Helpers
```gdscript
# validation.gd (for runtime checks)
class_name Validation
static func assert_valid_health(health: int) -> void:
assert(health >= 0 and health <= 100, "Invalid health: %d" % health)
static func assert_valid_position(pos: Vector2, bounds: Rect2) -> void:
assert(bounds.has_point(pos), "Position out of bounds: %s" % pos)
```
## Test Organization
```
test/
├── unit/
│ ├── test_player.gd
│ ├── test_enemy.gd
│ └── test_inventory.gd
├── integration/
│ ├── test_combat.gd
│ └── test_save_load.gd
└── fixtures/
├── test_level.tscn
└── mock_data.tres
```
## Best Practices
### 1. Test Edge Cases
```gdscript
func test_edge_cases() -> void:
player.take_damage(0) # Zero damage
assert_eq(player.health, 100)
player.take_damage(-10) # Negative (heal?)
assert_eq(player.health, 100) # Should not change
```
### 2. Isolate Tests
```gdscript
# Each test should be independent
func before_each() -> void:
# Fresh setup for each test
player = create_fresh_player()
```
### 3. Test Critical Paths First
```
Priority:
1. Core gameplay (movement, combat)
2. Save/load system
3. Level transitions
4. UI interactions
```
## Expert Testing Patterns
### 1. State-Snapshot-Testing (Data Regression)
Verifying that complex Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.