TL;DR

• Test coverage (what is planned, what we have achieved now, how many smoke/regression)
• Automation coverage (how many ready_for_automation, number/percentage of automated test cases)
• Defects metrics (found, fixed, how many found by automation)
• Test execution results: Run, Passed, Failed, Blocked, Skipped. Time spend for executing. Metrics by modules.
• Testing frequency (what is planned, what is actual)
• Test efficiency (defects found by you and defects found by customer)
• Sprint metrics (what did we do during this sprint)

What are the testing metrics?

Metrics help us measure the effectiveness of testing, test cases, if we have bugs → that means that metrics are not effective enough. Estimate progress

• Metrics measure progress, quality, productivity of the testing, and quality of product.
• Help make better decisions for further testing.

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

QA Metrics

• Project metrics: measure progress toward established project exit criteria, such as the percentage of test cases executed, passed, and failed
• Product metrics: measure some attribute of the product, such as the extent to which it has been tested or the defect density
• Process metrics: measure the capability of the testing or development process, such as the percentage of defects detected by testing