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/hyperexecute-maestro-testing.md
+15-83Lines changed: 15 additions & 83 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,6 @@ import TabItem from '@theme/TabItem';
51
51
This page outlines how to execute your Maestro tests on HyperExecute with [YAML 0.2](/support/docs/hyperexecute-yaml-version0.2/)
52
52
53
53
## Prerequisites
54
-
55
54
To run the Tests on HyperExecute from your Local System, you are required:
56
55
57
56
- Your LambdaTest [Username and Access key](/support/docs/hyperexecute-how-to-get-my-username-and-access-key/)
@@ -60,23 +59,17 @@ To run the Tests on HyperExecute from your Local System, you are required:
60
59
-[HyperExecute YAML](/support/docs/hyperexecute-yaml-version0.2/) file which contains all the necessary instructions.
61
60
62
61
## Step 1: Setup Your Test Suite
63
-
64
62
You can use your own project to configure and test it. For demo purposes, we are using the sample repository.
65
63
66
64
:::tip Sample repo
67
-
68
65
Download or Clone the code sample for the Maestro framework from the LambdaTest GitHub repository to run the tests on the HyperExecute.
69
-
70
66
<ahref="https://github.com/LambdaTest/maestro-sample-test"className="github__anchor"><img loading="lazy" src={require('../assets/images/icons/github.png').default} alt="Image" className="doc_img"/> View on GitHub</a>
71
-
72
67
:::
73
68
74
69
## Step 2: Setup the CLI in your Test Suite
75
-
76
70
After cloning / downloading the sample repo, you need to setup the CLI and the environment variables.
77
71
78
72
### Download the HyperExecute CLI
79
-
80
73
The CLI is used for triggering the tests on HyperExecute. It is recommend to download the CLI binary on the host system and keep it in the root directory of the suite to perform the tests on HyperExecute.
81
74
82
75
You can download the CLI for your desired platform from the below mentioned links:
@@ -88,13 +81,11 @@ You can download the CLI for your desired platform from the below mentioned link
88
81
| Linux |https://downloads.lambdatest.com/hyperexecute/linux/hyperexecute|
89
82
90
83
### Setup Environment Variable
91
-
92
84
Now, you need to export your environment variables *LT_USERNAME* and *LT_ACCESS_KEY* that are available in the [LambdaTest Profile page](https://accounts.lambdatest.com/detail/profile).
93
85
94
86
Run the below mentioned commands in your terminal to setup the CLI and the environment variables.
95
87
96
88
<TabsclassName="docs__val">
97
-
98
89
<TabItemvalue="bash"label="Linux / MacOS"default>
99
90
100
91
<divclassName="lambdatest__codeblock">
@@ -119,8 +110,7 @@ set LT_ACCESS_KEY="${ YOUR_LAMBDATEST_ACCESS_KEY()}"`}
119
110
</Tabs>
120
111
121
112
## Step 3: Upload your Application
122
-
123
-
Upload your <b>_android_</b> application (.apk file) to the LambdaTest servers using our <b>REST API</b>. You need to provide your <b>Username</b> and <b>AccessKey</b> in the format `Username:AccessKey` in the <b>cURL</b> command for authentication.
113
+
Upload your <b>_android_</b> application (.apk file) or <b>iOS</b> application (.ipa file) to the LambdaTest servers using our <b>REST API</b>. You need to provide your <b>Username</b> and <b>AccessKey</b> in the format `Username:AccessKey` in the <b>cURL</b> command for authentication.
124
114
125
115
:::info
126
116
Enter your local path of the code repository instead of `<YOUR_LOCAL_APP_PATH>` in the below cURL command.
@@ -133,85 +123,28 @@ Enter your local path of the code repository instead of `<YOUR_LOCAL_APP_PATH>`
133
123
</CodeBlock>
134
124
</div>
135
125
136
-
137
126
> Response of above cURL will be a **JSON** object containing the `App ID` of the format - `<APP123456789012345678901234567>` and will be used in the next step.
138
127
139
128
## Step 4: Configure YAML in your Test Suite
129
+
Enter your `APP_ID` in the YAML file that you have fetched in the above step.
140
130
141
-
Enter your `<APP_ID>` in the YAML file (line 52) that you have fetched in the above step.
131
+
<TabsclassName="docs__val">
132
+
<TabItemvalue="android"label="Android"default>
142
133
143
-
```yaml
144
-
---
145
-
# Define the version of the configuration file
146
-
version: "0.2"
147
-
148
-
# Specify the target platform for test execution (Android in this case)
149
-
runson: android
150
-
151
-
# Enable autosplit for test execution
152
-
autosplit: true
153
-
154
-
# Set the concurrency level for test execution (2 devices in parallel)
155
-
concurrency: 1
156
-
157
-
# Only report the status of the test framework
158
-
frameworkStatusOnly: true
159
-
160
-
# Enable dynamic allocation of resources
161
-
dynamicAllocation: true
162
-
163
-
# Pre-install required dependencies using pip
164
-
# will need java and maestro inside the container
165
-
pre:
166
-
- chmod +x ./maestro-test/setup-script.sh
167
-
168
-
env:
169
-
MAESTRO: true
170
-
171
-
# Test discovery configuration
172
-
testDiscovery:
173
-
# Command to discover tests from the test.txt file
174
-
command: cat ./maestro-test/discover.txt
175
-
# Test discovery mode can be static/dynamic
176
-
mode: static
177
-
# Test type is raw (custom test implementation)
178
-
type: raw
179
-
180
-
# Command to run the tests using the testRunnerCommand
> **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**.
216
149
217
150
Run the below command in your terminal at the root folder of the project:
@@ -231,7 +164,6 @@ OR use this command if you have not exported your username and access key in the
0 commit comments