Tom DeMarco wrote “You can’t control what you cannot measure”. If test automation has always been actively discussed, the returns of automated tests were usually described in a very general way. There have been so far very few methodologies that can provide you with unbiased assessment of your software testing automation process. This article proposes some of methods to define test automation key performance indicator (KPI).
Can you use the number of test cases as a metric? In this blog post, James Christie discusses this topic and the usefulness of counting test cases.
Software testing productivity is usually computed as the amount of testing over the effort spent for testing, but it may not be accurately measured using these size metrics. To address this issue, this article presents a new approach to estimate the software testing effort. The sizing method is called Test Case Point Analysis (TCPA).
In this blog post, Alberto Savoia discusses the CRAP (Change Risk Anti-Patterns) code metric. The CRAP metric combines cyclomatic complexity and code coverage by automated tests to help identify code that might be particularly difficult to understand, test or maintain.
“Metrics for Implementing Automated Software Testing” presents metrics that you can use to manage the transition towards automation of software tests.