sridhar

• Jan 9th, 2006

 

Smoke testing : Every release to the client should be preceded by smoke test. This is done due to avoid the suden surprise to the client. There is no test cases involved but check list will be maintained.       

Ex : Bad CD Burning,Application Deployment,Launching,Navigation and basic functinality will check.

Sanity Testing : To check whether the software or application is well enough to accept the major testing efort or not.

Ex : Dll file not found

Golden Rule : For every build we have to go for sanity test.

Meanwhile the m/c should be clean. If it is a web application remove the temporary internet files.

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.