Automation Hangout

An Article on Keyword Driven Test Case Design:- http://www.stickyminds.com/s.asp?F=S14393_ART_2

Introduction I would like to explain how testing on clean PC will help you to overcome the issues that may arise due to presence of additional software or improper settings on the Test PC. Many of the test engineers perform testing on PC that have lot of additional programs installed like messengers, browser toolbars and products that your potential clients or customers may not be using. Also, a test engineer involved in functional testing may install different versions of the AUT during the testing life cycle. Most of the install or uninstall programs prompt the user whether to uninstall a shared file or dll during the uninstall process. However, the fact is that most of the users ignore this message due to lack of knowledge or awareness. Also, the install program written for your software may fail to remove some of the registry entries. I have across situations where the client was unable to use the software due to the absence of some files in his machine during the starting of my ca

What is Test Execution Efficiency? It is generally very difficult to measure the efficiency of the testing process or the testing team for a project. Test Efficiency helps to calculate the efficiency of testing i.e. how many defects were leaked to the customer as compared to number of defects reported by the testing team. Generally almost 10-15 % of defects will be leaked and is considered acceptable. In the recent years, Companies have stared spending huge amount of money for developing quality. Due to this defect leakage percentage has come down to less than 10%. How to Measure? The Excel Sheet Attached helps us to calculate the efficiency of a testing process based on the number of defects reported by Customer and to the number of defects identified by the Testing Team. Steps 1) Provide Ranking to each severity. In the excel sheet the severity rankings have been assigned as a) Critical--4 b) Serious – 3 c) Moderate –2 d) Minor –1 2) Collect the list of def

What is a Smoke Test? Smoke testing is non-exhaustive software testing, to prove that the most crucial functions of a program work, but not bothering the finer details. A smoke test is similar to the basic type of hardware testing, in which the device passed the test if it didn’t catch fire the first time when it was turned on. The term is also used metaphorically, especially in computer programming, where it is also called a "sanity test Most of the software companies follow the “daily build and smoke test” process. Each day every file is compiled, linked, and combined into an executable program and the program has to pass through a “smoke test,” a relatively simple check to see whether the product “smokes” when it runs. After performing a smoke test the tester can come to a conclusion that the software can be accepted or rejected for a major round of testing. Benefits of Smoke Testing Reduces Integration Risks I have encountered many instances in the past where the entire softwa