automated-smoke-test
SolidRun an automated smoke test using the godot-mcp server. Launches the project, captures debug output, and checks for errors or crashes.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- striderZA
- Repository
- striderZA/OpenCodeGameStudios
- Created
- 2 months ago
- Last Updated
- 3 days ago
- Language
- JavaScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
smoke-check
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
mcp-driver
Runtime debugging and live project inspection via godot-mcp. Use when headless tools cannot diagnose the problem: code compiles but runtime behavior is wrong, tests pass but the game does not work as expected, or you need to inspect live state (node tree, console output, rendering). Escalation trigger: a task has failed 2+ times through the headless path (headless-build, gdunit-driver), or the issue is inherently runtime-only (visual glitches, input not responding, physics behaving unexpectedly at runtime). DO NOT use for: syntax/compile errors (use headless-build), unit test failures (use gdunit-driver), API lookups (use godot-api). Requires: godot-mcp MCP server registered as "godot" (@coding-solo/godot-mcp).
smoke-test
Runs a short, version-bound health check across the most critical user and system paths to decide whether deeper testing or rollout should continue.