What is the difference between smoke and sanity testing?

Showing Answers 1 - 5 of 5 Answers

sandy

  • Jun 4th, 2005
 

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.  
 
Smoke Test?, a broad but shallow verification of all the critical functionality

  Was this answer useful?  Yes

ASOKAN

  • Jun 6th, 2005
 

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.

  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