smoke-check

Automated smoke testing prevents broken builds from reaching QA by running an automated test gate and producing a clear PASS/FAIL verdict. It validates engine-specific test setup and executes batched stability checks before sprint hand-off.

A smoke test gate is an automated verification process needed during sprint hand-offs to validate build stability. It exercises coverage expectations, runs regression checks, and ensures critical paths are verified before releasing the build to QA.

Run automated smoke tests with platform variants by passing the desired platform argument during execution. This triggers engine-aware test detection and includes optional platform-specific checks within the interactive verification batches.

The smoke testing process supports manual critical-path verification through interactive batching. It guides users through core stability, sprint regression, and optional data integrity checks, requiring interactive batch confirmation before generating the final report.

Quick mode regression checks execute without auto-writing results by parsing runner output and generating gated reports interactively. The system requires explicit batch confirmation and relies on argument handling to differentiate between sprint and quick execution modes.

Automated test coverage scanning cannot execute manual evidence directly; it only flags missing or manual-test evidence needs. It evaluates story coverage expectations but requires interactive human verification to confirm the stability of manual critical paths.