You are on page 1of 10

Ways to measure testing

Metrics in Software Testing


Class Presentation, Tema 4

Software Testing Metrics are the quantitative


measures used to estimate the progress, quality,
productivity and health of the software testing
process.
Why?
⭆Track the status of QA activities
⭆Measure product quality and team
efficiency
⭆Optimize the processes
How?
⭆Absolute/Base metrics
⭆Derivative/Calculated metrics
Class Presentation, Tema 4

Why Test Metrics are Important?

"We cannot improve what we cannot measure" and Test Metrics helps
us to do exactly the same.
● Take decision for next phase of activities
● Evidence of the claim or prediction
● Understand the type of improvement required
● Take decision or process or technology change
Class Presentation, Tema 4

Metrics Lifecycle

● Analysis ● Evaluation
– Identify and define the metrics – Capture the required data
– Verify validity of the data captured
– Define parameters for evaluating the
– Calculate the metrics value
metrics

● Communicate ● Reports 
– Develop the report with effective conclusion
– Explain the need and significance of
– Distribute the reports to the stakeholders,
metrics to stakeholders and testing team
developer and the testing team
– Educate the testing team about the data
– Take feedback for further improvements
points need to be captured for processing
Class Presentation, Tema 4

Absolute or Base metrics


Base Metrics are the Metrics that are derived from the data
gathered by the Test Analyst during the test case development and
execution.
⭆A number of test cases written/executed
⭆A number of test cases passed/failed/blocked/pending
⭆A number of defects found/accepted/rejected/deferred
⭆A number of critical/high/medium/low defects
⭆A number of planned & actual test hours
⭆A number of defects found during retesting/regression
Class Presentation, Tema 4

Derivative or Calculated metrics


It is obtained by converting the data that is gathered in Base
Metrics into useful information.

⭆Process metrics ⭆Product metrics


● Error discovery rate
● Test tracking metrics ● Error fix rate
● Test case preparation ● Defect density
● Defect leakage
productivity
● Test design coverage
● Test execution productivity
Class Presentation, Tema 4

Process Metrics
TEST TRACKING
METRICS

TEST CASE
PREPARATION
PRODUCTIVITY

TEST DESIGN COVERAGE

TEST EXECUTION
COVERAGE

TEST EFFECTIVENESS
Class Presentation, Tema 4

Product Metrics
ERROR DISCOVERY RATE

ERROR FIX RATE

DEFECT DENSITY

DEFECT LEAKAGE
Class Presentation, Tema 4

Process and Product metrics


Example

Total executed tests: 240


Passed tests: 181
Failed tests: 28
Blocked tests: 31

Passed tests: 181/240*100 = 75,42%


Failed tests: 28/240*100 = 11,6%
Blocked tests: 31/240*100 = 12,92%
References
https://www.qamadness.com/metrics-in-software-testing-how-are-they-
helpful/
https://www.tothenew.com/blog/software-testing-metrics/
https://www.softwaretestinghelp.com/software-test-metrics-and-measur
ements/
https://www.tricentis.com/blog/64-essential-testing-metrics-for-measuri
ng-quality-assurance-success/

You might also like