HTTP traffic capture allows you to inspect representative request and response samples collected during a timeline run. This capability helps you investigate failures, analyze application behavior, and review request details without storing all traffic generated during execution.
Capture is configured at the timeline level.
Configure traffic capture
Open the timeline you want to configure and select a capture mode. Leapwork Go supports the following capture modes.
|
Mode |
Description |
|---|---|
|
Off |
No HTTP traffic is captured. |
|
Focused |
Captures a representative set of successful and failed requests. |
|
Error Only |
Captures only requests associated with errors. |
Focused mode automatically keeps the most useful samples: failures are captured by default, repeated identical failures are limited, and the first 3 occurrences of successful samples are retained for relevant request patterns.
Run the timeline
After configuring capture mode, run the timeline as usual. Captured data becomes available when execution completes.
Review captured traffic
Open Run Results and select the Captures tab. The Captures tab provides an overview of captured traffic, including summary metrics and captured samples.You can search and filter the captured data to focus on specific requests, sequences, response codes, or methods.The tab also provides aggregate information about the capture session, including the number of samples collected and execution statistics.
Inspect a capture
Select an individual capture to view request and response details.
Depending on the request, available information may include:
-
Request headers
-
Request payloads
-
Response headers
-
Response payloads
-
HTTP method
-
Response code
-
Capture timestamp
Large response bodies may be truncated to limit storage requirements.
Export captured traffic
Captured traffic can be exported as JSON for further analysis or sharing with other teams.
Exported data preserves the request and response information collected during execution.
Troubleshooting
The Captures tab is empty
Verify that capture is enabled on the timeline. No data is collected when capture mode is disabled.
Fewer samples than expected are displayed
Focused mode intentionally stores a representative sample rather than every request generated during execution.
Response content is truncated
The response exceeded the maximum capture size. Request and response metadata remain available even when the full payload is not stored.