Systems | Development | Analytics | API | Testing

Our goal with the Tricentis blog is to distill insights that help QA professionals navigate the massive, AI-driven transformation happening across the software delivery landscape. To that end, I reached out to experts across Tricentis, from product and services to marketing and strategy, to hear what they’re really thinking about AI in QA right now. This group brings decades of experience building testing products, guiding enterprise transformations, and shaping how organizations adopt AI.

70% of teams are already integrating generative AI tools into their daily workflows, according to our 2025 State of Game Technology Report. Now more than ever, teams are looking to connect their AI tools to the services and applications they rely on to get work done. To address this issue, the industry has begun to standardize using the Model Context Protocol (MCP) to connect their existing tools and LLMs like Claude, GPT, and Gemini.

Modern AI applications are no longer just about sending prompts to an LLM and returning text. As soon as AI systems need to interact with real business data, internal APIs, or operational workflows, the problem becomes one of orchestration, security, and control. The challenge is to build secure AI agents without embedding fragile logic or exposing sensitive systems directly to a model. This is where a layered architecture using Volcano SDK, DataKit, and Kong MCP Proxy becomes compelling.

AI transforms CI/CD testing from reactive bug detection into proactive quality assurance that accelerates release cycles while improving software reliability. Start embedding AI into your testing workflows now because teams that wait will struggle to match the velocity of competitors who already have. Continuous integration and continuous deployment pipelines have become the backbone of modern software delivery.

A customer recently shared their debugging workflow with me. When an error shows up in Honeybadger, they import it to Linear, manually add context about where to look in the codebase, then assign GitHub Copilot to investigate. It works, but they asked a good question: could Copilot just access Honeybadger directly? The answer is yes—and it's easier than I expected.