← Back to Home

Smoke Testing

Smoke Testing is a quick, shallow level of testing performed on a new build to verify that the critical and most important functionalities work, ensuring the build is stable enough for detailed testing.

Smoke testing answers: “Is the build testable?”

1. Definition

Smoke Testing is a quick, shallow level of testing performed on a new build to verify that the critical and most important functionalities work, ensuring the build is stable enough for detailed testing.

Smoke testing answers: “Is the build testable?”

2. Purpose of Smoke Testing

  • Verify build stability
  • Identify major failures early
  • Avoid wasting time on unstable builds
  • Decide whether to accept or reject a build

3. When Smoke Testing Is Performed

  • After a new build deployment
  • Before starting detailed functional testing
  • After major code changes

4. Who Performs Smoke Testing

  • Manual testers
  • Sometimes developers (basic checks)

5. Scope of Smoke Testing

Smoke testing covers:

  • Application launch
  • Login functionality
  • Core navigation
  • Critical business flows

It does not cover:

  • Deep functionality
  • Edge cases
  • Detailed validations

6. Smoke Testing vs Sanity Testing

Aspect Smoke Testing Sanity Testing
Purpose Build stability Feature stability
Depth Shallow Narrow but deep
When New build After minor changes
Documentation Minimal Minimal

7. Real-Time Example

For an e-commerce site, smoke testing includes:

  • Application opens
  • User can log in
  • Product list loads
  • Add to cart works

If any fail → build rejected.

8. Entry & Exit Criteria (Smoke Testing)

Entry Criteria

  • New build available
  • Build deployed successfully

Exit Criteria

  • Critical features pass
  • Build accepted or rejected decision

9. Common Defects Found

  • Application crash on launch
  • Login failure
  • Broken navigation
  • Configuration issues

10. Common Mistakes

  • Treating smoke testing as full regression
  • Including too many test cases
  • Skipping smoke testing under pressure

11. Interview-Ready Answers

Short answer:

Smoke testing is a quick test performed on a new build to verify basic functionality and build stability.

Detailed answer:

Smoke testing ensures that the critical features of an application work correctly so that the build can be accepted for further testing.

12. Key Takeaway

Smoke Testing protects the testing effort by filtering out unstable builds early.