From click-through to load test with Playwright and Gatling
You can now build a Gatling load test by browsing your app. Walk your user journey in a Playwright browser, and your AI coding agent turns the recording into a correlated Gatling test that replays it. The first script has always been the slowest part of load testing. You dig through the browser's network tab, work out which API calls matter, and chain IDs and tokens by hand. A recorder speeds up…
You can transform a Playwright browser journey into a Gatling load test by using an AI coding agent. The agent records your user journey in a Playwright browser, then converts that recording into a Gatling test. This saves time compared to manually scripting the test. The agent handles dynamic values like IDs and tokens automatically, so the test stays valid even if the data changes.
It also replays the API traffic, allowing up to 60,000 concurrent virtual users on a single load generator. However, the test does not measure front-end rendering or session data, so you should record with a test account. To use it, you'll need a Java 11-25 runtime, Node.js 24+, the coding agent (Claude Code), and the Gatling AI extensions plugin.
Install the Playwright CLI and the skill for Claude Code, then follow the prompts to create your Gatling test. The agent writes the test in a Gatling Java/Maven project, runs it locally, and can deploy it to Gatling Enterprise for larger-scale testing.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
