Professional Documents
Culture Documents
In recent years, businesses have raised their expectations for development projects,
cutting back financial resources and at the same time demanding shorter production
cycles. Also, with increasing business and margin pressures, the projects are required to
be accomplished in lesser amount of time with fewer people, often leveraging
automation. This translates into developers and testers leveraging every opportunity to
effectively manage the quality of their product or bear the risk of releasing software
that fails the user expectations.
http://gallop.net/
Software Testing Metrics had always been an integral part of software testing projects,
but the nature and type of metrics collected and shared have changed over time. Top
benefits of tracking software testing metrics include the following:
http://gallop.net/
The general software testing metrics are divided into the following three categories:
Coverage: It refers to the meaningful parameters for measuring test scope and test
success
Progress: Deals with the parameters that help identify test progress to be matched
against success criteria. This metrics is collected iteratively over time and measures
metrics like Time to fix defects, Time to test, etc.
Quality: is used to obtain meaningful measures of excellence, worth, value, etc. of the
testing product and it is difficult to measure it directly
Some of the other Common Software Testing Metrics have been detailed below.
Coverage Metrics
The principle of coverage metrics is to communicate to all stakeholders about what is
covered during formal testing. The dimensions include validation points to evaluate
application in compliance with the requirements and weigh them by business quality.
The two types of Coverage Metrics include:
Designed Coverage = Designed Validation points / All estimated validation points
Executed Coverage = Executed Validation points / All estimated validation points
This metric determines how defects are identified and created by evaluating the
compliance with agile principles. The dimensions include the number of defects
identified in different stages of software cycle and also the number of defects created in
different stages of Software cycle.
http://gallop.net/
This is one of the important areas where we focus to minimize production leakage.
Pareto Chart is one of the standard analysis techniques, used to identify the main types
of defects that have been identified so far. Pareto uses the 80:20 rule to prioritize.
Test Coverage
This metric defines the total number of test procedures/total number of test
requirements. This Test Coverage metric will indicate planned test coverage.
Test Effectiveness
Test effectiveness needs to be assessed statistically to determine how well the test data
has exposed the defects contained in the product.
Defect Aging
http://gallop.net/
At Gallop, we look at software testing as a process that starts from the requirements
gathering stage itself, rather than at the end of the development lifecycle. Accordingly,
in addition to the above metrics, our test teams use software testing metrics relevant
for every stage of testing. This ensures there are regular checkpoints which monitor,
observe and measure the progress vs expected progress. We ensure software testing
metrics measure process output and are linked to your business strategy and corporate
goals.
To know more about the software testing metrics we use in our projects, feel free to
drop us a line at contact@gallop.net.
Tags: Common Software Testing Metrics, Measurement of Test Metrics, Need for
Software Testing Metrics, Software Testing Metrics, Software Testing Metrics and
Measurement
http://gallop.net/