Explains in detail with example about calculation of - 1.Percentage Test cases Executed [Test Coverage] 2.Percentage Test cases not executed 3.Percentage Test cases Passed 4.Percentage Test cases Failed 5.Percentage Test cases BLOCKED/Deferred 6.Defect Density 7.Defect Removal Efficiency (DRE) 8.Defect Leakage 9.Defect Rejection ratio [Invalid bug ratio] 10.Percentage of Critical defects 11.Percentage of High defects 12.Percentage of Medium defects 13.Percentage of Low/Lowest defects

1. Test Metrics
“We can’t control things which we can’t measure”
Presented by :
DavisThomas K

2. What are
Software
Testing
Metrics?
 A Metric is a quantitative measure of the degree to which a
system, system component, or process possesses a given
attribute.
 Software Metrics are used to measure the quality of the project.

3. Test Metrics are
used to
 Evaluate testing performance and level of
quality
 Based on metrics , a better trade off between
constraints is possible
 Understand the kind of improvement required
to success the project
 Take decision on process or technology to be
modified
 Test Metrics are the most important to
measure the quality of the software.

4. Metrics Life cycle

5. Classification
Test Metrics
Base [Direct]
Metrics
Calculated
[Indirect]
Metrics
Base metrics is the raw data collected by Test Analyst during the test
case development and execution
Calculated metrics is derived from the data gathered in base metrics.

6. Basic test
Metric

7. Test Report
dashboard

8. Estimating
testing
BUG REPORT

9. Calcu
lated
Metri
cs
conv
ert
the
Base
Metri
cs
data
into
more
Percentage Test cases Executed
Percentage Test cases not executed
Percentage Test cases Passed
Percentage Test cases Failed
Percentage Test cases Blocked
Defect Density
Defect Removal Efficiency (DRE)
Defect Leakage
Defect Rejection ratio
Defects by Priority
Calculated test metrics
Calculated Metrics convert
the Base Metrics data into
more useful information.

11. PercentageTest cases
Executed
[Test Coverage]
 To obtain percentage of test case executed from total
test case
 Test Coverage= (No. ofTest cases executed /Total no.
ofTest cases written) * 100.
Test Coverage = (600/ 640) * 100 = 93.75%

12. PercentageTest cases NOT
Executed
To obtain percentage of test case NOT executed from total
test case
 Test Coverage= (No. ofTest cases NOT executed /Total
no. ofTest cases written) * 100.
Test Coverage = (40/ 640) * 100 = 6.25%

13. Percentage ofTest cases
passed
To obtain percentage of test case passed
 PercentageTest cases Passed = (No. ofTest cases
Passed /Total no. ofTest cases Executed) * 100.
Percentage of test cases Passed = (510/ 600) * 100 = 85%

14. Percentage ofTest cases failed
To obtain percentage of test case failed
 PercentageTest cases Failed= (No. ofTest cases failed/
Total no. ofTest cases Executed) * 100.
Percentage of test cases Failed= (80/ 600) * 100 = 13.33%

15. Percentage ofTest cases
blocked /deferred
This metric is used to obtain the blocked %ge of the
executed test cases.A detailed report can be submitted by
specifying the actual reason of blocking the test cases.
 PercentageTest cases blocked= (No. ofTest cases
blocked/Total no. ofTest cases Executed) * 100.
Percentage of test cases blocked= (10/ 600) * 100 =
1.67%

16. Defect Density
Defect density could be defined as the value of the total
defects which are known to the size of the software
product calculated
Defect Density = (32/ 50) = 1.67 defects / Story
Here, Size of release can be measured in terms of line of
code (LoC), user story, Functional point.

17. Advantages of defect density
•It helps measure the testing effectiveness
•It helps to differentiate defects in components/software modules
•It is useful in identifying the areas for correction or improvement
•It is useful in pointing towards high-risk components
•It helps in identifying the training needs to various resources
•It can be helpful in estimating the testing and rework due to bugs
•It can estimate the remaining defects in the software
•Before the release we can determine whether our testing is sufficient

19. Defect Removal Efficiency
(DRE)
DRE is used to identify the test effectiveness of the
system.
The defect removal efficiency (DRE) gives a measure of
the development team ability to remove defects prior to
release. It is calculated as a ratio of defects resolved to
total number of defects found.
Defect Removal Efficiency (DRE) = (No. of Defects found
during QA testing / (No. of Defects found during QA
testing +No. of Defects found by End user)) * 100
DRE = [29/ (29+ 3)] * 100 = [29/32] * 100 = 90.63%

20. Defect leakage
 Defect Leakage is the Metric which is used to identify the
efficiency of the QA testing
i.e., how many defects are missed / slipped during the QA
testing.
 Defect Leakage = (No. of Defects found in UAT / No. of
Defects found in QA testing.) * 100
DRE = [3/ 29] * 100 = 10.34%

21. Defects by Priority
Percentage of Critical defects
 Percentage of Critical Defects = No. of Critical Defects
identified /Total no. of Defects identified * 100
Percentage of Critical Defects = (10/ 32) * 100 = 31.25%

22. Defects by Priority
Percentage of High priority
defects
 Percentage of High priority Defects = No. of High priority
Defects identified /Total no. of Defects identified * 100
Percentage of Critical Defects = (5/ 32) * 100 = 15.63%

23. Defects by Priority
Percentage of Medium priority
defects
 Percentage of Medium priority Defects = No. of Medium
priority Defects identified /Total no. of Defects identified * 100
Percentage of Medium priority Defects = (12/ 32) * 100 =
37.5%

24. Defects by Priority
Percentage of Low priority
defects
 Percentage of Low priority Defects = No. of Low priority
Defects identified /Total no. of Defects identified * 100
Percentage of Low Priority Defects = (3/ 32) * 100 = 9.38%

25. Defect Rejection ratio [Invalid
bug ratio]
 Percentage of Invalid Defects = No. of Invalid Defects
identified /Total no. of Defects identified * 100
Percentage of Invalid Defects = (2/ 32) * 100 = 6.25%