Skip to content

Commit 315de7f

Browse files
authored
Merge pull request #2366 from surishubham/main
stage PRs - 2327, 44, 61, 62
2 parents cb9b8a3 + 1d2f424 commit 315de7f

16 files changed

+125
-34
lines changed
88.4 KB
Loading
88.3 KB
Loading
98.7 KB
Loading
98.4 KB
Loading

docs/apple-pay-auto.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ Currently, the Device Passcode feature in App Automation is enabled on the follo
5555
| Capability | Type | Default | Required / Optional | Description |
5656
|----------------------------|------------|---------|---------------------|---------------------------------------------------------------------------------------------|
5757
| **applePay** | Boolean | true | Mandatory | Enables Apple Pay provisioning including Wallet, Sandbox card, AssistiveTouch, and Passcode on supported real iOS devices. |
58-
| **applePayCardType** | Array | None | Optional | Specify preferred payment networks. Currently, you can choose from four supported cards: ["American Express", "Visa", "MasterCard", "Discover Global Network"].|
58+
| **applePayCardType** | Array | None | Optional | Specify preferred payment networks. Currently, you can choose from four supported cards: ["amex", "visa", "master", "discover"].|
5959

6060
---
6161

@@ -88,7 +88,7 @@ To enable Apple Pay automation, include the following capability in your automat
8888
// highlight-next-line
8989
"applePay": true,
9090
// highlight-next-line
91-
"applePayCardType": ["Visa", "Mastercard"],
91+
"applePayCardType": ["visa", "master"],
9292
}`}
9393
</CodeBlock>
9494
</TabItem>

docs/getting-started-with-xcuitest.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,8 @@ slug: getting-started-with-xcuitest/
1818

1919
import CodeBlock from '@theme/CodeBlock';
2020
import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
21+
import RealDeviceTag from '../src/component/realDevice';
22+
import VirtualDeviceTag from '../src/component/virtualDevice';
2123

2224
<script type="application/ld+json"
2325
dangerouslySetInnerHTML={{ __html: JSON.stringify({
@@ -42,8 +44,8 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
4244
})
4345
}}
4446
></script>
45-
46-
Developed by Apple, XCUITest is a framework for user-interface (UI) testing for iOS applications. It is built on top of XCTest, an integrated test framework in Apple's Xcode IDE. LambdaTest lets you perform automated app testing of your iOS apps using XCUITest across 3000+ real devices and OS combinations.
47+
<RealDeviceTag value="Real Device" /> <VirtualDeviceTag value="Virtual Device" />
48+
Developed by Apple, XCUITest is a framework for user-interface (UI) testing for iOS applications. It is built on top of XCTest, an integrated test framework in Apple's Xcode IDE. LambdaTest lets you perform automated app testing of your iOS apps using XCUITest across 10000+ real devices and OS combinations.
4749

4850
## Prerequisites
4951

@@ -227,6 +229,11 @@ curl --location --request POST 'https://mobile-api.lambdatest.com/framework/v1/x
227229
}'
228230
```
229231

232+
:::info
233+
- For Virtual Devices, both the App file and Test-suite should be in the `Zip format`.
234+
- We need to pass the following capability `isvirtualdevice:true` as well when we are running test for Virtual Devices.
235+
:::
236+
230237
<nav aria-label="breadcrumbs">
231238
<ul className="breadcrumbs">
232239
<li className="breadcrumbs__item">

