A huge joint stable release of AI was made yesterday, where 10 modules were updated to 1.1.0. This is a major milestone in the Drupal AI brings a host of improvements and significant new features. 

Announcement by Marcus Johansson.

Some technical facts of the AI release:

• 105 issues fixed on AI Core, 75 issues fixed on AI Agents and roughly 25 issues on providers.
• 90 unique contributors on AI Core
• 244 files changed, 6500 lines added, 15044 lines removed on AI Core.

The most important update is function calling and a new agent framework, but here is a list of some other new features:

• Custom Operation Types
• Drush command to run AI
• Make the chatbot tell it what its doing, while its doing it
• Make it possible to add autocomplete fields to AI Automator Chains on CKEditor
• AI Content Suggestion can be based on the rendered HTML of the entity
• Normalized Structured Response
• Any many more

Some things directly connected to it:

• Drupal CMS AI agents have been updated and are now 90% effective up from 80%.
• A new test framework has been created so can see their effectiveness more clearly and non developers can create new tests.
• Improvements to AI search making use of function calling means they will more accurately search when you ask it to.
• Over 1000 people in the #ai slack
• An officially funded AI position and a Strategic initiative with multiple companies to make this sustainable
• 4600 installs of AI up from 3000 at Atlanta

Full details of Drupal AI 1.1.0

🚀 Major New Feature: Agentic Framework

The by far largest feature is the new Agentic framework where anyone can build agents without writing a single line of code. They are stored as configurations, meaning that you can build once, export and ship anywhere. And you can trigger them from anywhere you want - Chatbot, CLI, widgets, via an API etc.

Because Drupal is such a flexible and stable CMF, it will be the perfect agent runner. It adheres automatically to your contents permissions, files etc. while also keeping humans in the loop.

With the announcement of the new AI Initiative the future looks bright for Drupal and AI, the announcement is here if you haven't seen it.

🔧 Standards-Based Tooling

We’ve implemented the tooling in a MCP-standardized way, which opens the door for seamless integration with external tools—and makes it easier to share and reuse agents and tools across systems and languages.

🧠 Visual Tools for Everyone

Outside of this we have also added a visual AI Agents Testing Tool where you can setup complex scenarios and retest them over and over, without having to be a developer. An advanced agent tracing tool is also in the pipeline!

And in the 1.1.0 release we also have the possibility to setup the agents via the modeler api and BMPN.io in a graphical way thanks to Jürgen Haas! He also has a visual way of building tools on the way.

The hope is that everything we build, should be possible to use directly from the browser!

🙌 Thank You

I thought I would thank a list of people that have contributed to this, but I checked the unique contributors via git and got 90 people. So I will not try to list everyone, because I will surely forget someone - but special thanks to James Abrahams and FreelyGive Ltd for giving me the opportunity to work with this full time (and more :) )!

It will be really exciting what kind of agents people will build, we have already tried everything from agents that checks configuration diffs for you, to agents that builds components from images. Hopefully your imagination, and not the framework, will be the limit ;)

We have a MR that can be tested for using this within Drupal CMS as well.

For anyone interested in the new agent framework I did a presentation on it at Drupal Days Leuven and also have a longer developers preview. More videos and documentation to follow.

Welcome to the June 2025 DDEV Newsletter
This month: TYPO3 Community Budget Proposal (VOTE NOW), Randy is back from bikepacking, Running Old PHP versions, Vite and DDEV with WordPress, DDEV Architecture, and more.

TYPO3: Your Vote Requested Before June 16!

• Q3 TYPO3 Budget Proposal: Improved GitHub Codespaces and Dev Containers support - We’ve proposed significant enhancements to make DDEV shine in GitHub Codespaces and Dev Containers. This will help TYPO3 and all DDEV users. If you're a TYPO3 member, please cast your vote to help the DDEV proposal using the email you received from the TYPO3 Foundation before June 16. → Read more↗

What’s New

• Randy is back from bikepacking!
  We covered lots of territory out in the state of New Mexico and had a great time. I'll never forget though, laying in my tent when we had some coverage and watching the DDEV community continue on supporting each other so very successfully. And every support answer from Stas was exactly what I would have said. I'm proud and amazed by this wonderful community.
• Using DDEV to Spin Up A Legacy PHP Application
  A guest blog by TYPO3 contributor Garvin Hickling on how to use DDEV to run a (very) old PHP 5.3/MySQL 5.5 application → Read more↗
