Smoke Testing

SMOKE TESTING  

• When ever new build is deployed, the basic functions are tested.
• Testing the basic functionality of the application before proceeding with the formal testing.This is called smoke testing.
• After new build is ready,the developers do some kind of smoke testing and then the build is given to test engineers.
• Test engineers will also do smoke testing.
• Smoke testing is done by developers before the build is released to the testers, or by testers accepting a build for further testing.
• It is also called sanity test or build verification test.
• While doing acceptance testing also smoke  testing should be performed because just to ensure that all features are working properly and to ensure that installation has happened properly.
•  When the product is moved to production they will also do smoke testing.
• Developers also do smoke testing but it is optional.when  there are many critical bugs,sending that feature repeatedly for test engineers will lead to stop testing.This will be a shame to developers so after coding and white box testing they will do smoke testing.
• It is non-Exhaustive testing.
  
  Exhaustive : Testing the same thing in different ways

  Why we do smoke testing?

1.   To ensure that the product is testable.
2.   Do smoke testing in early stage,catch the bugs ,send it to the development team.so  that development  will have sufficient time to fix it.
3.  To ensure that installation happened properly.

 Different types of smoke testing

1)Formal smoke testing
  Here Build come to testing team,Test engineer will send report to Test lead.Test lead will consolidate the report and send to development lead.Here Both testing and development team will communicate.

2)Informal smoke testing
 Here Test engineer will do smoke testing,but they will not send any report to Test lead and Test lead will also not send the report to development lead.But testing will be performed.There will be no communication between Testing and development team regarding smoke testing.