When used properly, test metrics can aid in software development process improvement by providing pragmatic, objective evidence of process change initiatives. Metrics are defined as "standards of measurement" and have long been used in the IT industry to indicate a method of gauging the effectiveness and efficiency of a particular activity within a project. Although test metrics are gathered during the test effort, they can provide measurements of many different activities performed throughout a project. In conjunction with root cause analysis, test metrics can be used to quantitatively track issues from points of occurrence throughout the development process. In addition, when test metrics information is accumulated, updated and reported on a consistent and regular basis, it ensures that trends can be promptly captured and evaluated.
Test metrics exist in a variety of forms, and the question is not whether metrics should be used, but which ones should be used. The five points I present here serve as a guide for instituting a metrics program.
