Run Result

This guide introduces you to Run Results in Leapwork Go. Run results show what happened during a performance test run so you can understand behaviour, spot bottlenecks, and decide what to investigate next.

What are Run results?

Run results are the detailed view of a completed or active load test. For every run, Leapwork Go records:

• How many virtual users were active over time
• How response times behaved (including percentiles)
• How many requests were sent and how many failed
• How different assets (groups, sequences, or endpoints) performed

You typically:

1. Start a run from a Timeline.
2. Wait for it to complete or stop it manually.
3. Open the Run results to analyse what happened and confirm the test outcome.

The Run results workspace

If you're new to Leapwork Go, start with the Overview of the Go workspace for a tour of the user interface.

When you open Run results, the workspace shows run‑specific information inside that same layout:

1. Run list: lists timelines that have been run, with status and duration.
2. Run header: shows the selected run, status, starting time, duration, and peak virtual users.
3. Timeline and VU chart: shows how virtual users and response times evolved during the run.
4. Metrics tables show detailed metrics for each asset, such as response times, request counts, and errors.
5. Go AI Insights: shows AI‑generated observations when available.

Run list

On the left side, the run list displays previously executed timelines. Each entry shows key information such as the timeline name, when the run started, its status, and how long it lasted.

This list helps you navigate between runs and compare results over time. For example, you might review how a recent run compares to an earlier one, or quickly check whether a run finished successfully or was stopped early.

Each run typically includes:

• Timeline name
• Start date and time
• Status (such as Finished or Stopped)
• Duration

You can also sort the list (for example, by newest first) to find specific runs more easily.

Run header and summary

At the top of the workspace, the run header focuses on the selected run and provides a quick overview of its key details. It shows the timeline name, run status, start time, total duration, and peak virtual users.

Below this, summary tiles give you a snapshot of important metrics during the run. These include values such as:

• Current virtual users
• Throughput (requests per second)
• Agents in use
• Total sequences executed
• Virtual user minutes (VUM)

Together, the header and tiles help you quickly understand the scale and outcome of the run before diving deeper.

Timeline and virtual user chart

The central chart shows how the run behaved over time. It combines load and performance data so you can see how the system responded as virtual users increased or decreased.

The chart typically shows:

• Virtual user count as a filled area
• Response time as a line
• A time ruler across the bottom

It may also include visual indicators, such as experience bands, to highlight when response times move into less acceptable ranges.

As you move your cursor across the chart, the summary tiles update to reflect metrics at that exact point in time. This makes it easier to connect what you see visually with actual values like throughput and active users.

You can use this chart to confirm that the run followed the expected load pattern and to spot periods where performance changes or becomes unstable.

Overall snapshot metrics

Below the chart, the metrics table shows aggregated statistics for the run. Each row represents an asset from the timeline, such as a group of requests or a specific endpoint.

For each asset, the table includes metrics such as:

• Average response time
• Percentiles (P90, P95, P99)
• Minimum and maximum response times
• Requests per second and total requests
• Error counts and data volume

This table helps you compare different parts of your system, identify slow or failing endpoints, and confirm that key transactions received enough traffic.

For each asset, the table shows:

You can scroll through the table if there are many assets in the run.

Go AI Insights

At the bottom of the Run results workspace, the Go AI Insights panel summarises notable patterns in the run. When insights are available, this panel may highlight things like:

• Sudden changes in response time or throughput.
• Endpoints that behave significantly worse than others.
• Anomalies that might deserve deeper analysis.

Use AI insights as a starting point for analysis. Combine them with what you see in the chart and metrics tables to decide which parts of your system need further investigation.

Run Results PDF/HTML Export

The Run results view now includes PDF and HTML as export options alongside the existing Excel export. After a timeline run completes, you can click the Export dropdown in the top-right corner of the results panel and choose your preferred format.

Available export formats:

• Excel: Tabular data export
• PDF: A formatted report suitable for sharing or archiving
• HTML: A self-contained HTML report that can be opened in any browser

This is useful when you need to share performance run results with stakeholders who don't have access to Leapwork Go, or when you want to archive results in a portable, readable format.

The exported report includes the run summary (status, starting time, total duration, peak VUs), stats, track visualizations, and overall snapshot metrics such as average response time, percentiles (P90, P95, P99), min/max, requests per second, and error counts.

Captured Data tab

When HTTP traffic capture is enabled on a timeline, Run Results displays a Captured Data tab after execution completes.

The tab provides access to the request and response samples collected during the run. From this view, you can search captured traffic, review individual requests, inspect responses, and export captured data for further analysis.