A shopper taps “Place Order” on their device. From there, payment, inventory, promotions, and order systems all contribute to what happens next. If one slows down, the shopper may experience a broken next step, even when the storefront itself looks fine. That’s why retail engineering teams need to check both how connected services behave under…
A test suite can quickly grow into a second system your engineers have to maintain. In financial services firms and insurance firms, that work may span customer portals, payment APIs, core platforms, and employee workflows. Teams need to maintain these connections while delivering new features, and sometimes, it can seem like the test suite is…
Bringing three NHS Trusts toward a shared electronic patient record (EPR) is a major undertaking. For BSW Hospitals Group, it also means aligning technology and clinical practice while preparing for a demanding delivery timeline. BSW Group CDIO Jonathan Hinchliffe recently discussed how Leapwork has helped provide testing capacity and quality that his team would otherwise…
When Linus Torvalds released the Linux kernel in 1991, the new, open source operating system was not for the faint of heart. Unless you enjoyed writing custom device drivers, porting applications between platforms and compiling lots and lots of code, you were not poised to become a Linux user in 1991. Even skilled IT professionals…
AI agents are a powerful way to make software tests faster, more efficient, and more scalable. But they can also make the process very expensive. Between token costs, API fees, agents’ CPU and memory consumption, and more, the costs of agentic testing can add up to the point that they exceed the price of testing…
The following post is a first-person account from Leapwork QA Architect Satpal Singh about how Leapwork Play changes the nature of his QA engineering work. Below, Satpal reflects on the nature, joy, necessity, and value of QA engineering based on his experience in the field. He also explains how Leapwork Play elevates the role of the QA…
The following post is a first-person, eyewitness account from Leapwork CTO Rohit Raghuvansi about how adopting Leapwork Play into his QA team’s workflows enabled them to increase new feature deployments from every two weeks to on-demand. Below, Rohit reflects on how aspirations for improving deployment speed led his team to discover firsthand how using Leapwork…
QA teams often say they have reached 80% or 85% automation coverage and are now targeting 90%. It’s easy to see why this number is important. Automation coverage is easy to measure, easy to communicate to leadership, and it shows that the company has made a serious investment in automation. But is automation coverage really…
Say these two phrases out loud: “using AI to test software,” and “testing software that uses AI.” They sound like the same sentence with the words shuffled. In practice, they describe two completely different jobs, and a surprising number of teams are doing the second while thinking they signed up for the first. The gap…
In July 2026, one of the most sophisticated AI companies in the world lost track of its own model, and the story is a near-perfect illustration of the risk every enterprise is now quietly carrying. The short version: an autonomous agent running inside a controlled security-testing environment did exactly what it was told to do:…
