Sanity Testing is the Initiative testing we are conducting
for        STLC cycle where as Smoke testing is conducting
by the developers before releasing the software build to the
testing phase.

Sanity testing is conducted by the Testers where as smoke
testing is conducted by the developers.

Based on the Sanity testing results testers will identify
the received initial build is further testable or not
And based on the Smoke testing developers will identify the
all the functionalities have been covered or not ...

regards
Sm

Smoke Testing :- It is a testing in which we test the major 
area of the application randomly with the motive to find 
out any crashing issue.

Sanity Testing :- it is a testing in which we test the 
application with only +ve data.

Hey guys are u going mad.First thing is that if u dont know
about the thing that please dont put your foot in that as
little knowledge is a very dangerous thing.This is very
simple thing which I m describing briefly:-

Sanity testing :- It is just to test the basic
functionalities of a software product and application.it is
done by testers.

smoke testing :-it is a form of regression testing.when a
application made some new changes to modules or added new
modules to a application then a smoke test is performed that
it is working fine or not.it can be done by both developers
and testers.

I hope this might have clear your doubts.

If anyone of has some queries regarding manual testing and
automation tools and quality assurance u can ask me freely.
my email id is akhil_25683@yahoo.co.in.

Thanks & Regards,
akhil

The Main difference between sanity and smoke testing is that
when very first time a software comes for testing and we
perform very basic testing like checking of navingation or
login etc its sanity testing

smoke testing is that when a software has few bugs and it
got fixed and we are performing the basic testing like login
and naviagtion etc

for more details visit

www.s-qa.bolgspot.com

Smoke testing suit execute where we can verify whether the 
application is stable or not to do functionality 
testing.Here we will test all the pages r displaying or 
not,all the modules are working or not,all the weblinks r 
redirecting to appropriate pages or not etc...

Sanity testing suit excute on final release to verify 
whether application is stable to deliver for client with 
respect to customer requirements.

Sanity Testing: sanity test is a very brief run-through of
the functionality of a computer program, system,
calculation, or other analysis, to assure that the system or
methodology works as expected

Smoke Testing: smoke testing is a preliminary to further
testing, i.e when the release is given to the test team -
need to do smoke testing for each and every link - in order
to verify that the next pages are displayed and the further
testing can be done.

Smoke testing is done by developers before the build is
released to testers.

Sanity testing is done by testers to verify whether to 
accept a build for further testing or not.

In both the same the way of technique used to test is the
same, both are for checking for minimal functionality of the
application only difference is done departments are different.

Smoke testing is basically perform to asure software is 
stable enough to consider it for further testing.It is 
shallow & wide as we navigate through all options of 
application without going into much deep.In this we are 
more concern about major functions without much bothering 
about minor ones.e.g.It is more useful in configuration 
(hardware) testing.

Sanity testing is cursory testing.When new build is 
released from development team with minor changes, in this 
case instead of performing through regression testing 
sanity testing is more appropriate to ascertain indeed 
rectifications are done.It is narrow & deep.It is subset of 
regression testing.

Sanity Testing
    A Test engineer verifies stability of build before 
start testing. This preliminary checking is called sanity 
testing. This is also known as Tester acceptance testing 
(TAT) or Build verification testing (BVT)

Smoke Testing
     It is an extra shake up in sanity testing. In this 
test, testing team reject a build with reason when that 
build is not working.
Eg: Watch is not working due to key rod problem.

Smoke Test: 

When a build is received, a smoke test is run to ascertain 
if the build is stable and it can be considered for further 
testing. 

 

Smoke testing can be done for testing the stability of any 
interim build.

 

Smoke testing can be executed for platform qualification 
tests. 

 

Sanity testing: 

Once a new build is obtained with minor revisions, instead 
of doing a through regression, a sanity is performed so as 
to ascertain the build has indeed rectified the issues and 
no further issue has been introduced by the fixes.  Its 
generally a subset of regression testing and a group of 
test cases are executed that are related with the changes 
made to the app.

 

Generally, when multiple cycles of testing are executed, 
sanity testing may be done during the later cycles after 
through regression cycles.

Take one example To test Word Doc::

In word doc we have different option available like File
Menu,Edit Menu,View Menu,Insert Menu,Tool Menu,Table Menu
etc.......
For Smoke Testing We check whether when we click in file
menu or in insert menu etc we get all options present in
that menu or not i.e Smoke Testing.. 


For Sanity testing After clicking on File menu we check its
sub menu whether or not they r working fine or not i.e
Sanity Testing ...........


with the help of example i think u understand the 2 Testing

smoke testing-Checking the functionality
Sanitary-opposite to smoke testing.checking in depth of
functionality of the process

sanity testing and smoke testing is same.
here  we wil check the basic functionalities of our build.
 we are using +ve data for sanity testing
but in smoke testing we are using -ve data .