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.

This is the sixth and final post in our "Features Sitting Idle" series, where we shine a light on OctoPerf features that are already in your account, ready to save you hours every week. It's a quiet but recurring friction. Teams that test regularly all end up with a preferred report layout. But in practice, that structure is often rebuilt manually after each run, or lost entirely when moving between projects.

The OctoPerf web application is a large Angular workspace: 7,786 TypeScript files, around 381,000 lines of code, 1,166 components and 2,738 test files. We have just taken it from Angular 20 to Angular 22, deleted zone.js, and replaced Karma and Jasmine with Vitest. The interesting part of this story is not the version number. It is that we got the strategy wrong first. We spent months migrating the codebase component by component, drowned in manual regression testing, and still let bugs reach production.

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.

The Internet of Medical Things (IoMT) is growing faster than ever. According to 2026 data from The Business Research Company, the global IoMT market has reached over $124 billion this year and is on track to hit nearly $300 billion by 2030. This growth is happening because healthcare is moving outside hospital walls and into patients' homes through remote monitoring. But for engineering teams, connecting these devices is a massive headache.

As AI rapidly integrates into software development, from code generation to interface review, it promises unmatched efficiency.

A practical definition of the discipline that proves a release is ready to ship, backed by evidence instead of opinion.

Claude Code shipped workflows: reusable, versioned instructions an agent can follow instead of improvising a process from scratch each time. We used that feature to hand Claude Code our entire QA job. Not "write a test case." The whole loop: read the requirement, design the coverage, run it on the platform, file the defect, report back with evidence. The kind of work a QE does in a day, compressed into one skill triggered with a sentence.

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.