Automation Hangout

If debugging is the process of removing bugs, then programming must be the process of putting them in. ~Author Unknown "Quality is free, but only to those who are willing to pay heavily for it." (Lister, DeMarco: "Peopleware") "The only person who likes change is a wet baby." (Carr, Hard, Trahant: "Change Process") "A day lost at the beginning of a project hurts just as much as a day lost at the end. ... There are infinitely many ways to loose a day ..but not even one way to get one back." (DeMarco, "The Deadline") “Before software can be reusable it first has to be usable.” – Ralph Johnson. “If you don’t care about quality, you can meet any other requirement” – Gerald M. Weinberg “Irreproducible bugs become highly reproducible right after delivery to the customer”, Michael Stahl’s derivative of Murphy’s Law

Article info : Wideband Delphi Estimation Technique

There are a couple of important items that we should keep in mind when we communicate the status of the daily test execution to the higher or middle management. The important items would be the following a) Status of test case execution: This can include the total number of test cases planned, executed, passed, failed, blocked and not executed. b) Defect status This can include total number of defects reported vs. the severity. Also the information on Open Sev 1 and Sev 2 defects would be a subject of interest as most of the projects the Sev 1 and 2 defects get fixed where as the Sev 3 and 4 would be open. c) Also mention about the risk and issues that the team is facing during test execution and the plans to mitigate the risks. d)  The status report also should state whether the current rate of test execution is enough to achieve the planned end dates. If no it will be good to mention the plans that are in place to increase the execution rate.