getting started with performance.md


version: "2026" language: "en"

Getting started with Go

How do I record my first test in Go?

If you haven't already installed and configured a proxy extension, do that first.

Once that is done, then:

  1. Open Go in Chrome or Edge.

  2. Create a Sequence by clicking on the green "+" icon at the top of the file explorer.

  3. Click Record inside your newly created Sequence.

  4. Configure the fields in the Start recording window.

  5. Before clicking "Start recording", enable the Proxy Extension in your browser.

  6. Perform your actions in the target app (web, mobile, or desktop).

  7. Return to Go and click Stop.

You will see that Go has captured network calls and display them as steps you can preview or edit.


Why do I need to install a certificate and proxy?

Go records HTTPS traffic through a local proxy.

After setup, you just toggle the proxy on/off; no local installs beyond that.


How does Go work technically?

Go records network traffic (HTTP/HTTPS), parameterizes it, and replays it at scale using automatically provisioned cloud agents.

No local setup is required beyond a proxy extension and a one-time proxy certificate for recording.


What's the difference between a Sequence and a Timeline ?


How do I reuse a Leapwork Flow flow in Go?

  1. Run the Leapwork flow once while Go's recorder is active.

  2. Go captures the underlying network traffic automatically.

  3. Stop the recording.

  4. It becomes a Sequence ready for load testing.

This allows you to scale an existing functional test into a performance test instantly.


Can I test authenticated logins (e.g., Azure AD or MFA)?

Yes. All you need to do is add AD users under Data Items.

Go handles cookie refreshes and MFA tokens automatically during long runs, so each virtual user behaves as a real, logged-in user.


How do I verify that my recording works before scaling it up?

Use Preview Run inside the Sequence.

This replays the flow once (or a few times) to confirm endpoints and authentication are valid before orchestrating it in a Timeline.

How can I see what happened during a run?

After a run: