Geeks With Blogs
The Library of Software Testing Pavankumar Pothuraju's weblog

Sanity Testing is 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 crashing systems every 5 minutes, 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. 
 
Sanity Testing - initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort.

 

               - Initial Testing effort that covers System's Major Functionalities.
              
               - It doesn't cover field level validations.
              
               - The purpose of this testing is "To test all the Major Functional flows working or not"
              
Smoke Test is done to see whether the product smokes when it runs. This is done by c
ompiling and linking every file and combining it into executable on a daily basis. This process minimizes integration risks and keeps defects manageable by helping in catching defects in the early stages.

 

           - This a kind of interface testing between modules in project/product. It involves testing of interaction between modules. Ex. Method Calls, Parameter Passing.

 

           - It doesn't cover field level validations and Major business flows.
          
           - the main focus of this testing is "To reduce the risks involved while doing product integration"

Thanks to B.Saravanakumar

Posted on Friday, August 27, 2004 3:25 PM Software Testing | Back to top


Comments on this post: Sanity and Smoke Testing

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Pavankumar Pothuraju | Powered by: GeeksWithBlogs.net