See what's new on Keypup!  📢

Change Failure Rate (PR based)

Connect your Git repository to calculate the ratio of failure in production among all merged pull requests.

Use CFR Metric

Automate Change Failure Rate (CFR) Calculation from Your Git Pull Requests

with the

Change Failure Rate (PR based)

Connect your Git repository to calculate the ratio of failure in production among all merged pull requests.

Use CFR Metric
Change Failure Rate (PR based)Change Failure Rate (PR based)Change Failure Rate (PR based)

From startups to large enterprises, Keypup serves all the unique complexities related to project size, structure and teams, including:

“Keypup has been instrumental in helping us gain a better perspective on our engineering activities and identifying bottlenecks. Its ease of use combined with its comprehensive features made a difference for us”

Bruno D'Auria

Engineering Director

“Great product with great support!

Keypup is extremely flexible in its reporting. Once you get your raw data connected, there is almost nothing it can't do. There is a wealth of tables, charts and other reports available. As Director of a software development team, I use Keypup to report on our work efficiencies to senior managment. Keypup makes this task very simple to produce each week.”

Brad B.

Director, Software Development

Understand the Pull Request Based Change Failure Rate

Based on the pull request labeling, this metric detects commits related to bug fixes. The template detects pull requests with the label "bug." You should adapt this label filter (or list of labels) to reflect your own naming convention.

What Good Looks Like for Change Failure Rate and How to Improve It?

Based on DORA metrics, elite performers are defined as teams or organizations with a CFR between 0% and 15%.

How to Improve Your Change Failure Rate

To improve CFR, you can:

  • Add linters and code analysis tools to let developers fix styling issues and keep reviewers focused on business logic code.
  • Automate end-to-end (E2E) testing so your QA and Product teams can spend more time on progressive rather than regression testing.
  • Train your testing team to properly test edge cases, document any unstable flow, and incorporate previous incident steps into your test cases.
  • Ensure your test environment(s) accurately reflect production to improve testing quality and reduce the likelihood of critical production-specific bugs.
Use CFR Metric