
MS Dashboard (@Demo) - v120.2.3
General
Informational
Read in
Key QA Metrics: How to Calculate, Implement, and Use Them Effectively

The other day I was chatting with a tester I know and we had this dialog:

After this dialog, I thought about how the metrics-related processes were set up in some of my projects:
- In one of them, only the developer was notified about critical bugs on the prod, who had to fix the bug urgently. As a result the bug is fixed, but the tester will not even be aware of this bug. This process makes it impossible to collect metrics related to bugs
- In another project, not all tasks are tested by the tester. For example, some trivial changes may be rolled out in the release even without notifying the tester, although in fact these changes may cause some regression bugs
- And on another project, where all tasks and bugs go through the tester — there are no metrics at all, because there was no sense in them specifically for that product. And that’s okay
Each project is a separate story. Metrics can be a tool that aligns processes and helps the team, but they are definitely not universal or even always needed. In this article, I want to talk about some good metrics, namely how to calculate, implement and use them in the future. Let’s go!
1. Test Coverage of Requirements
What is this metric?
This metric will reflect how much of the requirements are covered by tests and helps to assess test completeness and minimize the risk of missing critical bugs.
How is it calculated?
Get the MessageSpring App for Better Experiences!
Get the MessageSpring App for Better Experiences!
Recent messages from

MS Dashboard (@Demo) - v120.2.3
Academy • Krung Thep Maha Nakhon (Bangkok), Thailand