Test Notes

I don't make software; I make it better
posts - 78 , comments - 60 , trackbacks - 616

November 2003 Entries

Smoke & Sanity Testing
There are two type of test types, Smoke and Sanity. What they are exactly? Here we go..... The general definition (related to Hardware) of Smoke Testing is: Smoke testing is a safe harmless procedure of blowing smoke into parts of the sewer and drain lines to detect sources of unwanted leaks and sources of sewer odors. It it is related to s/w, the definition is Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with ......

Posted On Thursday, November 20, 2003 4:53 AM | Filed Under [ Software Testing CSTE ]

Software QA/Testing - Glossary and Technical FAQs

http://www.robdavispe.com/free2/

It is a great place for Software QA/Testing FAQ.  Great work Rob

Posted On Thursday, November 20, 2003 4:42 AM | Filed Under [ Testing/QA-FAQ ]

How Many Bugs Do Regression Tests Find?
What percentage of bugs are found by rerunning tests? That is, what's the value of this equation:

number of bugs in a release found by re-executing tests
100 X ------------------------------------------------------------------------------- ?
number of bugs found by running all tests (for 1st or Nth time)

Excellent article, click on the title for more.......

Posted On Tuesday, November 4, 2003 4:34 AM | Comments (0) | Filed Under [ Software Testing ]

Metrics for evaluating application system testing
Metric = FormulaTest Coverage = Number of units (KLOC/FP) tested / total size of the systemNumber of tests per unit size = Number of test cases per KLOC/FPAcceptance criteria tested = Acceptance criteria tested / total acceptance criteriaDefects per size = Defects detected / system sizeTest cost (in %) = Cost of testing / total cost *100Cost to locate defect = Cost of testing / the number of defects locatedAchieving Budget = Actual cost of testing / Budgeted cost of testingDefects detected in testing ......

Posted On Tuesday, November 4, 2003 4:31 AM | Filed Under [ Software Testing Quality Metrics ]

Common definitions for testing - A Set of Testing Myths:
“Testing is the process of demonstrating that defects are not present in the application that was developed.” “Testing is the activity or process which shows or demonstrates that a program or system performs all intended functions correctly.” “Testing is the activity of establishing the necessary “confidence” that a program or system does what it is supposed to do, based on the set of requirements that the user has specified.” These myths are still ......

Posted On Tuesday, November 4, 2003 4:29 AM | Comments (5) | Filed Under [ Software Testing ]

Risk Management
Risk avoidance: Risk is avoided by obviating the possibility that the undesirable event will happen. You refuse to commit to meeting milestone M by feature F - don't sign the contract until the software is done. This avoids the risk. As long as you enter into the contract to deliver specific scope by a specific date, the risk that it won't come about exists.Risk reduction: this consists of minimizing the likelihood of the undesirable event. XP reduces the likelihood that you will lack some features ......

Posted On Tuesday, November 4, 2003 1:56 AM | Comments (13) | Filed Under [ Risk Management ]

Three Questions About Each Bug You Find
1. Is this mistake somewhere else also?

2. What next bug is hidden behind this one?

3. What should I do to prevent bugs like this?

Posted On Tuesday, November 4, 2003 1:54 AM | Filed Under [ Software Testing Testing/QA-FAQ ]

TEST AUTOMATION FRAMEWORKS
An excellent ebook by "Carl Nagle"

Posted On Tuesday, November 4, 2003 1:53 AM | Comments (0) | Filed Under [ Automated Testing ]

The Product Quality Measures
1. Customer satisfaction index (Quality ultimately is measured in terms of customer satisfaction.) Surveyed before product delivery and after product delivery (and on-going on a periodic basis, using standard questionnaires) Number of system enhancement requests per year Number of maintenance fix requests per year User friendliness: call volume to customer service hotline User friendliness: training time per new user Number of product recalls or fix releases (software vendors) Number of production ......

Posted On Tuesday, November 4, 2003 1:51 AM | Filed Under [ Quality Metrics ]

Powered by: