Smoke Testing & Sanity testing

 

SMOKE TESTING

 Definition

Smoke Testing is a preliminary level of testing performed to verify that the basic and critical functionalities of the application are working after a new build is received.

 It checks whether the build is stable enough for further testing.


 Why Smoke Testing is done

  • To check basic features quickly

  • To confirm build is stable

  • To avoid wasting time on broken builds

  • To ensure major modules are working


 When Smoke Testing is done

✔️ After every new build release
✔️ Before detailed functional testing
✔️ During early testing phase


How Smoke Testing is performed

  1. Install the new build

  2. Run basic test cases

  3. Check main features (login, navigation, major modules)

  4. If pass → proceed to detailed testing

  5. If fail → reject build


 Where Smoke Testing is used

  • Software testing projects

  • Web applications

  • Mobile apps

  • Enterprise systems


 Example of Smoke Testing

Suppose you have an E-commerce Website

Basic tests:

  • Open website

  • Login works?

  • Add product to cart?

  • Checkout page opens?

If these basic features work → Build is accepted 


SANITY TESTING

 Definition

Sanity Testing is a focused testing performed to verify that specific bug fixes or new changes are working correctly without checking the entire application.

 It checks only the modified functionality.


 Why Sanity Testing is done

  • To verify bug fixes

  • To check small changes

  • To ensure new updates didn’t break functionality


 When Sanity Testing is done

✔️ After bug fixing
✔️ After minor code changes
✔️ During regression testing phase


 How Sanity Testing is performed

  1. Identify changed modules

  2. Test only those functionalities

  3. Verify bug is fixed

  4. Ensure related features work correctly


 Where Sanity Testing is used

  • After patch update

  • After small feature addition

  • After fixing reported defects

Example of Sanity Testing

Bug reported: “Login button not working”

After fix, tester checks:

  • Login button works?

  • Password validation correct?

  • Login redirects properly?

No need to test whole website 


 Difference Between Smoke & Sanity Testing

BasisSmoke TestingSanity Testing
DefinitionChecks basic functionalityChecks specific bug fixes
ScopeWide (entire build basics)Narrow (specific module)
WhenAfter new buildAfter bug fix/change
PurposeVerify build stabilityVerify correctness of changes
DepthShallow & broadDeep & focused
ExampleCheck login, homepage, cartCheck fixed login bug only

🎯 Easy Memory Trick for Exams

  • Smoke = “Build Acceptable?”

  • Sanity = “Bug Fixed Correctly?”


 Final 2-Line Conclusion

Smoke Testing ensures the build is stable by checking basic functionalities, whereas Sanity Testing verifies that specific bug fixes or changes work correctly without testing the entire application.



Comments

Popular posts from this blog

Software Testing Module 2

Assignment 1

Assignment 3