Systems | Development | Analytics | API | Testing

Playwright is a browser automation framework that also ships a built-in HTTP client for API testing. That HTTP client, called APIRequestContext, lets you send requests and assert on responses directly inside a Playwright test – no browser, no separate tool. If your team already uses Playwright for end-to-end browser tests, the API layer requires no separate testing framework. It runs inside the same suite, the same CI job, the same configuration.

I spent the day at NVIDIA thinking I’d be learning about all the newest models and RAM throughput achievements. Instead, a version of the future started to crystallize where AI really is good enough, pervasive and cheap(er). Let me share some of my observations and conclusions.

APIs are the backbone of modern software. They connect microservices, power mobile experiences, and make integrations possible across industries. For all their importance, API testing remains one of the most fragmented, manual, and maintenance-heavy parts of the software development lifecycle (SDLC). So as development accelerates in an AI-disrupted SDLC, application integrity – continuous, measurable assurance that your software just works as intended – becomes harder to maintain, not easier.

AI can now handle the slowest parts of test management, inside Jira. – The Zephyr Agent for Rovo creates test cases and links them to your work items, in the projects where your team already plans and builds. This guide covers how testing is changing in the AI age, what the agent is, where to find it, and how to run your first task.

You've diagnosed the problem. Your agentic AI initiatives are stalling — not because the models are wrong, but because the integration layer underneath them wasn't built for this. Batch data, rigid schemas, fragmented governance, no real-time event delivery. Now the question is: what do you actually build, and how do you build it without tearing down the infrastructure you already have?

If you've been around long enough to remember when iPaaS was the answer to everything, you know the pattern. New paradigms arrive. Someone realizes that wiring it into existing infrastructure is harder than the demos suggested. An integration layer gets built. That layer slowly becomes load-bearing. Eventually, the integration layer becomes the bottleneck. We're at that moment again — except this time, the new paradigm is agentic AI, and the bottleneck is forming faster than usual.

You swapped in a better model. You fine-tuned it. You threw more tokens at the problem. And still — your agents hallucinate, break under load, and deliver answers that were accurate about three hours ago. The model isn't the problem. Gartner recently flagged that up to 40% of enterprise agentic AI initiatives are at risk of failure. Executives see that number and immediately audit their LLM provider. Their infrastructure team. Their prompts.