sandeep kumar

• Jun 2nd, 2014

 

When one test the applications all functionality before releasing the build then the testing will be said SMOKING TESTING and usually done by white box test engineer or developers. While after releasing the build whatever the testing engineer test in the application that is called as SANITY TESTING.

keerthi

• Feb 2nd, 2016

 

Smoke testing is Build acceptance testing, mostly followed in daily build process (scrum model). Testing team also might does the smoke testing to make sure whether to accept the new build and can further proceed with testing in that build. Sanity testing is verifying the basic functionalities of the application to make sure we can further proceed with testing in that application. Suppose one of the module is not working but still we can continue testing in the other areas.

Amitkumar

• Nov 17th, 2016

 

Smoke Testing: This is process of verification done by development when they developed & check in certain feature & merge it application. This can be white box/black box.

Sanity Testing: This is process of verification done by test on receiving new build to ensure build is reliable enough to proceed with complete testing.

Ash

• Jul 6th, 2017

 

Smoke Testing: After the build is deployed to the system , the initial level of testing performed is smoke, This will include the basic testing like the URl is accessible, User is able to login, All the links are clickable not touching the functionality.
Sanity:Kind of regression testing checking for a particular module or a functionality.

srinivas

• Sep 15th, 2017

 

Smoke Testing: Software Testing done to ensure that whether the build can be accepted for through software testing or not. Basically, it is done to check the stability of the build received for software testing.
Sanity testing: After receiving a build with minor changes in the code or functionality, a subset of regression test cases are executed that to check whether it rectified the software bugs or issues and no other software bug is introduced by the changes. Sometimes, when multiple cycles of regression testing are executed, sanity testing of the software can be done at later cycles after through regression test cycles. If we are moving a build from staging / testing server to production server, sanity testing of the software application can be done to check that whether the build is sane enough to move to further at production server or not.