Smoke Test

A smoke test is a short, shallow set of checks that confirms a freshly deployed build is alive and its most important functions work. It does not try to prove correctness. It answers one question quickly: is it worth continuing, or should we roll back now?

Why it matters

A deploy can pass every unit test and still break production because of a missing environment variable, a failed migration or a misconfigured proxy. A smoke test run against the live environment catches those in seconds, before most users notice, and gives your pipeline an automatic reason to stop a rollout.

The same checks double as ongoing monitoring. A script that runs after each release can be scheduled every few minutes and become a synthetic check.

Example

A post-deploy step in a shell script:

set -e
BASE=https://example.com
curl -fsS -o /dev/null "$BASE/healthz"
curl -fsS "$BASE/" | grep -q "Sign in"
curl -fsS -o /dev/null -w "%{http_code}\n" "$BASE/api/v1/status"

-f makes curl fail on HTTP errors and set -e aborts the script, which fails the pipeline and can trigger an automatic rollback.

Common mistakes

• Checking only that the home page returns 200. A cached or static page can hide a dead database.
• Letting the suite grow into a slow regression test. Keep it under a minute or two.
• Running it against staging only. Environment differences are the usual cause of production breakage.

Related

• Synthetic monitoring
• Rollback
• Canary release
• Health check

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.