smoke-check

To run a smoke test gate before QA hand-off, execute a critical-path test command specifying your sprint scope and target platform. The gate validates build readiness by running automated tests, checking story coverage, and emitting a dated PASS/FAIL report.

Smoke testing for sprint readiness validates core stability before QA hand-off by executing automated test runners and verifying story-level test coverage. It prevents broken game engine builds from wasting QA time by producing a clear PASS/FAIL verdict.

Story-level test coverage validation scans your sprint or QA plan to identify covered, manual-evidence, missing, expected, or unknown test statuses. This ensures all completed stories have appropriate test proof before generating the final QA hand-off report.

Yes, you can generate platform-specific PASS/FAIL reports by specifying the target platform in your smoke test command. The tool runs structured manual verification batches for that platform and includes a per-platform verdict in the final dated report.

When an automated test is NOT RUN during the smoke check, it is handled as a warning requiring manual confirmation. The system logs the skipped test status and prompts for structured human verification before finalizing the QA readiness verdict.

No manual test runner configuration is needed. The smoke check automatically detects your game engine setup, selects the correct automated test runner, executes the critical-path tests, and records the pass/fail outcomes directly into the QA report.