docs/multi-device-testing.md

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
id: multi-device-testing
3+
title: Multi-Device Testing on Real Devices
4+
sidebar_label: Multi-Device Testing
5+
description: Learn how to test multiple devices simultaneously in a single session on LambdaTest App Live, including setup, workflow, and best practices.
6+
keywords:
7+
- Multi-Device Testing
8+
- App Live
9+
- Real Devices
10+
- Parallel Testing
11+
slug: multi-device-testing/
12+
site_name: LambdaTest
13+
url: https://www.lambdatest.com/support/docs/multi-device-testing/
14+
---
15+
import CodeBlock from '@theme/CodeBlock';
16+
17+
# Multi-Device Testing on Real Devices
18+
19+
**Multi-Device Testing** enables you to run multiple devices simultaneously in a single App Live session, allowing you to validate your application across different devices and OS versions faster and more efficiently. This approach simplifies **cross-device testing** by bringing multiple devices into a single session.
20+
21+
LambdaTest allows you to run **up to 6 devices at a time** within a single session, depending on your plan’s parallel limit. You can choose different applications for each device or test multiple versions of the same app concurrently, all from a single interface, without the need to start separate sessions.
22+
23+
---
24+
25+
## Use Cases
26+
27+
- **Cross-Device Functional Testing**: Validate app functionality across multiple devices simultaneously.
28+
- **UI Consistency Check**: Ensure your app displays correctly on different screen sizes and resolutions.
29+
- **Multi-App Workflow Testing**: Test interactions between multiple apps in a single session.
30+
- **OS Version Verification**: Verify app behavior across different OS versions.
31+
- **Faster Regression Testing**: Reduce testing time by running multiple devices together.
32+
33+
---
34+
35+
## Multi-Device Testing Workflow
36+
37+
### Step 1: Open a Real Device Session
38+
39+
Log in to your [App Live Dashboard](https://accounts.lambdatest.com/dashboard), upload your app, and select a **real device** (Android or iOS).
40+
41+
---
42+
43+
### Step 2: Add Devices Using Multi-Device Option
44+
45+
Once the session is open, click on the **add device** option to add more devices. You can set **up to 6 devices** per session and select the **device and application** for each.
46+
47+
![Multi-Device Selection Placeholder](../assets/images/real-device-app-testing/Multi-device-selector.png)
48+
49+
### Step 3: Apply Multi Device Control Settings
50+
51+
Once devices have been added to the session, you will see an option called **Multi-Device Control**. This feature allows you to apply common actions and settings across all connected devices simultaneously, reducing repetitive steps and ensuring consistent configurations.
52+
53+
![Multi-Device-control-2 Selection Placeholder](../assets/images/real-device-app-testing/Multi-device-2.png)
54+
55+
**Supported Multi-Device Controls**
56+
57+
| **Feature** | **Description** |
58+
| -----------------------| ---------------------------|
59+
|Home | Instantly navigate all devices to the Home screen with a single click |
60+
|Record Session| Start recording on all devices together, instead of initiating recordings individually|
61+
|IP Geolocation| Apply a unified IP geolocation to every device with one click|
62+
|GPS Location| Set a common GPS location across all devices simultaneously |
63+
|Network Throttling|Apply the same network throttling profile to all devices without configuring each device separately|
64+
|Settings|Update global settings such as idle timeout, language and timezone for all devices at once|
65+
66+
67+
:::info
68+
- Currently, **Record Session** downloads are not compatible with QuickTime Player. If you are using macOS, you may need an alternative media player to view the recordings.
69+
:::
70+
71+
---

docs/playwright-android-guide.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,8 +46,11 @@ Playwright is a Node.js library that uses a single API to automate Chromium, Fir
4646

4747
LambdaTest allows you to run Playwright tests across 100+ different android devices. This guide will cover the basics of getting started with Playwright testing on android devices on the LambdaTest platform.
4848

49+
:::tip
50+
- To run test using Playwright android, we currently support versions from `1.20.0` to `1.56.1`
51+
- excluding `1.54.0` which is not supported.
52+
:::
4953

50-
*You can run tests using Playwright versions **1.20.0** to **1.53.2**.*
5154

5255
## Prerequisites
5356
***

docs/regular-expression-xcui.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ site_name: LambdaTest
1212
slug: regular-expression-xcui/
1313
---
1414

15+
import RealDeviceTag from '../src/component/realDevice';
16+
1517
<script type="application/ld+json"
1618
dangerouslySetInnerHTML={{ __html: JSON.stringify({
1719
"@context": "https://schema.org",
@@ -35,6 +37,7 @@ slug: regular-expression-xcui/
3537
})
3638
}}
3739
></script>
40+
<RealDeviceTag value="Real Device" />
3841
Regular Expression or REGEX is widely used to make searching/find characters in a string.
3942

4043
When you run a test on LambdaTest using a specific device, there may be scenarios, in which the particular device that you selected isn’t available. In these scenarios, REGEX will help you widen the search request for devices to run the test on.

docs/sharding-xcui.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ import CodeBlock from '@theme/CodeBlock';
2222
import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
2323
import Tabs from '@theme/Tabs';
2424
import TabItem from '@theme/TabItem';
25+
import RealDeviceTag from '../src/component/realDevice';
2526

2627
<script type="application/ld+json"
2728
dangerouslySetInnerHTML={{ __html: JSON.stringify({
@@ -47,7 +48,7 @@ import TabItem from '@theme/TabItem';
4748
}}
4849
></script>
4950

50-
51+
<RealDeviceTag value="Real Device" />
5152
Generally the XCUI tests are run in sequence which is a time taking process. This document explains how you can speed up this process by splitting the tests into **shards**. We can divide the various tests into shards which can run parallelly and save time while running various XCUI tests.
5253

5354
This document will cover how to execute **XCUI Tests** on real devices with **HyperExecute**. HyperExecute is a smart test orchestration platform to run end-to-end tests at the fastest speed possible. HyperExecute is configured using a YAML file.

0 commit comments

Comments
 (0)