Systems | Development | Analytics | API | Testing

If you’ve been following Kong, you know that Kong was the first in the API platform space to introduce an enterprise-grade AI Gateway for LLM workloads. Today, we’ve also introduced a new enterprise-grade MCP Gateway to ensure that you can roll out production-ready MCP deployments. But we are focused on more than just the Gateway. Today, we’re excited to announce additional MCP workflow support in the Konnect Developer Portal and a brand new MCP integration solution, the MCP Composer.

With software applications growing increasingly complex, the way we test them to guarantee reliability and security must also increase accordingly. Among the many types of testing available, Grey Box Testing stands out as a hybrid method that presents us with a balanced perspective of insights from both black box and white box testing. It doesn`t matter if you’re a developer, QA engineer, or someone new to testing; grey box testing is important to everyone in today’s technological landscape.

The term “Behavior Driven Development”, or BDD, is an umbrella term for a wide variety of techniques. The general principles of BDD include reframing tests as descriptions of system behavior – “when I do one thing, I should see this result”. Historically, those descriptions were the output of a computer program. Over time, the uses of BDD shifted toward Gherkin, an English-like but precise language.

In our rapidly-changing digital world, companies are always searching for tools to enable automation for testing. Due to the increase in popularity of test automation, it is important to understand the pricing for testing tools. Whether you’re selecting a platform to help you simplify your QA process or determining how much to invest in test automation, pricing is an important factor.

This is the eighth post in a series about reasons to attend API Summit 2025. Check out the previous post here. The first time you push an API to production, you’re excited it’s finally live. You’re relieved that you can move on to your next big project. You’re also nervous. You’ve tested as much as you thought you should, but somewhere in the back of your mind is a whisper of, “What if I missed something? What if the commits are messy?

In engineering, we talk a lot about technical debt — the shortcuts and compromises made in code that pile up over time. But there’s another kind of debt that’s just as dangerous and far more invisible: QA debt. QA debt is what happens when testing isn’t given the same attention as features, architecture, or performance. It’s the accumulation of missed edge cases, outdated test suites, incomplete automation, or skipped regression checks.

Whether for frontend or backend, testing is a key aspect of building trustworthy JavaScript applications. For example, when writing code that relies on external modules or services such as APIs, databases, or configuration providers, mocking can allow for a more isolated testing structure without those real dependencies. If you are using Jest, one of the most popular JavaScript testing frameworks, then you may have seen the term mock.

Disclaimer: All of the opinions stated in this blog are my own and do not represent official Gartner opinions on the API Management and Integration markets or the Magic Quadrant report itself.