What problem does it solve?
Smoke-checks prevent broken builds from reaching manual QA by running automated tests and validating core functionality before hand-off.
Core Features & Use Cases
- Automated test execution by detected engine: Runs the appropriate test runner (e.g., Godot via gdunit4 runner) and summarizes passing/failing results.
- Coverage gap detection for story scope: Scans expected test evidence per story and flags missing coverage as advisory gaps (not immediate FAIL blockers).
- Interactive manual smoke batches: Uses guided questions to verify key gameplay and regression checks (with optional platform-specific batches).
Example: After a sprint implements new features, run smoke-check to confirm the automated suite is green and that core stability, the primary mechanic, and save/load behave correctly before QA starts.
Quick Start
Run the full gate for your sprint by invoking /smoke-check sprint with the appropriate platform flag if you need platform-specific checks.