Smoke tests are a minimal, fast-running subset of tests that verify an application is stable enough to proceed with deeper testing. They run immediately after deployment to confirm that critical endpoints are reachable, core functionality is operational, and no catastrophic failures are present. Unlike regression suites that can take minutes or hours to complete, smoke tests finish in seconds and provide an immediate go/no-go signal before any further testing begins. In deployment pipelines, smoke tests serve as the first gate: if smoke tests fail, the deployment is rolled back before investing time in comprehensive regression testing.

The tool generates smoke tests targeting the critical paths of a REST API from an OpenAPI specification. Required inputs are the base URL of the deployed service, the target endpoints to validate in the smoke check, and the authentication method. The generator produces a deterministic smoke test suite that confirms each critical endpoint returns an expected status code and valid response schema. Generated tests are minimal by design: they validate that the service is alive and responding correctly, not that every edge case is handled correctly. The focus is speed and reliability. A complete smoke test suite for a typical microservice with ten critical endpoints executes in under fifteen seconds.

Smoke tests deliver maximum value when they run automatically on every deployment. The standard pattern: deployment completes, smoke tests run against the newly deployed environment, pass or fail result gates further testing and promotion to the next stage. If smoke tests pass, the pipeline proceeds to regression testing. If smoke tests fail, the deployment is rolled back immediately without wasting time on comprehensive testing. Because Skyramp generates smoke tests deterministically from the API spec, the smoke suite stays synchronized with the API automatically when the spec is changed and tests are updated. There is no manual maintenance burden as endpoints are added or modified. Regenerating tests produces identical output for unchanged endpoints and updated tests for modified endpoints.

Developers often search for the distinction between smoke and regression testing. Smoke tests are fast, minimal, and deployment-gating. They validate that the service deployed successfully and core functionality is operational. Regression tests are comprehensive, slower, and run to confirm that existing functionality has not broken after a change. Both are necessary in a complete testing strategy. Smoke tests run first to confirm the deployment succeeded and the service is stable. Regression tests run after the smoke check passes to confirm no existing behavior was broken by the deployment. Skyramp generates both types from the same platform with the same deterministic approach, enabling teams to build complete test coverage from specifications.