How to do Smoke Testing on Softwares

Smoke Testing

• Testing the basic and critical features of the application or website before doing throw testing.
• In this type of testing, tester checks the stability of the product or software, during the functionality of the software tester found any of the crashes or blocker.
• Smoke testing is done manually, without the use of automation tools and scripts.

For example:- Just for the half day check the functionality on features of the application or website, if in case of any feature blocker is found send the bug report to developer. Afterward do the testing on other features, when the bug is revolved, again do the smoke testing of same feature to found the blocker or crashes.

• Difference between Smoke and Sanity Testing.

1. Smoke Testing:-                                                                      2.   Sanity Testing:-                                        
   • It is wide and shallow testing.                                                 It is deep and narrow testing.
   • It is scripted.                                                                            It is not scripted. 
   • Check the basic and critical features.                                     Check bug fixex and changes are working or not.

• Why do smoke testing?

1. To check whether the product or software is testable or not.
2. When the tester open the application and getting lots of bugs because of which you are not be able to test, hence the product or software is not testable.
3. If tester perform smoke testing the developer will get enough time to fix the bugs before you perform throw testing.
4. While performing smoke testing we should check it with negative values.
5. Smoke testing is done to verify build is working or not also known as built verification testing.
6. It is a kind of health checkup of a product or software.

• When to perform smoke testing?

1. Developer itself do the smoke testing of the product or software.
2. Even the acceptance test engineer do the smoke testing of the product or software.
3. RE and BE also do the smoke testing of the product or software.