Systems | Development | Analytics | API | Testing

We’re excited to announce the general availability of Kong Insomnia 11! This release introduces third-party vault integrations for enhanced security, an all-new Git sync experience for more seamless collaboration, and support for multi-tabs to improve efficiency within the Insomnia application. Keep reading to learn more.

When your company deployed its first large language model last quarter, your CTO probably didn't mention you'd need entirely new tools to understand what's happening under the hood. But here we are. AI Observability isn't just another tech buzzword—it's the difference between confidently leveraging AI and crossing your fingers hoping nothing breaks.

When it comes to ensuring software quality, having a well-defined Test Plan and Test Strategy is crucial. As a software developer or QA professional, understanding the differences between these two concepts and how to write a Test Plan or execute a test strategy effectively can significantly improve your testing process.

One method that developers use to submit code modifications for evaluation is known as pull requests (PRs). We discussed the advantages of testing PRs in software development in a previous post but before merging into the main branch, they give team members a chance to talk about the changes, make suggestions, and accept or reject the code. To keep code quality high and make sure that the team reviews all changes, this approach is essential.

In the evolving landscape of software testing, Behavior-Driven Development (BDD) has emerged as a powerful methodology for improving collaboration between technical and non-technical team members. However, the implementation of BDD tools like Gherkin and Cucumber often falls short of their intended purpose. Let's explore how to effectively use these tools and avoid common pitfalls.

Enterprises working in Microsoft Azure need to mask data, and they need to mask it quickly.Yet, it can be difficult to find Azure data masking methods that are both swift and secure. The wrong approach can lead to bottlenecks, compromised analytics quality, and significant regulatory risks.

Hiring a software testing company can be a good way to get more testing done without recruiting expensive, full-time QA engineers. However, through conversations with engineering leaders and developers, we frequently hear complaints about software testing companies bottlenecking release pipelines, missing apparent visual bugs, and highlighting non-issues as bugs.

Shipping high quality apps requires thorough testing, and testing thoroughly requires teams to automate more of their process. Quality isn’t just about testing more – it’s about testing smarter. By optimizing your workflow, you create space to validate every critical part of your application efficiently and reliably. Full-scale quality comes from full-coverage testing.