.default}){kind=icon}
View on GitHub View on GitHub
:::
-If you are using your own project, make sure you update the **Hub endpoint** in your tests file.
-
-By setting up the Hub endpoint, you establish the communication channel between your tests and the browser nodes, enabling effective test distribution and execution.
-
-
-Configure the desired capabilities based on your test requirements. For example:
-
-```java title="test.java"
-DesiredCapabilities capabilities = new DesiredCapabilities();
-capabilities.setCapability("browserName", "chrome");
-capabilities.setCapability("version", "70.0");
-capabilities.setCapability("platform", "win10"); # If this cap isn't specified, it will just get the any available one
-capabilities.setCapability("build", "LambdaTestSampleApp");
-capabilities.setCapability("name", "LambdaTestJavaSample");
-```
-
-> You can also use **dev** and **beta** browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
-
-### Step 2: Setup the CLI in your Test Suite
-
-After cloning / downloading the sample repo, you need to setup the CLI and the environment variables.
-
-#### Download the HyperExecute CLI
-
-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.
-
-You can download the CLI for your desired platform from the below mentioned links:
+### Step 2: Download the CLI in your Project
+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 project to perform the tests on HyperExecute. You can download the CLI for your desired platform from the below mentioned links:
| Platform | HyperExecute CLI |
| ---------| ---------------- |
-| Windows | https://downloads.lambdatest.com/hyperexecute/windows/hyperexecute.exe |
-| MacOS | https://downloads.lambdatest.com/hyperexecute/darwin/hyperexecute |
| Linux | https://downloads.lambdatest.com/hyperexecute/linux/hyperexecute |
-
+| Windows | https://downloads.lambdatest.com/hyperexecute/windows/hyperexecute.exe |
+| macOS | https://downloads.lambdatest.com/hyperexecute/darwin/hyperexecute |
+
-### Step 3: Configure YAML in your Test Suite
-
-Configure your YAML file as per your use cases using **key value** pairs.
-
-In this sample YAML file, we have mentioned:
-
-- **version** of the YAML file
-- **Timeouts** for executing your project
-- **Mode of execution** is [Autosplit](/support/docs/hyperexecute-auto-split-strategy/). You can also opt for [Matrix](/support/docs/hyperexecute-matrix-multiplexing-strategy/) or [Hybrid](/support/docs/hyperexecute-hybrid-strategy/) mode.
-- **Pre and Post** commands
-- **Reports and Artefacts** that will be generated after the completion of tests
-- and other necessary YAML Parameters
+### Step 3: Execute your Test Suite
-
-```yaml reference title="HyperExecute AutoSplit YAML"
-https://github.com/LambdaTest/testng-selenium-hyperexecute-sample/blob/main/yaml/linux/v2/testng_hyperexecute_autosplit_sample.yaml
-```
-
-### Step 4: 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**.
+> **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
-```
-
-OR use this command if you have not exported your username and access key in the step 2.
-
.default})
.default})
-### Step 5: Monitor the Test Execution
+### Step 4: Monitor the Test Execution
Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
.default})
-### Step 6: Download Artifacts and Reports
+
-## 2. Testing Using Gitpod
+
-[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&frameworkType=Selenium&framework=TestNG)
+
-**Step 2:** Login with LambdaTest credentials. Once logged in, a pop-up confirmation will appear, asking you to **'Proceed'** to the Gitpod editor in a new tab. The current tab will display the HyperExecute Dashboard.
+
-.default})
+
-**Step 3:** Choose your preferred editor (we recommend VS Code Editor)
+
-.default})
+
-**Step 4:** As you are running a sample project, Fetching of the Test Scripts, [HyperExecute YAML](/support/docs/deep-dive-into-hyperexecute-yaml/), [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) and Triggering your tests using the `Execution Command` will be automated.
+
-.default})
+
-**Step 5:** Once you see the `Job Link` in the logs, you can visit the [HyperExecute dashboard](https://hyperexecute.lambdatest.com/hyperexecute) to see the tests getting executed.
+
-:::tip
+
-## Navigation in Automation Dashboard
+## Testing using your own Project
+
+### Step 1: Configure your own Project
+If you are using your own project, make sure you update the **Hub endpoint** in your tests file. By setting up the Hub endpoint, you establish the communication channel between your tests and the browser nodes, enabling effective test distribution and execution. Configure the desired capabilities based on your test requirements. For example:
+
+```java title="test.java"
+DesiredCapabilities capabilities = new DesiredCapabilities();
+capabilities.setCapability("browserName", "chrome");
+capabilities.setCapability("version", "70.0");
+capabilities.setCapability("platform", "win10"); # If this cap isn't specified, it will just get the any available one
+capabilities.setCapability("build", "LambdaTestSampleApp");
+capabilities.setCapability("name", "LambdaTestJavaSample");
+```
+
+> You can also use **dev** and **beta** browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
+
+### Step 2: Download the CLI in your Project
+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 project to perform the tests on HyperExecute. You can download the CLI for your desired platform from the below mentioned links:
+
+| Platform | HyperExecute CLI |
+| ---------| ---------------- |
+| Linux | https://downloads.lambdatest.com/hyperexecute/linux/hyperexecute |
+| Windows | https://downloads.lambdatest.com/hyperexecute/windows/hyperexecute.exe |
+| macOS | https://downloads.lambdatest.com/hyperexecute/darwin/hyperexecute |
+
+### Step 3: Configure YAML in your Test Suite
-Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution.
+Configure your YAML file as per your use cases using **key value** pairs.
-You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
+In this sample YAML file, we have mentioned:
+
+- **version** of the YAML file
+- **Timeouts** for executing your project
+- **Mode of execution** is [Autosplit](/support/docs/hyperexecute-auto-split-strategy/). You can also opt for [Matrix](/support/docs/hyperexecute-matrix-multiplexing-strategy/) or [Hybrid](/support/docs/hyperexecute-hybrid-strategy/) mode.
+- **Pre and Post** commands
+- **Reports and Artefacts** that will be generated after the completion of tests
+- and other necessary YAML Parameters
+
+
+```yaml reference title="HyperExecute AutoSplit YAML"
+https://github.com/LambdaTest/testng-selenium-hyperexecute-sample/blob/main/yaml/linux/v2/testng_hyperexecute_autosplit_sample.yaml
+```
+
+### Step 4: Monitor the Test Execution
+
+Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexecute) and check your Job status.
+
+
+
+## Navigation in Automation Dashboard
+Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution. You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
.default})
@@ -246,24 +246,69 @@ The snapshot below shows the videos, logs and other meta data for that specific
.default})
+
+## Advanced Parameters
+
+Use Smart Auto Split Strategy, Matrix Strategy or Hybrid Strategy modes to split and execute tests as per your requirements.
+Get a detailed test report for every job and stream the terminal logs in real time to understand everything that happened with your test.
+Run your jobs faster or fail them quickly to receive instant feedback and save your test time.
+Label the jobs that you want to run first on HyperExecute by giving them a higher priority.
+HyperExecute also manages all of your test artifacts and provides you with the option to implement smart workflows on your test code without modifying it.
+Root Cause Analysis and Error Classification features in HyperExecute to view different kinds of errors and directly land on corrective measures or fixes.
+Triggers long-running Application Servers tasks like running WebApps or Databases and generates the logs report in the Dashboard.
+Auto Healing Feature allows you to automatically rеcovеr from cеrtain typеs of failurеs during thе еxеcution of your tеst scripts.
+