From 2dbc547581e051762e71ef3eaa6de32f233d398f Mon Sep 17 00:00:00 2001 From: Aman Chopra Date: Fri, 8 Nov 2024 19:43:07 +0530 Subject: [PATCH 1/2] artifacts and reports for HYP espresso xcui test --- ...cute-cli-run-tests-on-hyperexecute-grid.md | 1 - docs/hyperexecute-espresso-testing.md | 28 +++++++++++++--- docs/hyperexecute-xcui-testing.md | 22 ++++++++++--- docs/hyperexecute-yaml-version0.2.md | 11 +++++++ ...d-appium-versions-on-emulator-simulator.md | 32 +++++++++---------- 5 files changed, 69 insertions(+), 25 deletions(-) diff --git a/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid.md b/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid.md index 1d660120b..d1fc96b76 100644 --- a/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid.md +++ b/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid.md @@ -125,7 +125,6 @@ This flag allows you to download all the test related results that are generated :::note -- This functionality is not available with **XCUI** tests. - For Espresso with private devices HyperExecute can download user generated artefacts. ::: diff --git a/docs/hyperexecute-espresso-testing.md b/docs/hyperexecute-espresso-testing.md index 364258237..3a2de3f55 100644 --- a/docs/hyperexecute-espresso-testing.md +++ b/docs/hyperexecute-espresso-testing.md @@ -167,13 +167,16 @@ runson: android autosplit: true +report: true #to generate reports + framework: name: "android/espresso" args: buildName: "Espresso" video: true deviceLog: true - + artifacts: true #to generate artifacts + # You can use either the appId (lt://APP1234567) or provide the path of the application using appPath. Both examples are given below. appPath: proverbial_android.apk testSuitePath: proverbial_android_expressotest.apk @@ -209,12 +212,16 @@ runson: android autosplit: false +report: true #to generate reports + framework: name: android/espresso args: buildName: Espresso video: true deviceLog: true + artifacts: true #to generate artifacts + # highlight-next-line appPath: proverbial_android.apk # highlight-next-line @@ -264,21 +271,34 @@ preservedDevice: true ``` ::: -## Step 6: Execute your Test Suite +## Step 6: Generate Reports and Artifacts +To generate artifacts for your Espresso tests, add the `artifacts: true` flag in your YAML file: + +```yaml +report: true +framework: + name: "android/espresso" + args: + artifacts: true + ...// +``` + +To download these artifacts in your local machine, you can pass the `--download-artifacts` and `--download-report` flag with the CLI command to execute the tests as shown in the next step. +## Step 7: Execute your Test Suite > **NOTE :** In case of MacOS, if you get a permission denied warning while executing CLI, simply run **`chmod u+x ./hyperexecute`** to allow permission. In case you get a security popup, allow it from your **System Preferences** → **Security & Privacy** → **General tab**. Run the below command in your terminal at the root folder of the project: ```bash -./hyperexecute --config RELATIVE_PATH_OF_YOUR_YAML_FILE +./hyperexecute --config RELATIVE_PATH_OF_YOUR_YAML_FILE --download-artifacts --download-report ``` OR use this command if you have not exported your username and access key in the step 2.
- {`./hyperexecute --user ${ YOUR_LAMBDATEST_USERNAME()} --key ${ YOUR_LAMBDATEST_ACCESS_KEY()} --config RELATIVE_PATH_OF_YOUR_YAML_FILE `} + {`./hyperexecute --user ${ YOUR_LAMBDATEST_USERNAME()} --key ${ YOUR_LAMBDATEST_ACCESS_KEY()} --config RELATIVE_PATH_OF_YOUR_YAML_FILE --download-artifacts --download-report`}
diff --git a/docs/hyperexecute-xcui-testing.md b/docs/hyperexecute-xcui-testing.md index 3e2d86099..df97cb3c7 100644 --- a/docs/hyperexecute-xcui-testing.md +++ b/docs/hyperexecute-xcui-testing.md @@ -224,6 +224,7 @@ framework: values: ["LambdaUiKitIOSUITests/testverifyAppLaunch"] deviceSelectionStrategy: any devices: [".*"] + artifacts: true shards: mappings: @@ -258,25 +259,38 @@ If you are using the `deviceSelectionStrategy: any`, then in that case all the m ::: -## Step 5: Execute your Test Suite +## Step 5: Generate Artifacts +To generate artifacts for your XCUI tests, add the `artifacts: true` flag in your YAML file: + +```yaml +framework: + name: "ios/xcui" + args: + artifacts: true + ...// +``` + +To download these artifacts in your local machine, you can pass the `--download-artifacts` flag with the CLI command to execute the tests as shown in the next step. + +## Step 6: Execute your Test Suite > **NOTE :** In case of macOS, if you get a permission denied warning while executing CLI, simply run **`chmod u+x ./hyperexecute`** to allow permission. In case you get a security popup, allow it from your **System Preferences** → **Security & Privacy** → **General tab**. Run the below command in your terminal at the root folder of the project: ```bash -./hyperexecute --config RELATIVE_PATH_OF_YOUR_YAML_FILE +./hyperexecute --config RELATIVE_PATH_OF_YOUR_YAML_FILE --download-artifacts ``` OR use this command if you have not exported your username and access key in the step 2.
- {`./hyperexecute --user ${ YOUR_LAMBDATEST_USERNAME()} --key ${ YOUR_LAMBDATEST_ACCESS_KEY()} --config RELATIVE_PATH_OF_YOUR_YAML_FILE `} + {`./hyperexecute --user ${ YOUR_LAMBDATEST_USERNAME()} --key ${ YOUR_LAMBDATEST_ACCESS_KEY()} --config RELATIVE_PATH_OF_YOUR_YAML_FILE --download-artifacts`}
-## Step 6: Monitor the Test Execution +## Step 7: Monitor the Test Execution Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status. diff --git a/docs/hyperexecute-yaml-version0.2.md b/docs/hyperexecute-yaml-version0.2.md index 6bc3805e2..c4a80208e 100644 --- a/docs/hyperexecute-yaml-version0.2.md +++ b/docs/hyperexecute-yaml-version0.2.md @@ -64,6 +64,7 @@ The ```framework``` field in Hyperexecute YAML Version 0.2 allows you to configu | [workingDirectory](#workingDirectory) | String | No | Specifies the working directory where all discovery and execution commands will be executed.| | [defaultReports](#defaultReports) | Boolean | No | Specifies whether to create default reports for the specified framework.| | [region](#region) | String | No | Specifies in which region you want to spin your appium tests.| +| [artifacts](#artifacts) | Boolean | No | Specifies whether to genreate artifacts or not | ### `name` Specifies the testing framework used in your repository. @@ -167,6 +168,16 @@ framework: region: us ``` +### `artifacts` + +To generate artifacts for your Espresso tests, add the `artifacts: true` flag in your YAML file: + +```yaml +framework: + args: + artifacts: true +``` + > 📕 Learn [how to perform group-based test discovery in TestNG](/support/docs/hyperexecute-how-to-perform-group-based-test-discovery-in-testng) ## Sample Yaml Version 0.2 diff --git a/docs/supported-appium-versions-on-emulator-simulator.md b/docs/supported-appium-versions-on-emulator-simulator.md index 8f08c07b6..16b6514b6 100644 --- a/docs/supported-appium-versions-on-emulator-simulator.md +++ b/docs/supported-appium-versions-on-emulator-simulator.md @@ -81,27 +81,27 @@ The following table lists the iOS versions supported for app testing, along with | 17 | ['2.2.1', '2.3.0'] | | 18 | ['2.2.1', '2.3.0'] | -## 2. Web Testing on Android and 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. +## 2. Web Testing on Android +For mobile web testing, LambdaTest supports various Android versions, ensuring that your web applications are responsive and compatible with different browsers and devices. Below are the supported versions for web testing. -### 2.1 Supported Android Versions for Web Testing + The following table lists the Android versions supported for web testing, along with the corresponding Appium versions. | Android Versions | Appium Versions (Android) | |------------------|-----------------------------------------| -| 7 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | -| 7.1 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | -| 8 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | -| 8.1 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | -| 9 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | -| 10 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | -| 11 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | -| 12 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | -| 13 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | -| 14 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | -| 15 | ['1.12.1', '1.17.0', '1.22.3', '2.6.0'] | +| 7 | [`1.17.0`, `1.17.1`, `1.18.0`, `1.19.1`, `1.20.0`, `1.20.1`, `1.20.2`, `1.21.0`, `1.22.0`, `1.22.1`, `1.22.2`, `1.22.3` **(default)**] | +| 7.1 | [`1.17.0`, `1.17.1`, `1.18.0`, `1.19.1`, `1.20.0`, `1.20.1`, `1.20.2`, `1.21.0`, `1.22.0`, `1.22.1`, `1.22.2`, `1.22.3` **(default)**] | +| 8 | [`1.17.0`, `1.17.1`, `1.18.0`, `1.19.0`, `1.19.1`, `1.20.0`, `1.20.1`, `1.20.2`, `1.21.0`, `1.22.0`, `1.22.1`, `1.22.2`, `1.22.3` **(default)**] | +| 8.1 | [`1.17.0`, `1.17.1`, `1.18.0`, `1.19.1`, `1.20.0`, `1.20.1`, `1.20.2`, `1.21.0`, `1.22.0`, `1.22.1`, `1.22.2`, `1.22.3` **(default)**] | +| 9 | [`1.17.0`, `1.17.1`, `1.18.0`, `1.19.0`, `1.19.1`, `1.20.0`, `1.20.1`, `1.20.2`, `1.21.0`, `1.22.0`, `1.22.1`, `1.22.2`, `1.22.3` **(default)**] | +| 10 | [`1.17.0`, `1.17.1`, `1.18.0`, `1.19.0`, `1.19.1`, `1.20.0`, `1.20.1`, `1.20.2`, `1.21.0`, `1.22.0`, `1.22.1`, `1.22.2`, `1.22.3` **(default)**] | +| 11 | [`1.17.0`, `1.17.1`, `1.18.0`, `1.19.0`, `1.19.1`, `1.20.0`, `1.20.1`, `1.20.2`, `1.21.0`, `1.22.0`, `1.22.1`, `1.22.2`, `1.22.3` **(default)**] | +| 12 | [`1.17.0`, `1.17.1`, `1.18.0`, `1.19.0`, `1.19.1`, `1.20.0`, `1.20.1`, `1.20.2`, `1.21.0`, `1.22.0`, `1.22.1`, `1.22.2`, `1.22.3` **(default)**, `2.0.1`, `2.1.0`, `2.1.1`, `2.1.2`, `2.1.3`, `2.2.0`, `2.2.1`, `2.2.2`, `2.2.3`, `2.3.0`, `2.4.0`, `2.4.1`, `2.5.0`, `2.5.1`, `2.5.2`, `2.5.3`, `2.5.4`, `2.6.0`] | +| 13 | [`1.17.0`, `1.17.1`, `1.18.0`, `1.19.0`, `1.19.1`, `1.20.0`, `1.20.1`, `1.20.2`, `1.21.0`, `1.22.0`, `1.22.1`, `1.22.2`, `1.22.3`, `2.0.1`, `2.1.0`, `2.1.1`, `2.1.2`, `2.1.3`, `2.2.0`, `2.2.1`, `2.2.2`, `2.2.3`, `2.3.0`, `2.4.0`, `2.4.1`, `2.5.0`, `2.5.1`, `2.5.2`, `2.5.3`, `2.5.4`, `2.6.0` **(default)**] | +| 14 | [`1.17.0`, `1.17.1`, `1.18.0`, `1.19.0`, `1.19.1`, `1.20.0`, `1.20.1`, `1.20.2`, `1.21.0`, `1.22.0`, `1.22.1`, `1.22.2`, `1.22.3`, `2.0.1`, `2.1.0`, `2.1.1`, `2.1.2`, `2.1.3`, `2.2.0`, `2.2.1`, `2.2.2`, `2.2.3`, `2.3.0`, `2.4.0`, `2.4.1`, `2.5.0`, `2.5.1`, `2.5.2`, `2.5.3`, `2.5.4`, `2.6.0` **(default)**] | +| 15 | [`1.22.3`, `2.0.1`, `2.1.0`, `2.2.0`, `2.3.0`, `2.4.0`, `2.5.0`, `2.6.0` **(default)**] | -### 2.2 Supported iOS Versions for Web Testing + \ No newline at end of file From 8e2b1874e27e3358d1fd26bc8c35a3307edb0488 Mon Sep 17 00:00:00 2001 From: Aman Chopra Date: Fri, 8 Nov 2024 19:45:43 +0530 Subject: [PATCH 2/2] spell updates --- docs/hyperexecute-yaml-version0.2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/hyperexecute-yaml-version0.2.md b/docs/hyperexecute-yaml-version0.2.md index c4a80208e..503b41651 100644 --- a/docs/hyperexecute-yaml-version0.2.md +++ b/docs/hyperexecute-yaml-version0.2.md @@ -64,7 +64,7 @@ The ```framework``` field in Hyperexecute YAML Version 0.2 allows you to configu | [workingDirectory](#workingDirectory) | String | No | Specifies the working directory where all discovery and execution commands will be executed.| | [defaultReports](#defaultReports) | Boolean | No | Specifies whether to create default reports for the specified framework.| | [region](#region) | String | No | Specifies in which region you want to spin your appium tests.| -| [artifacts](#artifacts) | Boolean | No | Specifies whether to genreate artifacts or not | +| [artifacts](#artifacts) | Boolean | No | Specifies whether to generate artifacts or not | ### `name` Specifies the testing framework used in your repository.