Getting started with Performance

How do I record my first test in Performance?

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

Once that is done, then:

1. Open Performance 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 Performance and click Stop.

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

Why do I need to install a certificate and proxy?

Performance records HTTPS traffic through a local proxy.

• The certificate allows Performance to decrypt secure traffic (similar to Postman or Fiddler).

• The proxy forwards your actions to Performance’s recorder.

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

How does Performance work technically?

Performance 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?

• A Sequence = one recorded performance, load or API test. This test case can be equivalent to a user journey (e.g., “Create Sales Order” in an ERP system) or a single API endpoint (e.g., “sendStartCheckout”).

• A Timeline = how many users run what Sequences, for how long, from which regions. You can see it as editing a movie with multiple tracks and ramps.

How do I reuse a Leapwork Studio flow in Performance?

1. Run the Leapwork flow once while Performance’s recorder is active.

2. Performance captures the underlying network traffic automatically.

3. Stop the recording.

   1. 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.
Performance 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:

• Open Run Results → view requests, errors, and response times per step.

• Metrics show min / avg / P95 / P99 latencies and requests per second.

• Use AppDex Score to understand user-experience quality (satisfied / tolerable / frustrated).

• The AI Summary at the bottom highlights anomalies and likely causes.