QA metrics

Contents
Metric: Customer satisfaction...........................................................................................................2
Metric: Number of tests run over a certain duration (test velocity)..................................................2
Metric: Test review rate: Number of tests reviewed / Total duration...............................................3
Metric: Metric: Test Case Productivity (Average bugs per test)........................................................3
Fix failure rate....................................................................................................................................4
Test time vs estimate.........................................................................................................................4
Metric: Customer satisfaction

Description: How satisfied is the end user with the product they received?

Measuring customer satisfaction is crucial for any business, as it can provide valuable insights into
the success of a product or service.

However, simply focusing on metrics such as bug fixes and performance improvements may not be
enough to fully gauge customer satisfaction. A product that is technically sound may still fail to meet
the needs and expectations of its target audience. For example, a product that meets all technical
requirements but lacks the features that users desire may not be successful.

In contrast, a product that is engaging and enjoyable to use may succeed even if there are some
residual technical issues. This is especially true in the world of gaming, where user engagement and
enjoyment are often more important than technical perfection. A game with some remaining bugs
may still be highly rated if it is fun and immersive.

In other words, a red sign-off indicating unresolved technical issues may be less important if the final
product has a high approval rating from users. This highlights the importance of considering
customer satisfaction as a key metric for product success.

It's important to think about whether it will be a long-term title. If a product is intended to have a
long lifespan, it's critical to continue listening to user feedback and making updates and
improvements over time.

How to implement:

Uses:

Currently tracked: To some extend.

Metric: Number of tests run over a certain duration (test velocity)

Description:

How to implement:

Uses:

Currently tracked:
Metric: Test review rate: Number of tests reviewed / Total duration

Description:

How to implement:

Uses:

Currently tracked:

Metric: Metric: Test Case Productivity (Average bugs per test)

Description:

How to implement:

Uses:

Currently tracked:

Consider structuring along lines of cost or depth or area

Fix failure rate

Test time vs estimate