Systems | Development | Analytics | API | Testing

Picture a large-scale grocery and retail chain launching its first online storefront. The setup is complicated: a single online order must travel through an SAP eCommerce platform, multiple payment and loyalty systems, before disappearing into back-end SAP supply chain and ERP apps. The complexity of merging the online and offline business is like a “digital tsunami.” For many SAP enterprises, this sounds familiar.

ABAP turned 43 this year — “an unusually long run,” as Sonja Liénard, head of ABAP platform at SAP, put it in a recent interview. SAP’s proprietary language has been reinvented numerous times, from procedural code to today’s ABAP Cloud, to keep up with market demands. The same cannot be said for ABAP testing. Most SAP teams are deciding what to test the way they did twenty years ago: run the full regression suite and hope it holds.

At Datadog DASH in the spring, the Tricentis NeoLoad team met folks in all types of roles – developers, test engineers, CoE leads, and SREs – and one recurring theme we found was that SREs often didn’t know much about how performance validation happens at their companies. That’s a fair division of labor. Seemingly, the performance team’s work would be related but not mission-critical to the infrastructure team’s. But that’s not entirely true.

Over the past twelve months, something has shifted in how software teams think about quality. Claude Code, Cursor, and Playwright agents have made it genuinely easy to generate functional tests without deep automation expertise. The impact is showing up across two very different kinds of teams: Both paths lead to the same place: tests accumulate without governance, you get coverage without traceability, and there’s automation debt no one owns. But coverage numbers and quality are not the same thing.

For decades, APIs have been the universal handshake of the digital economy. You want data? Call an endpoint. You want to trigger an action? POST a payload. APIs are simple, predictable, and everywhere. But in 2024, Anthropic introduced the Model Context Protocol (MCP), an open standard that dramatically changed how systems speak to one another. MCP enables AI agents to connect with external apps without custom code.

Citizens today compare government digital services to the best experiences they have in the private sector. A missed benefit payment. A tax portal that crashes during filing season. A license renewal that takes weeks instead of minutes. Today, software failures aren’t just IT problems, they’re public trust problems, and many state and local agencies are struggling to deliver digital services quickly, effectively, and consistently.

This fall, Tosca’s suite of AI capabilities will be available for on-premises deployments — giving teams the tools to meet the pressure of the AI era head-on. Customers will gain access to leading AI features, including Agentic Test Automation, AI-powered test creation, MCP connectivity, and AI Workspace, no matter their deployment type or existing infrastructure. AI’s unprecedented development means testing practices that were standard a year ago could already be outdated.

Picture a software testing failure at your company. The consequences range from money lost on weeks of rework to life-threatening catastrophe. These are the errors that keep engineers, their directors, and executives up at night. At some point, those risks came to life in the real world and pushed software teams to develop rigorous testing methodologies. But for some reason, we don’t think about data the same way. We think of it as reliable, durable, and highly unlikely to cause a big issue.

Performance engineering teams are already stretched. AI-accelerated development means more code, more releases, and more pressure on the people responsible for making sure it all holds up. Tricentis NeoLoad 2026.2 is built around a straightforward premise: performance validation must scale to match the pace of delivery, and that means more than just making specialists faster.

Pre-built Oracle test cases have become an increasingly popular resource as organizations look for faster ways to scale test automation. The appeal is understandable: reusable assets and templates can help teams accelerate onboarding and reduce the effort required to begin automation initiatives. Tricentis offers an Oracle test case library as a reference framework rather than an instant, maintenance-free automation solution.