You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/junit-report.md
+5-23Lines changed: 5 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,39 +45,23 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
45
45
}}
46
46
></script>
47
47
48
-
---
49
-
50
-
## Introduction
51
-
---
52
-
53
48
JUnit reports provide a detailed summary of test execution, allowing you to better understand your test outcomes. This document aims to guide you through the process of retrieving JUnit reports for Espresso tests executed on the LambdaTest platform.
54
49
55
-
## Objective
56
-
---
57
-
### By the end of this document, you should be able to:
58
-
59
-
1. Fetch JUnit reports for non-shard Espresso builds.
60
-
61
-
2. Fetch JUnit reports for shard builds, both for individual shards and all shards collectively.
50
+
> This feature is also supported for [Virtual Devices](/support/docs/app-automation-on-emulators-simulators/)
62
51
52
+
## JUnit Report APIs
63
53
64
-
65
-
## JUnit report APIs
66
-
----
67
-
68
-
**Non-shard build :**
54
+
### Non-shard build
69
55
To fetch the JUnit report for a `non-shard` build, you can use the following cURL command:
To fetch the JUnit report for a `single shard` in a shard build,use:
82
66
83
67
<divclassName="lambdatest__codeblock">
@@ -88,7 +72,7 @@ To fetch the JUnit report for a `single shard` in a shard build,use:
88
72
</div>
89
73
90
74
91
-
**Shard build (For all the shards):**
75
+
### Shard build (For all the shards)
92
76
To fetch the JUnit reports for `all shards` in a shard build, use:
93
77
94
78
<divclassName="lambdatest__codeblock">
@@ -98,8 +82,6 @@ To fetch the JUnit reports for `all shards` in a shard build, use:
98
82
</CodeBlock>
99
83
</div>
100
84
101
-
102
-
103
85
:::note
104
86
- Authenticate the API using your LambdaTest username and access key, and replace `build_id`, `job_id` and `shard_id` for which you want to fetch report.
105
87
- It is recommended to run the sharding test(via HyperExecute CLI) in the verbose mode i.e. with the **--verbose** flag. This allows the shard ID(task ID) and build ID(Job ID) to be displayed in the logs and then they can be used to fetch the above reports.
Copy file name to clipboardExpand all lines: docs/sharding-espresso.md
+3-31Lines changed: 3 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,8 +47,6 @@ import TabItem from '@theme/TabItem';
47
47
})
48
48
}}
49
49
></script>
50
-
51
-
52
50
Running **Espresso** tests sequentially can be laborious and time-intensive. This guide offers an efficient solution by introducing the concept of **sharding**. By breaking down tests into shards, they can be executed in parallel, significantly trimming down the total testing duration.
53
51
54
52
Furthermore, this document provides insights on executing Espresso Tests on real devices using the innovative **HyperExecute** platform. Designed with precision, HyperExecute stands out as a test orchestration solution, tailored to execute end-to-end tests at breakneck speed. To streamline its setup and configuration, a user-friendly `YAML` file is employed. Dive into this guide to make your testing process more agile and efficient.
@@ -57,19 +55,9 @@ Furthermore, this document provides insights on executing Espresso Tests on real
57
55
You can learn more about the HyperExecute portal and UI by going through our [Guided Walkthrough](/support/docs/hyperexecute-guided-walkthrough/) page. It contains all the relevant information that you need to optimize your testing process with HyperExecute.
58
56
:::
59
57
60
-
## Objectives
61
-
62
-
---
63
-
64
-
By the end of this topic, you will be able to:
65
-
1. Speed up your Espresso tests with sharding
66
-
2. Learn more about HyperExecute
67
-
3. Explore advanced features of LambdaTest
58
+
> This feature is also supported for [Virtual Devices](/support/docs/app-automation-on-emulators-simulators/)
68
59
69
60
## Prerequisites
70
-
71
-
---
72
-
73
61
Before you start performing your App automation testing with Espresso, please make sure:
74
62
75
63
- You have access to LambdaTest username and accessKey. If you have not registered yet, you can do the same by visiting our [website](https://accounts.lambdatest.com/register). You will be able to access the credentials at the [LambdaTest Profile](https://accounts.lambdatest.com/detail/profile)
@@ -113,14 +101,9 @@ Here is an example cURL request to upload your app using our REST API:
113
101
</TabItem>
114
102
</Tabs>
115
103
116
-
117
-
118
104
>Response of above cURL will be a **JSON** object containing the `App URL` of the format - `lt://APP123456789123456789` and will be used in the last step as `appId`.
119
105
120
-
121
-
122
106
### Step 2: Uploading Test Suite
123
-
124
107
Upload your **test suite** (.apk file) to the LambdaTest servers using our **REST API**. You need to provide your **Username** and **AccessKey** in the format `Username:AccessKey` in the **cURL** command for authentication. Make sure to add the path of the **appFile** in the cURL request. Here is an example cURL request to upload your app using our REST API:
125
108
126
109
**Using App File:**
@@ -154,11 +137,7 @@ Upload your **test suite** (.apk file) to the LambdaTest servers using our **RES
154
137
155
138
>Response of above cURL will be a **JSON** object containing the `App URL` of the format - `lt://APP123456789123456789` and will be used in the next step as ``testSuiteAppId``
156
139
157
-
158
140
## How to use Sharding
159
-
160
-
---
161
-
162
141
1. Firstly, create a folder on your local.
163
142
2. Download the **HyperExecute CLI** file and put it under this folder based on your platform.
164
143
#### Download HyperExecute CLI
@@ -177,7 +156,7 @@ Sharding can be categorized into two types:
177
156
178
157
Refer to the sample `.yaml` file here
179
158
180
-
```bash title="SampleYamlFile.yaml"
159
+
```yaml title="SampleYamlFile.yaml"
181
160
version: "0.2"
182
161
concurrency: 2
183
162
runson: android
@@ -238,14 +217,11 @@ If you are using the `deviceSelectionStrategy: any`, then in that case all the m
238
217
**For example:** If there are 2 shards mentioned in `.yaml`and 3 devices mentioned, the system will create 2 shards. These shards might use any 2 devices from the given 3 configurations. It's also possible that the same device configuration could be used for both shards. In this setup, test cases will be distributed between these shards.
239
218
:::
240
219
241
-
---
242
-
243
-
244
220
**Auto Sharding** : The system intelligently determines the distribution of tests across devices, employing specific criteria to optimize the testing process.
245
221
246
222
Refer to the sample `.yaml` file here
247
223
248
-
```bash title="SampleYamlFile.yaml"
224
+
```yaml title="SampleYamlFile.yaml"
249
225
version: "0.2"
250
226
concurrency: 2
251
227
runson: android
@@ -289,8 +265,6 @@ If you are using the `deviceSelectionStrategy: any`, then in that case all the s
289
265
**For example:** If the concurrency is set to 2 and 3 devices mentioned, the system will create 2 shards. These shards might use any 2 devices from the given 3 configurations. It's also possible that the same device configuration could be used for both shards. In this setup, test cases will be distributed between these shards.
290
266
:::
291
267
292
-
293
-
294
268
4. Go to the location of the folder on the terminal and run the below commands. After the second command, you may need to give permission on **System Settings/Privacy & Security**.
295
269
296
270
```bash
@@ -332,8 +306,6 @@ This example will fetch all the test cases from 2 classes and 1 package as defin
332
306
333
307
## Additional Links
334
308
335
-
---
336
-
337
309
-[Advanced Configuration for Capabilities](https://www.lambdatest.com/support/docs/desired-capabilities-in-appium/)
338
310
-[How to test locally hosted apps](https://www.lambdatest.com/support/docs/testing-locally-hosted-pages/)
339
311
-[How to integrate LambdaTest with CI/CD](https://www.lambdatest.com/support/docs/integrations-with-ci-cd-tools/)
Copy file name to clipboardExpand all lines: docs/supported-appium-versions-on-emulator-simulator.md
+21-53Lines changed: 21 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,33 +53,17 @@ LambdaTest offers a powerful and reliable cloud-based platform for testing mobil
53
53
## 1. App Testing on Android and iOS
54
54
Mobile app testing on LambdaTest emulators and simulators allows developers to ensure their applications perform as expected across multiple Android and iOS versions. Below are the supported versions for app testing.
55
55
56
-
### 1.1 Supported Android Versions for App Testing
57
-
The following table lists the Android versions supported for app testing, along with the corresponding Appium versions.
56
+
The following table lists the supported versionsn of Appium for Emulators (Android) and Simulators (iOS).
For mobile web testing, LambdaTest supports various Android <!--and iOS device--> versions, ensuring that your web applications are responsive and compatible with different browsers and devices. Below are the supported versions for web testing.
@@ -89,30 +73,14 @@ The following table lists the Android versions supported for web testing, along
Copy file name to clipboardExpand all lines: docs/xcui-supported-capibilities.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,8 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
46
46
47
47
This document provide details about the features and capabilities supported for XCUI Framework on LambdaTest.
48
48
49
+
> The capabilities listed in this document are also supported for [Virtual Devices](/support/docs/app-automation-on-emulators-simulators/)
50
+
49
51
| Capability Name | Data Type | Description |
50
52
|------|-----------|-------------|
51
53
| app | String | Enter the app id generated while uploading the app to the platform. Example:`lt://APP123456789123456789`|
@@ -59,7 +61,7 @@ This document provide details about the features and capabilities supported for
59
61
| build | String | To set the Espresso build name. Example: `build: My Espresso Build`. |
60
62
| geoLocation | String | Set the geolocation country code if you want to enable the same in your test. Example - `geoLocation: FR`|
61
63
| tunnel, tunnelName | Boolean | To activate the tunnel mode, pass the value as `tunnel: true` and provide the name of your tunnel as `tunnelName: NewTunnel`|
62
-
| resignApp | Boolean | Set this to `false` if you want to to prevent the apps from being re-signed. The app should be built for enterprise distribution. |
64
+
| resignApp <br /> <br />Not supported in **Virtual Devices**| Boolean | Set this to `false` if you want to to prevent the apps from being re-signed. The app should be built for enterprise distribution. |
63
65
64
66
:::caution Important
65
67
You can either use **GeoLocation** or **Tunnel** in single execute command. They both are mutually exclusive.
Copy file name to clipboardExpand all lines: docs/xcui-xml-report.md
+4-25Lines changed: 4 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,40 +44,22 @@ import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/co
44
44
})
45
45
}}
46
46
></script>
47
-
48
-
---
49
-
50
-
## Introduction
51
-
---
52
-
53
47
XML reports provide a detailed summary of test execution, allowing you to better understand your test outcomes. This document aims to guide you through the process of retrieving XML reports for XCUI tests executed on the LambdaTest platform.
54
48
55
-
## Objective
56
-
---
57
-
### By the end of this document, you should be able to:
58
-
59
-
1. Fetch XML reports for non-shard XCUI builds.
60
-
61
-
2. Fetch XML reports for shard builds, both for individual shards and all shards collectively.
62
-
63
-
49
+
> This feature is also supported for [Virtual Devices](/support/docs/app-automation-on-emulators-simulators/)
64
50
65
51
## XML report APIs
66
-
----
67
-
68
-
**Non-shard build :**
52
+
### Non-shard build
69
53
To fetch the XML report for a `non-shard` build, you can use the following cURL command:
To fetch the XML report for a `single shard` in a shard build,use:
82
64
83
65
<divclassName="lambdatest__codeblock">
@@ -87,8 +69,7 @@ To fetch the XML report for a `single shard` in a shard build,use:
87
69
</CodeBlock>
88
70
</div>
89
71
90
-
91
-
**Shard build (For all the shards):**
72
+
### Shard build (For all the shards)
92
73
To fetch the XML reports for `all shards` in a shard build, use:
93
74
94
75
<divclassName="lambdatest__codeblock">
@@ -98,8 +79,6 @@ To fetch the XML reports for `all shards` in a shard build, use:
98
79
</CodeBlock>
99
80
</div>
100
81
101
-
102
-
103
82
:::note
104
83
- Authenticate the API using your LambdaTest username and access key, and replace `build_id`, `job_id` and `shard_id` for which you want to fetch report.
105
84
- It is recommended to run the sharding test(via HyperExecute CLI) in the verbose mode i.e. with the **--verbose** flag. This allows the shard ID(task ID) and build ID(Job ID) to be displayed in the logs and then they can be used to fetch the above reports.
0 commit comments