Skip to content

Commit 5fb8a96

Browse files
authored
Merge pull request #1965 from surishubham/main
Merge pull request #1964 from sakshamarora-arch/stage
2 parents 671a169 + ce5538a commit 5fb8a96

10 files changed

+369
-15
lines changed
49.4 KB
Loading
49.2 KB
Loading
49.9 KB
Loading
50 KB
Loading
49.2 KB
Loading

docs/assistive-touch-on-real-ios-devices.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,11 +47,12 @@ import TabItem from '@theme/TabItem';
4747
}}
4848
></script>
4949

50-
> To enable it for your organization, please contact us via <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24×7 chat support**</span> or you can also drop a mail to **[email protected]**.<br />
51-
5250
LambdaTest's **Assistive Touch** feature enables you to perform key system-level actions directly from the testing toolbar during manual sessions on real iPhones and iPads.
5351
This allows you to replicate gestures such as going to the Home Screen, opening the Notification Center, taking screenshots, and more without relying on physical device buttons or gestures.
5452

53+
> To enable it for your organization, please contact us via <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24×7 chat support**</span> or you can also drop a mail to **[email protected]**.<br />
54+
55+
5556
## Use Cases
5657

5758
- Navigate to the Home Screen after completing a flow (e.g., logout, relaunch).
Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
---
2+
3+
id: network-configurations-in-browser
4+
title: Network Configurations in Browser Live
5+
sidebar_label: Network Configurations
6+
description: Learn how to configure and capture HTTP/S traffic on real devices during manual testing in Browser Live, with options for content capture and domain filtering.
7+
keywords:
8+
- lambdatest manual testing
9+
- network logs
10+
- mitm proxy
11+
- http traffic capture
12+
- domain filtering
13+
- network configurations
14+
url: https://www.lambdatest.com/support/docs/network-configurations-in-browser/
15+
site_name: LambdaTest
16+
slug: browser-network-configurations/
17+
18+
---
19+
20+
# Network Logs and Configurations in real devices
21+
22+
Network logs record every network interaction during your test session, from API calls and page requests to server responses and load times. These logs are stored in HAR format, giving you a complete snapshot of **network performance** for each run. By reviewing this data, you can identify slow endpoints, troubleshoot failed requests, and validate that your app communicates with the right services—all without leaving your testing workflow.
23+
24+
On LambdaTest, you can enable **network configurations** to capture and analyze this traffic in real time on real devices. With flexible options such as content capture and domain-based filtering, you can focus on the most relevant network interactions while reducing noise from unrelated requests. This helps ensure faster debugging, clearer insights, and more efficient test runs.
25+
26+
27+
> To enable it for your organization, please contact us via <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24×7 chat support**</span> or you can also drop a mail to **[email protected]**.<br />
28+
29+
---
30+
31+
### Use cases
32+
33+
- **Debug API calls** by viewing HTTP/S request and response data directly from real device sessions.
34+
- **Verify backend integration** by checking if calls are made to the correct endpoints.
35+
- **Filter noise** by including/excluding specific hosts.
36+
- **Reproduce production issues** that depend on specific network conditions or API behaviors.
37+
38+
---
39+
40+
## Enabling Network Configuration
41+
42+
### Step 1: Access App Testing
43+
44+
Log into your LambdaTest dashboard and navigate to Real Devices > App Testing.
45+
46+
### Step 2: Select your device or browser
47+
48+
Choose a real Android or iOS device, upload your app (APK/IPA), or open a browser URL.
49+
50+
51+
### Step 3: Configure network log options
52+
53+
Run your app. In the network logs for your device, open the **Configuration Options** slider and select the options you want to apply for your current session.
54+
![Enable network logs](../assets/images/real-device-app-testing/Network-RD/Network-window-o.png)
55+
56+
---
57+
58+
### Configuration Options
59+
60+
| Setting | Type | Default | Description |
61+
|-----------------------------|------------------------------|----------|--------------------------------------------------------------------------------------------------------------|
62+
| Capture Content | Toggle | Enabled | Captures the full response body of network requests in the DevTools Response tab. Disable if only headers or metadata are needed. |
63+
| Include specific domains | Text input (comma-separated domains) | Empty | Capture network requests only for the specified domains. |
64+
| Exclude specific domains | Text input (comma-separated domains) | Empty | Exclude network requests to the specified domains. |
65+
66+
---
67+
68+
## Available configuration options
69+
70+
71+
### **Include specific domains**:
72+
Use this to capture logs only for network requests to specified domains. Enable the toggle and add the domains separated by commas, as shown below.
73+
![Include hosts for network logs](../assets/images/real-device-app-testing/Network-RD/Network_Include_Ho.png)
74+
75+
### **Capture content**:
76+
Use this option to capture or exclude response content. This is off by default but can be enabled if needed, as shown below.
77+
![Disable content capture](../assets/images/real-device-app-testing/Network-RD/Network_disable_cont.png)
78+
79+
### **Exclude specific domains**:
80+
Use this to exclude certain domains from network logs. This works similarly to **Include specific domains**. If both options are enabled, **Exclude specific domains** takes precedence.
81+
![Exclude hosts from network logs](../assets/images/real-device-app-testing/Network-RD/Network_Log_excl.png)
82+
83+
84+
---
85+
86+
## Best practices & tips
87+
88+
- Exclude noisy domains to reduce clutter in your logs.
89+
- Use the include list to focus on relevant domains.
90+
- Avoid broad patterns that may capture excessive traffic.
91+
- Save your settings for reuse in future sessions.
92+
93+
---
94+
95+
:::info
96+
- Available only on **Pro Plans** for manual testing.
97+
- Apps from the App Store or Play Store may not support network capture.
98+
- Certificate-pinned apps may fail unless pinned hosts are excluded.
99+
::
Lines changed: 95 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,95 @@
1+
---
2+
id: network-configurations-in-real-devices
3+
title: Network Configurations in App Live
4+
sidebar_label: Network Configurations
5+
description: Learn how to configure and capture HTTP/S traffic on real devices during manual testing in App Live & Browser Live, with options for content capture and domain filtering.
6+
keywords:
7+
- lambdatest manual testing
8+
- network logs
9+
- mitm proxy
10+
- http traffic capture
11+
- domain filtering
12+
- network configurations
13+
url: https://www.lambdatest.com/support/docs/network-configurations-in-real-devices/
14+
site_name: LambdaTest
15+
slug: network-configurations-in-real-devices/
16+
---
17+
18+
# Network Logs and Configurations in real devices
19+
20+
Network logs record every network interaction during your test session, from API calls and page requests to server responses and load times. These logs are stored in HAR format, giving you a complete snapshot of **network performance** for each run. By reviewing this data, you can identify slow endpoints, troubleshoot failed requests, and validate that your app communicates with the right services—all without leaving your testing workflow.
21+
22+
On LambdaTest, you can enable **network configurations** to capture and analyze this traffic in real time on real devices. With flexible options such as content capture and domain-based filtering, you can focus on the most relevant network interactions while reducing noise from unrelated requests. This helps ensure faster debugging, clearer insights, and more efficient test runs.
23+
24+
25+
> To enable it for your organization, please contact us via <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24×7 chat support**</span> or you can also drop a mail to **[email protected]**.<br />
26+
27+
---
28+
29+
### Use cases
30+
31+
- **Debug API calls** by viewing HTTP/S request and response data directly from real device sessions.
32+
- **Verify backend integration** by checking if calls are made to the correct endpoints.
33+
- **Filter noise** by including/excluding specific hosts.
34+
- **Reproduce production issues** that depend on specific network conditions or API behaviors.
35+
36+
---
37+
38+
## Enabling Network Configuration
39+
40+
### Step 1: Access App Testing
41+
42+
Log into your LambdaTest dashboard and navigate to Real Devices > App Testing.
43+
44+
### Step 2: Select your device or browser
45+
46+
Choose a real Android or iOS device, upload your app (APK/IPA), or open a browser URL.
47+
48+
49+
### Step 3: Configure network log options
50+
51+
Run your app. In the network logs for your device, open the **Configuration Options** slider and select the options you want to apply for your current session.
52+
![Enable network logs](../assets/images/real-device-app-testing/Network-RD/Network-window-o.png)
53+
54+
---
55+
56+
### Configuration Options
57+
58+
| Setting | Type | Default | Description |
59+
|-----------------------------|------------------------------|----------|--------------------------------------------------------------------------------------------------------------|
60+
| Capture Content | Toggle | Enabled | Captures the full response body of network requests in the DevTools Response tab. Disable if only headers or metadata are needed. |
61+
| Include specific domains | Text input (comma-separated domains) | Empty | Capture network requests only for the specified domains. |
62+
| Exclude specific domains | Text input (comma-separated domains) | Empty | Exclude network requests to the specified domains. |
63+
64+
---
65+
66+
## Available configuration options
67+
68+
69+
### **Include specific domains**:
70+
Use this to capture logs only for network requests to specified domains. Enable the toggle and add the domains separated by commas, as shown below.
71+
![Include hosts for network logs](../assets/images/real-device-app-testing/Network-RD/Network_Include_Ho.png)
72+
73+
### **Capture content**:
74+
Use this option to capture or exclude response content. This is off by default but can be enabled if needed, as shown below.
75+
![Disable content capture](../assets/images/real-device-app-testing/Network-RD/Network_disable_cont.png)
76+
77+
### **Exclude specific domains**:
78+
Use this to exclude certain domains from network logs. This works similarly to **Include specific domains**. If both options are enabled, **Exclude specific domains** takes precedence.
79+
![Exclude hosts from network logs](../assets/images/real-device-app-testing/Network-RD/Network_Log_excl.png)
80+
---
81+
82+
## Best practices & tips
83+
84+
- Exclude noisy domains to reduce clutter in your logs.
85+
- Use the include list to focus on relevant domains.
86+
- Avoid broad patterns that may capture excessive traffic.
87+
- Save your settings for reuse in future sessions.
88+
89+
---
90+
91+
:::info
92+
- Available only on **Pro Plans** for manual testing.
93+
- Apps from the App Store or Play Store may not support network capture.
94+
- Certificate-pinned apps may fail unless pinned hosts are excluded.
95+
::

