Smoke Testing vs Sanity Testing vs Regression Testing

Smoke Testing Definition: Smoke testing is a quick check that the basic and critical functions of an application work after a new build or deployment. It answers: “Is the build stable enough for deeper testing?” Key Points Executed immediately after a new build is deployed. Covers core paths only — broad but shallow. If it fails, the build is rejected; no further testing proceeds. Often automated in CI/CD; sometimes run by developers or QA. Analogy Like turning on a new appliance: if you see smoke, you don’t test every feature. Example (E-commerce) App starts and homepage loads. User can log in / sign up. Search returns results. Item can be added to cart. Checkout can be initiated. Smoke vs. Sanity vs. Regression Testing Sanity Testing Purpose: Verify a...