The 6 Essential Quality Gates You Need in Your CI/CD

This session explores the shortcomings of traditional testing and QA methods and offers clear criteria for establishing CI/CD quality gates to ensure bad code never gets promoted.

Enterprises today are all about increasing the velocity of software development and delivery. But with shorter release cycles, code quality is often sacrificed.

As the first line of defense for software quality and customer experience, QA teams are under pressure to prevent code defects from escaping into production, yet they need to also manage unprecedented workloads with less time and resources to invest in testing code than ever before.

The fact that most organizations still encounter significant production errors on a somewhat regular occasion speaks to the shortcomings and resource constraints of today’s QA processes. Most testing methods require pre-defined conditions and an impossible level of foresight into “unknown unknowns.” Even when tests are designed for 100% code coverage, not all issues can be accounted for. Additionally, many QA processes are still too manual, and the pressure to move fast means tests are written poorly, or not executed properly.

To help address these gaps, we’ve identified 6 key quality gates that can be built into your CI/CD pipeline using open source plugins and used to more clearly determine if a release is truly safe enough to be promoted.

The six gates are:

1. New Errors – Did the release introduce any errors that didn’t previously exist?

2. Critical Exceptions – Did the release introduce any severe/showstopping errors?

3. Increasing Error Rate – Did the rate of a known error increase dramatically in this release?

4. Resurfaced Errors – Did an error that was previously resolved appear again in the current release?

5. Total Error Volume – Did this release introduce a dangerous spike in the total volume of errors?

6. Unique Error Volume – Did the release introduce an unusually high number of many unique (i.e. discrete) errors?

In this session, we’ll discuss the challenges and shortcomings of current QA and testing methods mentioned above in more detail, and then clearly define these six quality gates, including examples of how they work, best practices for configuring thresholds and where to access the necessary open source resources.

More Related Sessions

30-minute Talk

10:30 a.m. – 11:00 a.m.

Automating the New York Times Crossword

30-minute Talk

4:15 p.m. – 4:45 p.m.

Agile Document Delivery

30-minute New Voice Talk

2:30 p.m. – 3:00 p.m.

Security Tooling in Your DevOps Pipeline

Full-Day Tutorial (6 hours)

9:00 a.m. – 5:00 p.m.

1-day Tutorial: Selenium WebDriver with Java

Equipment required

Your privacy matters

We use cookies to understand how you use our site and to give you the best experience on our website. If you continue to use this site we will assume that you are happy with it and accept our use of cookies and Privacy Policy.