• Securing DDEV’s Future: Our Commitment to Financial & Community Sustainability Read more↗
• 106 GitHub Sponsors
  We now have 106 GitHub Sponsors! Breaking our aggregation script was a delightful milestone—thank you for believing in DDEV.
• May 2025 Advisory Group Meeting Notes → Read more↗. Join us July 2; ask for a calendar invitation in the DDEV Discord or the contact page.

Community Tutorials

• Integrating Vite and DDEV into WordPress → Read more↗
• AI-generated DDEV Architecture by DeepWiki, pretty impressive! → Read more↗
• Setup an existing WordPress multisite locally with DDEV (with Bonus Pantheon support!) from Kalamuna → Read more↗

Governance & Roadmap

• Apache Foundation-inspired Project Management Committee Exploration
  We’re exploring a governance model inspired by the Apache Foundation and Backdrop CMS to better support long-term sustainability and shared leadership. Take a look and join the conversation about future DDEV governance → Details↗

Sponsorship Status

• Monthly average income up from $7,639 to $7,809 (65% of $12,000 goal, up a percent since early May!). Every contribution helps sustain our work—thank you! → Become a sponsor↗

Stay in the loop—follow us and join the conversation

• Blog↗
• LinkedIn↗
• Mastodon↗
• Bluesky↗
• Discord↗

Website Availability - handling an outage

Jun 12, 2025 By John Locke 0

How do you get a website back up, when it goes down?

Dev Corner Read More

This blog has been re-posted and edited with permission from Dries Buytaert's blog.

Drupal launches its AI Initiative with more than $100,000 in funding and a dedicated team to build AI tools for website creation and content management.
 

Imagine a marketer opening Drupal and with a clear goal in mind: launch a campaign for an upcoming event.

They start by uploading a brand kit to Drupal CMS: logos, fonts, and color palette. They define the campaign's audience as mid-sized business owners interested in digital transformation. Then they create a creative guide that outlines the event's goals, key messages, and tone.

With this in place, AI agents within Drupal step in to assist. Drawing from existing content and media, the agents help generate landing pages, each optimized for a specific audience segment. They suggest headlines, refine copy based on the creative guide, create components based on the brand kit, insert a sign-up form, and assemble everything into cohesive, production-ready pages.

Using Drupal's built-in support for the Model Context Protocol (MCP), the AI agents connect to analytics tools and monitor performance. If a page is not converting well, the system makes overnight updates. It might adjust layout, improve clarity, or refine the calls to action.

Every change is tracked. The marketer can review, approve, revert, or adjust anything. They stay in control, even as the system takes on more of the routine work.

Why it matters

AI is changing how websites are built and managed faster than most people expected. The digital experience space is shifting from manual workflows to outcome-driven orchestration. Instead of building everything from scratch, users will set goals, and AI will help deliver results.

This future is not about replacing people. It is about empowering them. It is about freeing up time for creative and strategic work while AI handles the rest. AI will take care of routine tasks, suggest improvements, and respond to real-time feedback. People will remain in control, but supported by powerful new tools that make their work easier and faster.

The path forward won't be perfect. Change is never easy, and there are still many lessons to learn, but standing still isn't an option. If we want AI to head in the right direction, we have to help steer it. We are excited to move fast, but just as committed to doing it thoughtfully and with purpose.

The question is not whether AI will change how we build websites, but how we as a community will shape that change.

A coordinated push forward

Drupal already has a head start in AI. At DrupalCon Barcelona 2024, I showed how Drupal's AI tools help a site creator market wine tours. Since then, we have seen a growing ecosystem of AI modules, active integrations, and a vibrant community pushing boundaries. Today, about 1,000 people are sharing ideas and collaborating in the #ai channel on Drupal Slack.

At DrupalCon Atlanta in March 2025, I shared our latest AI progress. We also brought together key contributors working on AI in Drupal. Our goal was simple: get organized and accelerate progress. After the event, the group committed to align on a shared vision and move forward together.

Since then, this team has been meeting regularly, almost every day. I've been working with the team to help guide the direction. With a lot of hard work behind us, I'm excited to introduce the Drupal AI Initiative.

The Drupal AI Initiative builds on the momentum in our community by bringing structure and shared direction to the work already in progress. By aligning around a common strategy, we can accelerate innovation.

What we're launching today