docs/network-configurations.md

Lines changed: 156 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,156 @@
1+
---
2+
id: network-configurations
3+
title: Network Configurations in Automation Tests
4+
sidebar_label: Network Configurations
5+
description: Learn how to configure and capture HTTP/S traffic during automation testing on LambdaTest Real Devices.
6+
keywords:
7+
- lambdatest automation
8+
- appium network logs
9+
- espresso network logs
10+
- xcuitest network logs
11+
- mitm proxy
12+
- http traffic capture
13+
- domain filtering automation
14+
url: https://www.lambdatest.com/support/docs/network-configurations/
15+
site_name: LambdaTest
16+
slug: network-configurations/
17+
---
18+
19+
import CodeBlock from '@theme/CodeBlock';
20+
import Tabs from '@theme/Tabs';
21+
import TabItem from '@theme/TabItem';
22+
23+
# Network Logs and Configurations
24+
25+
Network logs record every network interaction during your test session, from API calls and page requests to server responses and load times. These logs are stored in HAR format, giving you a complete snapshot of **network performance** for each run. By reviewing this data, you can identify slow endpoints, troubleshoot failed requests, and validate that your app communicates with the right services—all without leaving your testing workflow.
26+
27+
On LambdaTest, you can enable **network configurations** to capture and analyze this traffic in real time on real devices. With flexible options such as content capture and domain-based filtering, you can focus on the most relevant network interactions while reducing noise from unrelated requests. This helps ensure faster debugging, clearer insights, and more efficient test runs.
28+
29+
> To enable it for your organization, please contact us via <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24×7 chat support**</span> or you can also drop a mail to **[email protected]**.<br />
30+
31+
---
32+
33+
## Use Cases
34+
35+
36+
- **Debug API calls** by viewing HTTP/S request and response data directly from real device sessions.
37+
- **Verify backend integration** by checking if calls are made to the correct endpoints.
38+
- **Filter noise** by including/excluding specific hosts.
39+
- **Reproduce production issues** that depend on specific network conditions or API behaviors.
40+
41+
42+
43+
---
44+
45+
## Capabilities
46+
47+
| Capability | Type | Default | Description |
48+
|-----------------------------|------------------------|---------|--------------------------------------------------------------|
49+
| **network** | Boolean | true | Enables network logs for the session. |
50+
51+
---
52+
53+
## Network Configuration Settings
54+
To enable the following you would need to pass them under `networkLogsOptions` Capability.
55+
56+
| Network Configurations Capability | Type | Default | Description |
57+
|-----------------------------|------------------------|---------|--------------------------------------------------------------|
58+
| **captureContent** | Boolean | true | Captures the response body in network logs. |
59+
| **networkLogsExcludeHosts** | String | None | Hosts to exclude from network logs. |
60+
| **networkLogsIncludeHosts** | String | None | Only capture network logs for these hosts; all others will be excluded. |
61+
62+
63+
:::info
64+
- `networkLogsExcludeHosts` and `networkLogsIncludeHosts` are mutually exclusive. If both are set, **IncludeHosts** takes precedence.
65+
:::
66+
67+
---
68+
## Managing Certificate Pinning in Network Logs
69+
70+
Some mobile apps add an extra layer of security by using **certificate pinning** — a process where the app is hard-coded to trust only a specific certificate or public key for certain hosts. This means that whenever the app communicates with those hosts, it **verifies the server’s certificate** against its pinned copy before allowing the connection.
71+
72+
When you enable **network logging** on LambdaTest, traffic passes through a **secure proxy** so requests and responses can be captured. For **certificate-pinned hosts**, this interception may cause the connection to fail because the certificate no longer matches exactly. To avoid such issues, you can exclude pinned hosts from being proxied by adding them to the `networkLogsExcludeHosts` capability. This ensures your tests run smoothly without breaking **secure connections**.
73+
74+
---
75+
## Network Configurations in Automation Test
76+
77+
### Step 1: Upload Your App to LambdaTest
78+
79+
Before enabling network configurations, ensure your app is uploaded to LambdaTest.
80+
81+
1. **Uploading Your App** – Follow the detailed steps in our [Upload Your Application](https://www.lambdatest.com/support/docs/upload-your-application/) guide.
82+
2. Once uploaded, **note the App ID** returned by the API or dashboard.
83+
3. Use this **App ID** in the `"app"` capability in your automation script.
84+
85+
---
86+
87+
### Step 2: Add Desired Capabilities
88+
89+
<Tabs>
90+
<TabItem value="android" label="Android" default>
91+
<CodeBlock className="language-java">
92+
{`desired_caps = {
93+
"deviceName": "Galaxy S20",
94+
"platformName": "Android",
95+
"platformVersion": "15",
96+
"isRealMobile": True,
97+
"app": "YOUR_APP_ID",
98+
"build": "Sample Build",
99+
"name": "Sample Test",
100+
"network": True,
101+
#highlight-next-line
102+
"networkLogsOptions": {
103+
"captureContent": True,
104+
"networkLogsIncludeHosts": "api.example.com, login.example.com",
105+
"networkLogsExcludeHosts": "analytics.example.com, *.facebook.com"
106+
},
107+
}`}
108+
</CodeBlock>
109+
</TabItem>
110+
111+
<TabItem value="ios" label="iOS">
112+
<CodeBlock className="language-java">
113+
{`desired_caps = {
114+
"deviceName": "iPhone 16",
115+
"platformName": "ios",
116+
"platformVersion": "18",
117+
"isRealMobile": True,
118+
"app": "YOUR_APP_ID",
119+
"build": "Sample Build",
120+
"name": "Sample Test",
121+
"network": True,
122+
#highlight-next-line
123+
"networkLogsOptions": {
124+
"captureContent": True,
125+
"networkLogsIncludeHosts": "api.example.com, login.example.com",
126+
"networkLogsExcludeHosts": "analytics.example.com, *.facebook.com"
127+
},
128+
}`}
129+
</CodeBlock>
130+
</TabItem>
131+
</Tabs>
132+
133+
134+
135+
---
136+
137+
### Step 3: Run Your Test
138+
Execute your test script using your preferred automation framework with the above capabilities.
139+
140+
---
141+
142+
## Best Practices
143+
144+
- **Exclude analytics/tracking domains** to reduce log noise.
145+
- For **certificate-pinned apps**, always add pinned hosts to `networkLogsExcludeHosts`.
146+
- Use **networkLogsIncludeHosts** for focused debugging when investigating specific endpoints.
147+
- Keep `captureContent: false` if you only need headers for performance gains.
148+
149+
---
150+
151+
:::tip
152+
- **Certificate-pinned apps** may fail if pinned hosts are not excluded.
153+
- Available only on **Pro Plan**.
154+
- Certain HTTPS connections (e.g., using custom certificate pinning) cannot be intercepted even with MITM.
155+
156+
:::

0 commit comments

Comments
 (0)