Generally, a smoke test is scripted (either using a written
set of tests or an automated test), whereas a sanity test is
usually unscripted.

Smoke Test
----------
In software testing, a smoke test is a collection of written
tests that are performed on a system prior to being accepted
for further testing. This is also known as a build
verification test.

Sanity Test
-----------
A classic example of this in programming is the hello world
program. If a person has just set up a computer and a
compiler, a quick sanity test can be performed to see if the
compiler actually works.



correct me if I am wrong....

sanity and smoke both are same but little difference is 
there.there both are known as build acceptence testing .

sanity means that ensures to check the major functionality 
of application when a build release.that means to verify 
the stability of the build.so that can be a build but only 
the intial build.

Smoke means that ensures to check the major functionality 
of application when a new build release.that means to 
verify the stability of the build.so that can be a build 
Accept the intial build.

Both smoke and sanity tests are same. but a little 
difference lies on the apporach.

Sanity tests is to conform the basic functionality works 
fine and build is ready for system test.
Smoke test is the negative test apporach to reject the 
build for system test.

Both are part of build verification test.

SAnity and smoke both are same .there is the slight 
difference.  
Intial build is sanity.
Rest of other build is smoke.
1)sanity checks the major functionality of the application 
when a build occurs.that means to verify the stability of 
the build.that can be a build but only the intial build.
2)smoke checks the major functionality of the application 
when a new build occurs.that means to verify the stability 
of the build.that can be a build except the intial build.

hi,
i think these are diffent. In somke testing we check minmal 
most features of the application.
and in the smoke testing we check minimal most operational 
features of the application.

Sanity and Smoke are same but there is a slight difference 
between them
Sanity testing checks whether the build is testable or not
Smoke testing checks  the  main functionality of the 
application and also checks the stability of the 
application.

smoke testing is performed by tester for build stability
where as sanity is performed by the programmers befor 
deploy in the testing environment

Smoke Test
---------->
Smoke testing is a term used in plumbing, woodwind repair, 
electronics, and computer software development. It refers 
to the first test made after repairs or first assembly to 
provide some assurance that the system under test will not 
catastrophically fail.
Sainty Test
---------->
A sanity test is a basic test to quickly evaluate the 
validity of a claim or calculation.

Smoke Test: Build Verification Test. Once the Build is 
moved from development Enviroment to QA Enviroment, test 
the Major functionalities in a possitive flow to ensure the 
app is elgible for testing and also for any Show stopper 
and/or Block Issues

Sanity Test: Testing is done once all the issues are 
closed, before cerfifying the application one quick test 
will be conducted in a +ve flow and then release the 
certification or beta testing

Smoke testing :- Smoke testing is done when s/w build 
reaches from developer to test engineer,to check wheather 
it can withstand further testing or not,u can say it is a 
testing to check the stability of the build as per the 
customer requirement.

Sanity testing :-this type of testing is done prior to the 
release of build to the market,when almost all aspect of 
testing is covered  & only only cirtification or u can say 
clearence is left 
Smoke Testing  :-Developer -smoke testing--test engineer
Sanity Testing  :_Test engineer--Sanity testing--Quality 
analysis

Smoke Testing
This test is done when the build is just prepared (fresh build) and deployed in the test environments. This is basically an ad hoc test to check roughly to make sure the major functionalities are not broken. It is the preliminary a test carried out by the QA tester. After the smoke test, the testers perform functional testing
Sanity Test: 
Testing is done once all the issues are 
closed, before cerfifying the application one quick test 
will be conducted in a +ve flow and then release the 
certification or beta testing