+
-{`curl -u "${ YOUR_LAMBDATEST_USERNAME()}:${ YOUR_LAMBDATEST_ACCESS_KEY()}" --location --request POST "https://manual-api.lambdatest.com/app/uploadFramework" --form "appFile=@"C:/Users/varunkumarb/Downloads/proverbial_ios_xcuitest.ipa"" --form "type=\"espresso-android\""`}
+{`${ YOUR_LAMBDATEST_USERNAME()}:${ YOUR_LAMBDATEST_ACCESS_KEY()}`}
-
-
-
-:::note
+- Once you have uploaded your app and test suite, you can execute your test by running the following command:
+
+> Enter your **BASIC_AUTH_TOKEN**, **APP_ID** (generated in the first step) and **TEST_SUITE_ID** (generated in the second step) in the below command.
-Response of above cURL will be a **JSON** object containing the `App URL` of the format - `APP123456789123456789` and will be used in the next step as ``testSuiteAppId``
-
-:::
+```bash
+curl --location --request POST 'https://mobile-api.lambdatest.com/framework/v1/espresso/build' \
+--header 'Authorization: Basic BASIC_AUTH_TOKEN' \
+--header 'Content-Type: application/json' \
+--data-raw '{
+ "app" : "APP_ID",
+ "testSuite": "TEST_SUITE_ID",
+ "device" : ["Galaxy S21 5G-12"],
+ "queueTimeout": 10800,
+ "IdleTimeout": 150,
+ "deviceLog": true,
+ "network": false,
+ "build" : "Proverbial-Espresso"
+ # highlight-start
+ "envVariables":{ //setting up environment variables
+ "STAGE":"stg1",
+ "PROD":"prod1"
+ }
+ # highlight-end
+}'
+```
-## Step 3: Configure YAML in your Test Suite
-Enter your `
` and `` in the YAML file
+## Run your test in HyperExecute
+To execute your test suite in HyperExecute, configure your YAML file by specifying the `` and ``.
```yaml
---
@@ -203,70 +205,7 @@ framework:
values: ["/", "/"]
```
-## Step 4: Generate Reports and Artifacts
-To generate artifacts for your XCUI tests, add the `artifacts: true` and `report: 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 5: 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 --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 --download-artifacts --download-report`}
-
-
-
-## Step 6: Monitor the Test Execution
-
-Visit the dashboard and check your job status.
-
-
-
-## Benefits of Using Environment Variables in Espresso
-
-### Environment Flexibility:
-Easily switch between different configurations (STAGE, PROD, DEV) without changing the test code.
-
-### Reusability:
-Use the same test script for different environments by only changing the environment variables.
-
-### Cleaner Configurations:
-Manage and switch environment settings via Postman or YAML without modifying your test code.
-
-### Cross-Platform Compatibility:
-LambdaTest allows you to run your Espresso tests on multiple Android devices in parallel, ensuring broader coverage.
-
-## Troubleshooting Tips
-### Problem: Environment Variables Not Loading
-Ensure that the environment variables are correctly defined in Postman or YAML and properly linked to LambdaTest.
-Double-check that the correct environment variable names are being used in your Espresso test code.
-### Problem: Environment Variable Not Found
-Verify that the environment variable name in the LambdaTest capability and the test code match exactly.
-Check the syntax in the Postman or YAML file for any typos or missing parameters.
-### Problem: Test Fails on LambdaTest
-Make sure the Appium server or Espresso test is correctly set up on LambdaTest.
-Ensure that the environment variable values are being passed and accessed properly in the code.
diff --git a/sidebars.js b/sidebars.js
index 02cb4a727..c474ffbb3 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -2595,22 +2595,17 @@ module.exports = {
id: "getting-started-with-espresso-testing",
},
{
- type: "doc",
+ type: "category",
+ collapsed: true,
label: "Supported Capabilities",
- id: "espresso-supported-capabilities",
- },
- // {
- // type: "category",
- // collapsed: true,
- // label: "Supported Capabilities",
- // link: {
- // type: "doc",
- // id: "espresso-supported-capabilities",
- // },
- // items: [
- // "espresso-env-variables-settings",
- // ],
- // },
+ link: {
+ type: "doc",
+ id: "espresso-supported-capabilities",
+ },
+ items: [
+ "espresso-env-variables-settings",
+ ],
+ },
{
type: "doc",
label: "RegEx in Espresso",