xxy

• Oct 19th, 2005

 

There is no differnece betweeen smoke and sanity testing.

sandhya kiran bandaru

• Oct 26th, 2005

 

A quick and dirty test that the major functions of a piece of S/W work.Originated in the H/W testing practice of turning on a new piece of H/W for the first time and considering it a success if it does not catch on fire.Santi testing is the brief test of major functional of a piece of S/W to determine if its basically operational.

suganthi

• Jan 30th, 2006

 

smoke testing is performedto make sure the basic appln functionality is working.whereas sanity testing is to see the appln is not broken ( eg patch testing)

swarna

• Oct 10th, 2006

 

Smoke testing is a DAY BY DAY TESTING.

sanity testing is done after recording or any modifications or chages are done.

nirmmal

 Profile 

• 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.