What is the difference between smoke testing and sanity testing?

Showing Answers 1 - 8 of 8 Answers

kavita13

  • Dec 4th, 2006
 

Win Some books it's given that smoke testing is the sanity testing.But some books have different openion abt this.It's basically depend on the compant how they think on this .For some company..sanity testing maens....the basi testing carriend out for basic security.

  Was this answer useful?  Yes

Hi Friends

I've already asked somany peoples and verified in somany sites also to know

about this diff.  Here i'm trying to give a dif in my way.. Let me know if i'm

wrong.

Smoke Testing : Smoke is scripted, and done when build is comes at very

first time, to verify major functionality is available or not to conduct major

level of testing.

Sanity Testing : Sanity is unscripted, and done after build is again released

with some changes which raised at smoke testing.

Srinivasulu.B (srinivasulub1981@gmail.com)

  Was this answer useful?  Yes

supriya

  • Dec 27th, 2006
 

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/superficial /brief 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.

 

 

  Was this answer useful?  Yes

saritha

  • Jan 4th, 2007
 

Smoke testing :

Is nothing but ....before going to start testing the application.we dp this type of testing..and this is called basic type of tesing.

Sanity testing is nothing but.....

before going to release the build...we do testing..whether that build is correctt or not .this is called sanity testing.

  Was this answer useful?  Yes

Ikramuddin

  • Jan 17th, 2007
 

Smoke Testing:-

        Checking the proper build has been installed or not, is smoke tsting....tested by POC( Point of Contact) one of senior member of testing team.

Sanity Testing:-

        Checking the readyness of the application by testing its basic functionality....

     eg: in Flight Reservation appln of WR, insert order is the basic funtionality....

  Was this answer useful?  Yes

Murali

  • Feb 5th, 2007
 

Hi CAn you please explain the major difference between these two REGRESSION TESTING & FUNCTIONAL TESTING,RegardsMurali

  Was this answer useful?  Yes

nirmmal

  • Feb 11th, 2007
 

A smoke test is a series of test cases that are run prior to commencing with full-scale testing of an application. The idea is to test the high-level features of the application to ensure that the essential features work. If they do not work, there is no need to continue testing details of the application, so the testing team will refuse to do any additional testing until all smoke test cases pass. This puts pressure on the development team to ensure that the testing team does not waste valuable testing time with code that is not ready to be tested.Once smoke tests are implemented as part of your software development life cycle, you will see the overall quality of the product improve and the sensitivity to producing high quality software increased.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions