AI TEST GENERATION
Browse your app. AI writes the Gatling load test.
Browse your site in a real browser and name each step. Your coding agent records the requests, attributes them to your steps, and generates a working Gatling test that mirrors your journey.
WORKS IN YOUR AI CODING AGENT


AGENTIC TEST CODING
Your first load test, written by your AI agent in one session
Walk the journey once. Your coding agent maps the traffic, correlates every ID and writes a Gatling test you can run right away. No requests to copy by hand, no recorder script to fix.
WHY IT MATTERS
Simply browse with your coding agent
No scripting, no recorder setup, no correlation by hand. Your agent turns the journey you walk into a load test.
HOW IT WORKS
You browse, AI does the rest.
Playwright to Gatling runs on Gatling's AI skills and MCP server, inside your coding agent. You walk the journey and name each step. The AI records the traffic, maps every request, correlates dynamic values and writes the Gatling test.
Browse and name each step
Before each action, post starting: <step name>. The agent timestamps it and confirms, then you click through the journey like a real user. Say done when you are finished. There is no timeout between steps.
AI writes a correlated Gatling test
The AI keeps the calls to your API, maps each one to the step you named and turns every step into a Gatling group. IDs and tokens are extracted from responses and reused, and checks follow your step names, like an expected 401 on an unauthenticated checkout.
It runs on the first try
The steps run in the order you walked them. The agent runs the Gatling test once locally with the Maven wrapper, so you know it replays before you scale it up.
Scale it on Gatling Enterprise
One more prompt and the agent writes the configuration as code, packages the project, starts the run on Gatling Enterprise and returns the link to the live report.
EVERY WAY TO CREATE A TEST
Create Gatling tests the way your team works
Write them as code, record them, build them in the UI, or let AI write and migrate them for you. Pick the path that fits each team and each test.
FAQ
Questions about AI test generation with Playwright
Is this an AI feature?
Yes. Your coding agent uses Gatling's AI skills and MCP server to analyze the recorded traffic, correlate dynamic values and generate the Gatling test. You stay in control: you name every step, ambiguous requests are flagged to you, and the output is plain Java code you can review.
Which coding agents does it work with, and what do I need?
Coding agents that support MCP servers and skills, including Claude Code, Cursor, Codex, Windsurf and Antigravity. You also need a 64-bit OpenJDK LTS from 11 to 25. Maven is optional: the project ships with the Maven Wrapper.
What does the recording capture?
The recording captures the traffic of your session, so use a test account and review the discovery folder before committing it. Only calls to the API base URL set in the prompt end up in the Gatling test.
Your next load test is one browsing session away
Browse your app, name each step, and let AI write the Gatling test. See it built live on December 10.
Need technical references and tutorials?
Minimal features, for local use only