The Drupal AI Initiative is closely aligned with the broader Drupal CMS strategy, particularly in its focus on making site building both faster and easier. At the same time, this work is not limited to Drupal CMS. It is also intended to benefit people building custom solutions on Drupal Core, as well as those working with alternative distributions of Drupal.

To support this initiative, we are announcing:

• A clear strategy to guide Drupal's AI vision and priorities (PDF mirror).
• A Drupal AI leadership team to drive product direction, fundraising, and collaboration across work tracks.
• A funded delivery team focused on execution, with the equivalent of several full-time roles already committed, including technical leads, UX and project managers, and release coordination.
• Active work tracks covering areas like AI Core, AI Products, AI Marketing, and AI UX.
• USD $100,000 in operational funding, contributed by the initiative's founding companies.

For more details, read the full announcement on the Drupal AI Initiative page on Drupal.org.

Founding members and early support

Some of the founding members of the Drupal AI initiative during our launch call on Google Hangouts.

Over the past few months, we've invested hundreds of hours shaping our AI strategy, defining structure, and taking first steps.

I want to thank the founding members of the Drupal AI Initiative. These individuals and organizations played a key role in getting things off the ground. The list is ordered alphabetically by last name to recognize all contributors equally:

• Jamie Abrahams (FreelyGive) – Innovation and AI architecture
• Baddý Breidert (1xINTERNET) – Governance, funding, and coordination
• Christoph Breidert (1xINTERNET) – Product direction and roadmap
• Dries Buytaert (Acquia / Drupal) – Strategic oversight and direction
• Dominique De Cooman (Dropsolid) – Fundraising and business alignment
• Marcus Johansson (FreelyGive) – Technical leadership
• Paul Johnson (1xINTERNET) – Marketing and outreach
• Kristen Pol (Salsa Digital) – Cross-team alignment and contributor engagement
• Lauri Timmanee (Acquia) – Experience Builder AI integration
• Frederik Wouters (Dropsolid) – Communications and outreach

These individuals, along with the companies supporting them, have already contributed significant time, energy, and funding. I am grateful for their early commitment.

I also want to thank the staff at the Drupal Association and the Drupal CMS leadership team for their support and collaboration.

What comes next

I'm glad the Drupal AI Initiative is now underway. The Drupal AI strategy is published, the structure is in place, and multiple work tracks are open and moving forward. We'll share more details and updates in the coming weeks.

With every large initiative, we are evolving how we organize, align, and collaborate. The Drupal AI Initiative builds on that progress. As part of that, we are also exploring more ways to recognize and reward meaningful contributions.

We are creating ways for more of you to get involved with Drupal AI. Whether you are a developer, designer, strategist, or sponsor, there is a place for you in this work. If you're part of an agency, we encourage you to step forward and become a Maker. The more agencies that contribute, the more momentum we build.

Update: In addition to the initiative's founding members, Amazee.io already stepped forward with another commitment of USD $20,000 and one full-time contributor. Thank you! This brings the total operating budget to USD $120,000. Please consider joining as well.

AI is changing how websites and digital experiences are built. This is our moment to be part of the change and help define what comes next.

Join us in the #ai-initiative channel on Drupal Slack to get started.

Austria’s leading Drupal agency, drunomics, balances business goals with deep community involvement. In a conversation with The DropTimes’ Thomas Alias, CTO Wolfgang Zeigler shares how the agency tackles open-source challenges, champions ecosystem growth, and embeds contribution into daily operations.

Drupal Modeler API ready for testing Jürgen Haas Wed 11 Jun 2025 - 08:35

The Modeler API is a new module that has been created by the Drupal community to address the requirement of existing modules and ecosystems with complex configurations, providing modern and easy-to-use UIs for non-technical users so they can independently create, modify, and maintain their own sites. Examples of such ecosystems are ECA (Events, Conditions, Actions - Drupal's modern rules engine), AI Agents, and Migrations.

In this episode, Ivan Stegic and Randy Oest discuss the impact of AI on junior developers and other roles, debating whether AI will be a disruptive force in the job market. They delve into the complexities of using LinkedIn for job hunting and effective networking strategies. The conversation shifts to new features in Figma, the potential of AI-driven coding tools like Cursor, and the importance of investing in junior developers. They also explore higher education design systems, innovative business strategies, and reflect on the balance between tactical and digital controls in modern cars. The episode wraps up with a light-hearted chat about slang, parental roles, and mentorship.

For show notes visit: https://www.talkingDrupal.com/cafe004

Topics Ivan Stegic

Ivan is a prominent leader in the Drupal community and the founder of TEN7, a Minneapolis-based technology studio specializing in Drupal development, strategy, and digital transformation. With a background in physics and a passion for problem-solving, Ivan transitioned from science to tech, ultimately finding a perfect fit in the open-source world of Drupal. Since founding TEN7 in 2007, Ivan has championed Drupal as a powerful, scalable platform for mission-driven organizations, nonprofits, and enterprises. Under his leadership, TEN7 has delivered impactful Drupal solutions for clients across education, healthcare, and government sectors. Ivan is also known for fostering a people-first company culture grounded in trust, transparency, and continuous improvement. Beyond his work at TEN7, Ivan is an active contributor to the Drupal project, frequently speaking at DrupalCons and camps, hosting the ONE OF 8 BILLION podcast (formerly the TEN7 Podcast), and mentoring others in the community. His advocacy for open source and ethical tech underscores his commitment to using Drupal to make the internet—and the world—a better place.

Randy Oest

Randy is a design strategist, creative director, and accessibility advocate helping mission-driven organizations craft inclusive, user-centered digital experiences. With a background that spans visual design, front-end development, and content strategy, Randy specializes in building scalable design systems and digital platforms—particularly within the Drupal ecosystem. As the former Creative Director at Four Kitchens, Randy led cross-functional teams in developing cohesive design strategies, architecting front-end systems, and aligning user experience with organizational goals. He’s known for bridging the gap between high-level vision and implementation, ensuring that every project is both beautiful and deeply usable. Beyond his client work, Randy is a frequent speaker at DrupalCon, regional camps, and virtual events, where he shares insights on accessibility, usability, and design systems. A passionate advocate for open-source collaboration and digital equity, he is committed to making the web a more inclusive and empowering space for everyone.

• Debunking AI Myths: Junior Developers Are Here to Stay
• Casual Catch-Up: Podcast Conversations and AI Avatars
• LinkedIn: A Wasteland or a Goldmine?
• Creative Networking: From Fortune Tellers to Meaningful Connections
• Figma Innovations: Draw and Sites
• The Future of Coding: AI Tools and Junior Developers
• Flying Cars and Spam Texts
• Dealing with Spam Texts
• Exploring Higher Education Design Systems
• The Onion's Creative Agency
• The Importance of Tactile Controls in Cars
• Wrapping Up and Future Plans

Guests

Ivan Stegic - TEN7 ivanstegic Randy Oest - amazingrando.com amazingrando

In this final installment of a multi-part series, Professor Graham Leach examines the Drupal Project’s 2024 decision to end support for Drupal 7. The article analyzes why migration efforts failed, assesses the project's strategic shift, and outlines the broader consequences for open source users and maintainers. Key insights include the limits of technology adoption, the realities of long-term support, and the need for new governance models in Free and Open Source Software.

Comparing Drupal Cookie Consent Modules: Finding the Right Fit for GDPR and Privacy Compliance bhavinhjoshi Wed, 06/11/2025 - 11:29

With privacy regulations like GDPR, CCPA, and ePrivacy directives tightening globally, implementing a robust cookie consent solution on your Drupal site is essential. Drupal offers several cookie consent modules to help website owners comply with these laws while enhancing user trust. In this blog post, we’ll compare the most prominent Drupal cookie consent modules, including Klaro Cookie & Consent Management, to help you choose the best fit for your site. We’ll explore their features, ease of use, and compliance capabilities, concluding with a detailed comparison table.

Disclaimer: No liability is assumed regarding compliance with GDPR or other regulations. Always consult legal experts to ensure your site meets local privacy requirements.

Comparing Drupal Cookie Consent Modules Overview of Drupal Cookie Consent Modules

Here’s a breakdown of the key Drupal cookie consent modules available as of June 2025, based on their functionality, configuration options, and compliance features:

1. Klaro Cookie & Consent Management

• Source: https://www.drupal.org/project/klaro
• Description: Klaro is an open-source consent management module that integrates the Klaro! JavaScript library, offering a lightweight, user-friendly way to manage cookie consent. It provides fine-grained control over services, purposes, and external resources, ensuring compliance with GDPR and ePrivacy regulations. Klaro automatically blocks non-essential scripts until user consent is granted and supports multilingual sites.
• Key Features:
  • Customizable consent banners with opt-in/opt-out options.
  • Automatic attribution of HTML script tags to block third-party resources.
  • Supports multiple dialog modes (Silent, Notice, Modal, Consent Modal).
  • Multilingual support with translatable texts.
  • Blocks unknown external resources by default.
  • Stores consent decisions in a strictly necessary cookie (klaro).
  • Actively maintained with a stable 3.x branch release candidate as of December 2024.
• Ease of Use: Requires some technical knowledge to configure services and purposes, but the admin interface is intuitive. Automatic attribution simplifies script management for developers.
• Best For: Sites needing a lightweight, open-source solution with granular control over third-party services.

2. COOKiES Consent Management

• Source: https://www.drupal.org/project/cookies
• Description: The COOKiES module focuses on GDPR-compliant user consent management, enabling third-party integrations (e.g., Google Analytics, Facebook Pixel) to function only after user consent. It offers a fully customizable, responsive banner and supports accessibility.
• Key Features:
  • Fully responsive and translatable UI.
  • Accessibility-compliant design.
  • Supports third-party integrations like Google Tag Manager, Matomo, and video embeds.
  • Customizable styling via CSS variables or SCSS.
  • Includes a “Cookies settings” link for user preference changes.
  • Configurable scroll limit to delay banner display for performance.
• Ease of Use: Developer-friendly with examples for integrating third-party modules. Configuration is straightforward via the admin interface, though styling may require CSS knowledge.
• Best For: Sites with multiple third-party integrations needing a customizable, accessible banner.

3. Cookie Consent Notice by CookieYes

• Source: https://www.drupal.org/project/cookieyes
• Description: CookieYes is a third-party service integrated into Drupal, offering automated cookie scanning and compliance with GDPR, CCPA, and other privacy laws. It provides a user-friendly front-end integration without backend modifications.
• Key Features:
  • Automatic cookie scanning and categorization.
  • Customizable opt-in/opt-out banners with multilingual support.
  • Geo-targeting to display banners only in specific regions.
  • Consent logging and proof-of-consent documentation.
  • Supports Google Consent Mode and IAB TCF.
  • Blocks non-essential scripts until consent is granted.
• Ease of Use: Extremely easy to set up due to automated scanning and minimal configuration. Ideal for non-technical users, though it relies on an external service.
• Best For: Sites seeking a plug-and-play solution with automated compliance features.

4. EU Cookie Compliance (GDPR Compliance)

• Source: https://www.drupal.org/project/eu_cookie_compliance
• Description: One of the oldest and most widely used Drupal cookie consent modules, EU Cookie Compliance provides a GDPR-compliant banner with flexible consent methods. It supports blocking cookies and scripts until consent is obtained and is actively maintained with Drupal 10 compatibility.
• Key Features:
  • Multiple consent methods: consent by default, opt-in, opt-out.
  • Customizable banner placement (top/bottom) and styling.
  • Geo-targeting with Smart IP or GeoIP modules.
  • Multilingual support for global audiences.
  • Blocks cookies and scripts until consent is granted.
  • Roadmap for a 2.0 rewrite with enhanced features.
• Ease of Use: User-friendly configuration with clear options for consent methods and banner placement. Some advanced features (e.g., geo-targeting) require additional modules.
• Best For: Sites needing a mature, reliable solution with EU-specific compliance options. Note: Maintainers recommend switching to Klaro for modern Drupal sites due to focus on maintaining stable releases.

5. Simple Klaro

• Source: https://www.drupal.org/project/simple_klaro
• Description: A lightweight alternative to the main Klaro module, Simple Klaro provides a minimal implementation of the Klaro! JavaScript library. It relies on a single configuration file for settings, making it ideal for simple setups.
• Key Features:
  • Basic consent banner with customizable texts and translations.
  • Controls script execution based on consent.
  • Deletes cookies via regular expressions when consent is revoked.
  • Minimal configuration via a single file.
  • Multilingual support based on HTML lang attribute.
• Ease of Use: Requires manual configuration of the Klaro JSON file, which may be challenging for non-developers. Cache clearing on settings changes simplifies updates.
• Best For: Small sites or developers comfortable with JSON configuration seeking a lightweight Klaro implementation.

6. CookieConsent

• Source: https://www.drupal.org/project/cookieconsent
• Description: CookieConsent integrates the Cookie Consent JavaScript plugin (version 2.0.9) to provide a simple, lightweight solution for EU Cookie Law compliance. It’s maintained by Synetic but has no stable releases as of June 2025.
• Key Features:
  • Lightweight consent banner with basic customization.
  • No external module dependencies.
  • Uses an older version of the Cookie Consent plugin.
  • Limited to basic cookie consent functionality.
• Ease of Use: Easy to set up for basic needs, but lacks advanced features and modern compliance options. Configuration is minimal but dated.
• Best For: Small sites with minimal cookie usage needing a quick, basic solution. Note: Limited maintenance and outdated plugin version make it less suitable for modern compliance needs.

Key Considerations for Choosing a Module

When selecting a cookie consent module, consider the following factors:

• Compliance Needs: Ensure the module supports GDPR, CCPA, and other relevant regulations. Features like consent logging (CookieYes) or geo-targeting (EU Cookie Compliance, CookieYes) are critical for region-specific compliance.
• Ease of Setup: Non-technical users may prefer CookieYes for its automation, while developers might opt for Klaro or COOKiES for customization.
• Third-Party Integrations: If your site uses tools like Google Analytics or Facebook Pixel, COOKiES and Klaro offer robust integration options.
• Multilingual Support: All modules support multilingual sites, but CookieYes and EU Cookie Compliance excel in global audience targeting.
• Maintenance and Support: Actively maintained modules like Klaro, EU Cookie Compliance, and CookieYes are safer bets for long-term use. CookieConsent’s lack of stable releases is a concern.
• Performance: Lightweight options like Klaro and Simple Klaro minimize performance impact, while CookieYes’s external service may introduce slight overhead.

Comparison Table: Drupal Cookie Consent Modules

Feature Klaro COOKiES CookieYes EU Cookie Compliance Simple Klaro CookieConsent GDPR Compliance Yes Yes Yes Yes Yes Partial CCPA Compliance Partial Partial Yes Partial Partial No Customizable Banner Yes Yes Yes Yes Yes Limited Multilingual Support Yes Yes Yes Yes Yes No Geo-targeting No No Yes Yes (with add-ons) No No Automatic Cookie Scanning No No Yes No No No Blocks Non-Essential Scripts Yes Yes Yes Yes Yes No Consent Logging No No Yes No No No Third-Party Integration Yes Yes Yes Limited Limited No Accessibility Compliance Partial Yes Yes Partial Partial No Google Consent Mode Support No No Yes No No No IAB TCF Support No No Yes No No No Ease of Setup Moderate Moderate Easy Easy Advanced Easy Actively Maintained Yes Yes Yes Yes (Stable focus) Yes No Drupal Versions Supported 8/9/10 8/9 8/9/10 7/8/9/10 7/8/9 8/9/10 Free/Open-Source Yes Yes No (Service) Yes Yes Yes

Conclusion

Choosing the right Drupal cookie consent module depends on your site’s specific needs:

• Klaro is ideal for developers seeking a lightweight, open-source solution with granular control and active development.
• COOKiES excels for sites with multiple third-party integrations and a focus on accessibility.
• CookieYes is perfect for non-technical users needing automated scanning and comprehensive compliance features, though it’s a paid service.
• EU Cookie Compliance remains a reliable, mature option for EU-focused sites, but its maintainers suggest transitioning to Klaro for modern setups.
• Simple Klaro suits small sites with basic needs and developers comfortable with manual configuration.
• CookieConsent is outdated and best avoided for modern compliance requirements.

For most Drupal sites, Klaro or CookieYes are the top contenders due to their balance of features, compliance, and maintenance. If budget is a constraint, Klaro’s open-source nature makes it a strong choice, while CookieYes is worth the investment for automated compliance and peace of mind.

Note: Always verify compliance with legal experts, as module features may not cover all regulatory nuances.

Cookie Drupal Planet Drupal

Share this

Copied to clipboard

Add new comment

Making Regression Testing Work for... QA Testing duncan Mon, 09/06/2025 - 15:46 Why Regression Testing Matters Every time a new version of your website is prepared for deployment, whether it’s a minor update, a major upgrade, or a bug fix, there’s a risk that something unexpected breaks. That’s where regression testing comes in. Regression testing is a repeatable suite of checks designed to ensure that recent changes haven't unintentionally…