Hi

Smoke Testing: Smoke testing is non-exhaustive software testing ascertaining that the most crucial functions of a program work but does not bother with finer details.

Sanity Testing: Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing. It normally includes a set of core tests of basic GUI functionality to demonstrate connectivity to the database application servers printers etc.

Regards

Teena.

Smoke Test is a dirty and quick test done as soon as a build is given to ensure that the system is reliable and does not crash

Sanity test is to test whether the build is sane enough or meets important requirements before we can proceed with a majot testing effort.

smoke testing - To test whether the build is stable or not by doing some testing

Sanity testing - to test whether the build meets the requirements are not

Regards

Raghu

Smoke testing _BVT(Build Verification testing)

Sanity testing _BAT(Build Acceptance testing)

BVT:- 10 to 15 is critical test cases.

BAT:- 85 to 90 of test cases will be BAT.That is non crtitical test cases.

BVT:-Once navigation tests are complete execute the tests that are termed critical. That means a set of test scenarios/cases must be identified as critial priority such that if these tests do not work the product does not get acceptance from the test team. Usually this will be 10 to 15 of the total test cases.

BAT:- The next job is to go thru the rest of the 90 of test cases and the respective test steps one by one and then actually performing the steps on the software roduct.

Smoke Testing - Testing of critical features Done before Testing regours Testing of Application.

Sanity Testing - Testing of Critical Features done Before Regression testing..

Regards

Biswajit pani

Sanity Tersting : Testing Basic Functionality of application.

Smoke Testing: Testing Stability of the Application

smoke te..is testing major functionalites heavily minor functionalities r not tested.it is a nonexhaustive testing.(not done thoroughly).It can b done in any phase of stlc once after the module is ready.

Sanyty testing :it is a cursery or casual testing done in order to check wheather the sy si s ready to test or not ..especially done after a small change iis done .thats why it is called sub regression testing aswell.

smoke testing: it is done to check the initial check up of the build

snanity testing: its is aslo garabage testing. it is done to

check extra functionality of build