Systems | Development | Analytics | API | Testing

When you operate a digital commerce ecosystem across multiple international borders, processing thousands of concurrent checkout events for over 70 global brands, the standard concept of "QA" completely breaks down. Most corporate discussions treat software validation as a simple pre-release checklist, a final mechanical hurdle before a deployment goes live.

With the release of Xray Cloud 15.0.0, Xray expands its latest AI capabilities with the introduction of AI Test Prioritization, joining two recently released features: Xray's Rovo Test Plan Summarizer and AI-generated Manual Scripts for Test Case Designer, introduced in Xray Cloud 14.0.0. Testing is rarely just about executing test cases. Teams need to understand where risk exists, how testing is progressing, and whether a release is ready to move forward.

Webinar recap: Andy Cotgreave (co-founder, How to Speak Data) and Francois Lopitaux (SVP of Product, ThoughtSpot) on hallucinations, accountability, and what it actually takes to trust AI with your data.

You will still need to solve many last-mile problems to make them production-ready. We can help.

In 2024, two of the largest data platform companies, each with billions in revenue and dedicated AI research teams, invested in building their own foundation models. One spent roughly $10 million training a 132-billion parameter model on 3,072 NVIDIA H100 GPUs. The other released a 480-billion parameter model optimized for enterprise tasks like SQL generation and code. Both achieved strong results within their compute class.

There's a well-worn path to resumable AI chat streams: find the Vercel SDK docs, implement Redis-backed replay, and ship it. For many products, that's the right call. The challenge arises when the product goes further than that. AI customer support tools that handle complex queries over 30-plus seconds. Agents that keep working while the user switches from their laptop to their phone.

The gap between "our logs follow every best practice" and "I can actually find what's wrong, fast" is what I want to write about here. I'll go through the standard checklist first, because it's genuinely worth doing. Then I want to talk about the part that checklist doesn't cover.

In 2006, the TIOBE Index crowned Ruby its Language of the Year for posting the fastest growth rate of anything on the list. Two decades later, it's settled in around - respectable, but a long way down from where it once stood. Ruby went from "the future of programming" to "wait, people still use that?" within a single career. This isn't a eulogy, though - stick around, because Ruby is very much alive, just not where the headlines are looking.

In the first experiment, I wanted a baseline: if an AI coding agent gets the same production signal a human would get, can it fix bugs in a codebase it has never seen? Yes, but only when I gave it better context. With only an alert, the agent passed 51% of the runtime tests. When I added captured traffic, the actual request and response for the failing call, it climbed to 77%. This post is the second pass.

If you have watched a Temporal demo and an n8n demo back to back, the reaction is almost universal: “Wait, aren’t these the same thing?” Both stitch together a sequence of steps. Both retry failures. Both, as of 2026, market themselves around AI agents. On a whiteboard, they look like cousins. They are not. Temporal vs n8n is one of the most common false equivalences in modern engineering, and getting it wrong is expensive in both directions.