Topic: Smoke Testing vs Sanity Testing

Smoke Testing (Build Verification Testing)
  • A high-level test to check if the critical functionalities of the application work.
  • Done on every new build release before deeper testing.
  • Ensures the build is stable enough for further testing.
  • Example: Can you log in? Can you open the dashboard?
Sanity Testing
  • A narrow and focused test done after receiving a bug fix or minor change.
  • Verifies that the reported issue is fixed and related features still work.
  • Example: If a login bug is fixed → test login and related sessions.
Key Differences
High-level comparison of smoke testing versus sanity testing
Feature Smoke Testing Sanity Testing
Scope Broad, shallow Narrow, deep
Purpose Check build stability Check bug fix/change impact
When done After every build After fixes/minor updates
Automation Often automated Often manual
Example Check login, homepage load Re-check login after bug fix