smoke-test

To generate smoke tests from OpenAPI or Swagger specs, this Skill creates minimal executable test suites by parsing the provided spec data and applying scope-based endpoint selection for safe, high-relevance validation. It outputs test files and a structured manifest for traceability.

The best way to run a quick health check on deployed APIs is generating minimal smoke tests from OpenAPI specs. This approach filters endpoints by scope, such as health checks and read-only routes, ensuring low-risk baseline verification before requesting explicit user execution.

You cannot automatically execute generated API tests against a live service without explicit user confirmation. This Skill enforces safety boundaries by requiring user approval before running tests on deployed services, ensuring safe pre-release checks and baseline health verification.

Smoke testing with this Skill filters out endpoints with path parameters by default during scope-based endpoint selection. It focuses on minimal, low-risk validation like health checks and read-only operations to ensure safe baseline health verification for deployed services.

The test manifest output includes structured results for traceability, retaining records before and after test execution. It documents the generated minimal smoke tests, input contracts, execution policies, and scope-based endpoint selection from your OpenAPI or Swagger spec data.

You should not use minimal smoke tests for complete regression, performance testing, or security testing. This Skill focuses strictly on quick, low-risk post-deployment validation and baseline health verification, avoiding the complexity of comprehensive test suites.