What metrics are important to you for evaluating your software QA testing? Choose the top 3 methods.

Test coverage metrics such as % of requirements covered.39%

Test effectiveness metrics such as % of defects in production47%

Test execution metrics such as # of tests completed, # passed, # failed53%

Test effort metrics, such as #of tests run, defects per test hour, time to fix32%

Defect distribution metrics, such as platform, severity, test type30%

Economics metrics, such as total cost of testing, cost per fix, budget variance17%

Automation metrics, such as % of automation coverage, time to deliver new scripts16%

Qualitative measures such as team reviews, retrospectives10%

Other0%

Limited environment/Infrastructure resources31%

Inability to quickly identify the root cause of CI/CD pipeline failures45%

Lack of standardized CI/CD pipeline templates across the organization53%

Integrating security tools - inefficient security implementation leading to false positives38%

Poor communication across business and product teams/coordination challenges26%

Cost/resource management26%

Implementation of CI/CD into on-going projects and workflows22%

Internal resistance: training issues, culture, etc.14%

Inefficient implementation of CI/CD due to lack of expertise, poor training, etc.19%

Poorly written unit and acceptance testing9%

We are not doing regression testing10%

25% manual, 75% automated50%

50% manual, 50% automated28%

100% manual, 0% automated8%

Don't know2%