Gatling.io

Posted on Nov 24 • Originally published at gatling.io

From browser journeys to Gatling tests in minutes: introducing Gatling Studio

#testing

creating your first load test shouldn’t feel like a project on its own. But for many teams, it still does.

You start with a blank script, try to map user actions to HTTP calls, dig through HAR files, and piece together a scenario that “feels” realistic. It’s slow, manual, and easy to get wrong.

Gatling Studio changes that.

It turns a real browser session into clean, editable Gatling code in minutes, so you can focus on performance—not reverse-engineering traffic.

Studio is the fastest way to move from “I want to test this flow” to runnable, version-controlled, production-ready load tests.

What is Gatling Studio?

Gatling Studio is a desktop application that captures real browser traffic, filters out noise, and generates clean Gatling test-as-code projects you can edit, version, and run locally or at scale.

Why we built Gatling Studio

Teams adopting test-as-code love the flexibility and power of Gatling. But the first mile of test creation often takes too much time:

Capturing user behavior by hand
Cleaning out noise
Defining realistic timing
Structuring requests into a readable scenario

For teams new to load testing—or teams who need to scale test creation across QA, Dev, and SRE—this work becomes a bottleneck.

Gatling Studio removes it.

You record a real browser journey, refine it, generate code, and export a complete Gatling project to your IDE. No scripting guesswork. No manual cleanup.

Studio is part of Gatling Enterprise Edition, and it’s designed for organizations that want to industrialize load testing across teams while keeping full test-as-code control.

The fastest path from browser flow to load test code

Gatling Studio gives you a single, streamlined path:

Record
Refine
Generate
Export

Let’s break each one down.

Record real browser traffic with one click

Studio launches a controlled browser session and captures every interaction:

Requests and responses
Headers and cookies
Timings and pauses
User navigation and workflow context

You can also import an existing HAR file if your QA or frontend teams already recorded one.

This gives you a true picture of real user behavior, not an approximation of it.

Clean up and refine your scenario

Raw browser traces include a lot of noise: static assets, analytics calls, third-party trackers, fonts, ads, and more.

Studio filters that for you.

You can refine by:

domain
request type
relevance to the user journey

This leaves you with a clear scenario that represents what matters: the functional path and load you actually want to test.

Generate clean Gatling code you can trust

With one click, Studio turns your refined flow into high-quality Gatling code:

Grouped requests and clear scenario structure
Realistic pauses and timings
Complete HTTP calls with parameters
Java + Maven project layout, ready for version control

Because Studio builds code, not opaque test files, you keep full ownership of your load tests. You can extend them, review them, and integrate them into your CI/CD pipelines—just like any other part of your codebase.

This aligns with Gatling’s core philosophy: test as code.

Export to your IDE and run anywhere

Studio exports a full Gatling project you can:

Open in IntelliJ, VS Code, or your preferred IDE
Store in Git
Customize for different environments
Run locally with Gatling Community Version
Scale massively with Gatling Enterprise Edition

Exporting is instant. From there, your workflow remains the same as any test-as-code simulation you write by hand.

What teams gain by using Gatling Studio

Faster test creation

No more blank scripts or manual correlation. Studio gives you a ready-to-use baseline in minutes.

Realistic user journeys

Tests reflect true behavior—timings, sequence, dependencies, and all.

Lower onboarding cost

QA, backend, frontend, and SRE teams can generate tests without deep scripting knowledge.

Cleaner, more maintainable tests

Generated scenarios follow Gatling best practices and produce readable code you can iterate on.

A smoother path to Gatling Enterprise Edition

Studio is built to work inside Enterprise Edition.

It fits into your existing pipelines, governance, and team workflows ◆ CI/CD plugins, access control, private locations, advanced dashboards, and configuration-as-code.

How Gatling Studio fits into a modern load testing stack

Gatling Studio is more than a recorder. It’s part of a broader flow that helps teams standardize performance testing across development, QA, and operations.

With Studio, you can:

Build test scenarios quickly
Store them in Git
Automate them in CI/CD
Scale them globally across cloud locations
Compare results across runs and track regressions
Gate releases based on SLAs

Combined with Gatling Enterprise Edition’s analytics—live dashboards, TLS/DNS/TCP breakdowns, multiple-run comparison, and run trends—Studio becomes the starting point of an industrialized performance testing practice.

Try it live: 20-minute demo

If you want to see the full workflow—from recording a browser session to generating production-ready code—join our next live demo.

DEV Community