Scribd
Upload
141 views

What Is A Test Strategy?

A test strategy provides a roadmap that describes the testing steps, their timing, and required resources. It incorporates test planning, design, execution, and evaluation. Debugging occurs after testing reveals errors. It involves methodically eliminating causes to identify the root problem. Various metrics can measure testing effectiveness, including test case adequacy, defect detection rate, and cost of quality.

Uploaded by

vinitajenny
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
141 views

What Is A Test Strategy?

A test strategy provides a roadmap that describes the testing steps, their timing, and required resources. It incorporates test planning, design, execution, and evaluation. Debugging occurs after testing reveals errors. It involves methodically eliminating causes to identify the root problem. Various metrics can measure testing effectiveness, including test case adequacy, defect detection rate, and cost of quality.

Uploaded by

vinitajenny
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 14

What Is a Test Strategy?

• It provides a road map that describes the steps to be conducted as


part of testing, when these steps are planned and then undertaken,
and how much effort, time and resources will be required.

• It must incorporate test planning, test case design, test execution


and resultant data collection and evaluation.
Debugging
• Occurs as a consequence of successful testing

• Is an action that results in the removal of the error

• Results of the test give a “symptomatic” indication of the


software problem
Debugging - Is it difficult?
• The symptoms may be caused by human errors.
• The symptom may be because of a timing problem rather than
processing problem.
• The symptom may be intermittent.

First step in fixing a broken program is getting it to fail repeatably. –


T.Duff
Debugging
Debugging by Brute Force

1. By studying Storage Dumps


2. by invoking run-time traces
3. by scattering print statements
• by use of automated debugging tools
Debugging
Cause elimination
Debugging by Induction
1. Locate data
2. Organize data
3. Device a hypothesis
4. Prove the hypothesis
Debugging by deduction
1. enumerate the causes
2. eliminate each cause
Debugging
Debugging by Backtracking
Beginning at the place where the symptom is uncovered, the
source code is traced backward until the site of the cause is
found
Debugging

Error Analysis - When Correcting the error , ask these three questions :
- Is the cause of the bug reproduced in another program?
- What “next bug” might be introduced by the fix that I’m
about to make?
- What could we have done to prevent this bug in the first place?
Debugging

Error Analysis - When Correcting the error , ask these three questions :
- Is the cause of the bug reproduced in another program?
- What “next bug” might be introduced by the fix that I’m
about to make?
- What could we have done to prevent this bug in the first place?
Testing Metrics
Test Case Adequacy
• Test Case Adequacy = No. of actual Test cases * 100 / No. of
test cases estimated
Test Case Effectiveness
• Test Case Effectiveness = # of defects detected using the test
cases * 100/ total # of defects detected in testing
Defect Detection Index
•  Defect Detection Index = # of defects detected in each phase
/ total # of defects planned to be detected in each phase
Metrics
• Why Measure
 Tracking Projects against plan
 Take timely corrective actions
 Getting early warnings
 Basis for setting benchmarks
 Basis for driving process improvements
 Tracking process performance against business
 objectives
Testing Metrics
Test Case Adequacy
• Test Case Adequacy = No. of actual Test cases * 100 / No. of
test cases estimated
Test Case Effectiveness
• Test Case Effectiveness = # of defects detected using the test
cases * 100/ total # of defects detected in testing
Defect Detection Index
•  Defect Detection Index = # of defects detected in each phase
/ total # of defects planned to be detected in each phase
Testing Metrics
Defect Density
• Total Defect density = (Total number of defects found in all
the phases + Post delivery defects)/Size
Average Defect Age
• Average Defect age = (Sum of ((Defect detection phase
number – defect injection phase number) * No of defects
detected in the defect detection phase))/(Total Number of
defects till date)
Defect Removal Efficiency
• DRE = 100 * No. of pre-delivery defects / Total No. of Defects
Testing Metrics
Review Effectiveness
• Review Effectiveness = 100 * Total no. of defects fond in
review / Total no. of defects
Cost of finding a defect in review(CFDR)
• Cost of finding a defect in reviews = (Total efforts spent on
reviews / No. of defects found in reviews)
Cost of finding a defect in testing(CFDT)
• Cost of finding a defect in testing = (Total efforts spent on
testing / defects found in testing)
Testing Metrics
Cost of Quality
• % Cost of Quality = (Total efforts spent on Prevention + Total
efforts spent on Appraisal + Total efforts spent on failure or
rework)*100/(Total efforts spent on project)

• Failure cost = Efforts spent on fixing or reworking the pre-


delivery defects + (3 * efforts spent on fixing or reworking the
post-delivery defects)

You might also like