smoke test
A quick test that checks the most basic behaviour works after a deploy, before deeper testing or real traffic.
In more detail
It is shallow and fast by design, so it can run right after every deploy. If it fails, there is no point running deeper tests or sending real traffic.
Example
In blue-green the smoke tests hit the green endpoint before the switch.Related terms
- blue-green deployment — Running two complete environments, blue for the current release and green for the candidate, and switching traffic between them in one step.
- unit test — An automated check of one small piece of code, such as a single function, that runs quickly and on its own.
- end-to-end test — A test that drives the whole system from the outside, often through a browser or public API, with every part running.
- integration test — A test that checks several real parts working together, such as the service talking to a real database.
Taught in
- Blue-Green Deployments — Continuous Integration & Continuous Delivery Pipelines
- Deployment Strategies: Blue Green — DevOps & Site Reliability Engineering
- Tying It All Together — Modern Java: Virtual Threads & High-Throughput Services
- Namespaces, Labels And Declarative Manifests — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: describe, Events And A First Smoke Test — Kubernetes: Production-Grade Container Orchestration
- NodePort, LoadBalancer And ExternalName — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: A Timed Service Recovery Drill — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: GitOps Drift And Controller Failures — Kubernetes: Production-Grade Container Orchestration