Systems | Development | Analytics | API | Testing

We’re excited to introduce two powerful new capabilities in Xray: AI Test Case Generation and AI Test Model Generation for Xray Enterprise, powered by Sembi IQ — Sembi’s AI platform built to help QA, development, and security teams deliver better software, faster. With these new features, Xray brings intelligence directly into the testing process, making it faster to design tests, easier to ensure coverage, more secure by design, and always guided by human expertise.

Refreshing a page might seem simple. But when you're working with dynamic applications, forms, or session-sensitive flows, the way you refresh matters. A mis-timed reload can cause flaky results or unexpected behavior in your automation scripts. That’s why knowing how to refresh the page in Selenium is essential. There are multiple ways to reload a page, and each has its own use case. Some simulate user behavior. Others trigger a full re-render of the DOM.

Modern websites open new tabs for all sorts of reasons. A login button can trigger a third-party auth flow, or a “Pay Now” link can open a secure payment gateway. When automating such flows, your test script must keep up. That’s where understanding how to switch tabs in Selenium with Python becomes essential. If your script keeps running in the old tab, it’ll miss everything happening in the new one.

Hey everyone, Launch days are always exciting, and today, I couldn’t be happier to share something we’ve been working hard on: the MCP Server in Katalon Studio. This isn’t just another update. It’s a milestone for StudioAssist and for all of you who are looking to move faster with AI. With this release, we evolved StudioAssist from simply answering your questions to becoming your Agentic AI assistant. That means it doesn’t just tell you what to do.

Did you know that nearly 35% of software bugs detected in late stages could have been caught at the build stage—if a proper smoke test were in place? What’s worse: those bugs often cost 10× more to fix later. If you’re a business owner or DevOps lead pushing for faster releases, you can’t afford to skip basic checks.

Building distributed systems is a huge undertaking, but the complexity doesn’t end once your application or platform is “production ready.” Keeping these systems online and operational through cloud region outages, a network partition, or just scheduled maintenance is a constant challenge. The bottom line: you don’t want data pipelines for essential business services, customer-facing products, or enterprise data platforms to go dark.

As the adoption of real-time data processing accelerates, the ability to scale stream processing applications to handle high-volume traffic is paramount. Apache Kafka, the de facto standard for distributed event streaming, provides a powerful and scalable library in Kafka Streams for building such applications. Scaling a Kafka Streams application effectively involves a multi-faceted approach that encompasses architectural design, configuration tuning, and diligent monitoring.

Jetpack Compose is Android’s modern UI toolkit. It unifies and simplifies the experience by consolidating state and logic in the rendering with a more declarative approach. Among its most notable features is a powerful animation framework that helps developers create fluid and performant animations with ease. Jetpack Compose allows you to easily inject animations into your UI, which is a great way of providing visual feedback and enhancing interactions that directly affect the user experience.

Reading a lot of code from very senior engineers is probably one of the best ways to level up as a Ruby on Rails developer. By doing so, we can learn new tips and techniques that we can reuse in our jobs. Thanks to open source, we can read code written by the best developers from all over the world, and for free! However, reading code from a Ruby gem or a Rails engine for the first time without being guided can be daunting. There are so many files; how do we even know where to start?

In part one of this series, we explored how Angular Signals shift the reactive model away from the RxJS-centric approach we’ve relied on for years. We walked through the core API signal(), computed(), and effect() primitives, and demonstrated how they simplify state management by removing the need for subscriptions, teardown logic, and deeply nested observables. We also introduced a minimalist CartService that held cart items in a private signal and exposed a computed total price.