sudjoshi

 Profile Answers by sudjoshi 

• May 19th, 2006

 

Difference Between Smoke Testing and Sanity Testing

There are two types of test types, Smoke and Sanity.  What they are exactly? Here we go.....
The general definition (related to Hardware) of Smoke Testing is: Smoke testing is a safe harmless procedure of blowing smoke into parts of the sewer and drain lines to detect sources of unwanted leaks and sources of sewer odors.
It is related to s/w, the definition is Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details.
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.
Smoke Testing and Sanity Testing In greater details...
 
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, 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.

Difference between Smoke Testing and Sanity Testing:

?                  Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke.  In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested. A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.

?                  A smoke test is scripted--either using a written set of tests or an automated test. A sanity test is usually unscripted.

?                  A Smoke test is designed to touch every part of the application in a cursory way. It's is shallow and wide. A Sanity test is used to determine a small section of the application is still working after a minor change.

?                  Smoke testing will be conducted to ensure whether the most crucial functions of a program work, but not bothering with finer details. (Such as build verification). 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.

?                  Smoke testing is normal health check up to a build of an application before taking it to testing in depth. Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

 

jayakumar

• Jun 6th, 2006

 

Sanity testing- It is done to check the each and every part of the application before going into indepth first.It is performed by developers before putting a file into a testing enviroment.Smoke testing: it is done by testers to check the functionality of the application or build system before going into the indepth testing.

vinoth

• Jun 27th, 2006

 

Sanity Testing - typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is often crashing systems, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.

 

 

 

Smoke test describes an initial set of tests that determine if a new version of application performs well enough for further testing

Manohar

• Jul 20th, 2006

 

Smoke test- This is also called as Build verification test mainly used to verify the stability of the application.This is Mandatory test process in progression testing.

Sanity Testing-its a type of regression testing where testing will b conducted on specific functionality when ever there is less time for regression.

This is The Exact Answer!!!!

sudhakar2068

 Profile 

• Sep 11th, 2006

 

Smoke testing:It  is small shackup in sanity testing.During this smoke test, test engineers reject build with reason when that build is not working.smoke testing is optional.

sanity testing:It conducted intial check up on that build by tester after receiving initial build from development team.It is also called as tester acceptance testing or build verfication testing. sanity is manditory.

 sudhakar kolla

If you are having any doubt can ask me.

My Email:Kollasudhakar2005@yahoo.co.in

My number :09819859346

 

testing.siva

 Profile Answers by testing.siva 

• Jun 17th, 2008

 

hi,
    It a test which checks the application is ready for further major test..
     means all the mojor doc are tested here and its working properly according to the 
     expected level.

amresh08

 Profile Answers by amresh08 

• Jun 24th, 2008

 

hi testing.siva,
Your ans is a defination, its not exact ans of  the asked question.