Blocked Test Cases [Functional Validation]

Software Testing 101

Blocked Test Cases [Functional Validation]

What is “Blocked Test Cases”?

The  “Blocked Test Cases” DevOps quality metric measures functional test cases that could not be executed due to an external reason. For example, a test might be blocked because an environment is not ready, or because another failure prevents the test suite from reaching and executing it. 

How “Blocked Test Cases” Ranks vs. Other Quality Metrics

In new Forrester research on DevOps quality metrics, DevOps leaders ranked “Blocked Test Cases” as the #6 most valued functional validation quality metric. Of the 38% of DevOps leaders who measured this metric, 60% of them ranked it as one of their most valuable DevOps quality metrics. This metric was not found to be a “DevOps Differentiator” (DevOps experts/leaders measured it significantly more than DevOps laggards did).

Here‘s a quick look at how “Blocked Test Cases” is positioned vs. other Functional Validation Metrics—based on the raw data collected from DevOps experts. “DevOps Differentiators” are highlighted in green.

These findings are expanded upon in the new ebook: Forrester Research on DevOps Quality Metrics that Matter: 75 Common Metrics—Ranked by Industry Experts.