Software Testing Metrics
Uploaded by
sbk infotechSoftware Testing Metrics
Uploaded by
sbk infotechSOFTWARE TESTING METRICS
Prepared by,
B.Maaithili
Assistant Professor,
Department of Information Technology,
Saiva Bhanu Kshatriya college, Aruppukottai
SOFTWARE TESTING METRICS
• To measure the quality & efficiency of the software testing
process.
ST Metrics Taxonomy: - To categorize metrics into area like
Test Coverage Metrics - To measure the percentage of code covered by test cases. Eg: Statement
Coverage
Defect Density Metrics – To calculate the no. of defects found per unit of code. Eg: Defects per line of
code
Code Quality Metrics – To focus readability of code. Eg: Cyclomatic Complexity
Product Metrics – To measure the performance & user experiences of the software products itself.
Eg: Customer Satisfaction
Test Execution Coverage – To count the percentage of Test Cases executed during the Test Phase. Eg :
Test cases executes Vs Total Test Cases
Calculated Metrics – To derived from base metrics for analysis the Test Process. Eg :Defect Removal
efficiency
Project Metrics – To measure the efficiency & Effectiveness of Testing Team
Complexity Metrics – To analyze the complexity of software.
Linguistic Metrics
• Metrics based on measuring properties of program or
specification text without interpreting what that text
means or the ordering of components of the text.
• A metric is linguistic if its value doesn’t change when
you rearrange the text.
• For example: lines of code, number of statements,
number of unique operators, number of unique
operands, total number of operators, total number of
operands, total number of keyword appearances, total
number of tokens.
Code Count:
• Count the number of lines of code in a program and use
that number as a measure of complexity.
• Used to calculate Code Coverage Metric
• Data declarations, comments, or any other lines that did
not result in object code.
• If we include the above, it may affects maintenance costs
Statement Count
• Total no. of executable statement within a piece of code
• Used to calculate Statement Coverage Metrics
Halstead’s Metrics
• It is based on a combination of arguments derived from
common sense, information theory, and psychology.
• To evaluate the complexity of a software program
• It is based on the no. of distinct operators & operands in the
program and,
• Are used to estimate effort required to develop and maintain
the program
• Measurement parameters are,
n1 = the number of distinct operators in the program (e.g., keywords)
n2 = the number of distinct operands in the program (e.g., data objects)
N1 = program operator count(Total no. of occurrences of operator)
N2 = program operand count(Total no. of occurrences of operand)
ThanK U
