Quality is not a task at the end of a project delivery. It is the measurable outcome of the entire project delivery lifecycle.
Many software teams invest heavily in manual testing and repetitive quality assurance, although a significant share of these checks could be shifted left and automated. In this session, I will start from a practical business hypothesis: with proper quality gates, teams can reduce repetitive QA effort, lower regression risk, and spend their budget where it creates more value.
I will walk through common quality gates that are expected from professional delivery teams across the full application lifecycle, from local development and merge requests to release preparation and production integration. Some of these controls are universal to modern web applications, while others are Drupal-specific. Both need to work together to support projects that have to meet modern business requirements for security, compliance, performance, and maintainability.
The session focuses on Drupal related open-source and freely available tooling, including static analysis, coding standards, automated testing, security checks, and release controls. The goal is not to present individual tools, but to show how they can be orchestrated as measurable quality gates.
The business value is undeniable: reduced spending on repetitive manual testing, fewer regressions, stronger adherence to best practices, and faster delivery with high confidence. This way teams can establish a highly compliant and sustainable Drupal optimised delivery process.
Learning objectives
You will learn how to define a professional baseline of quality gates for Drupal projects, how to distinguish universal controls from project-specific checks, and how to place those controls across local development, merge requests, release preparation, and production.
You will also learn how to explain quality assurance measures in business terms such as security, legal compliance, financial risk, and operational reliability.