This document discusses the importance of testing metrics and recommends several metrics that should be tracked. It recommends tracking individual service performance, scenarios run in each build, security warnings, test coverage, code quality metrics, number of tests and test run time, defects by priority, number of defects from production, defects by module, and mean time between build failures. The document emphasizes that metrics help make testing trends visible, improve ownership and prevent issues, but not all metrics are needed for every project and metrics should help rather than replace human judgment.