For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

Running Selenium Framework Tests on HyperExecute

HyperExecute runs your Selenium test suites at scale across every major language binding and test framework. Pick your language below, clone the matching sample repository, and trigger the job with the HyperExecute CLI. The setup steps are the same for every framework, only the sample repository and its YAML change.

HyperExecute is an AI Native Test Orchestration Cloud Platform that runs your end-to-end tests quickly and efficiently, with Just-in-Time (JIT) infrastructure, smart orchestration, and detailed real time logs.

Supported languages and frameworks:

  • Java: TestNG, JUnit, Cucumber
  • Python: PyTest, PyUnit, Behave, Robot
  • C#: NUnit, SpecFlow, Reqnroll
  • Ruby: Ruby, Capybara
  • JavaScript: WebdriverIO, Nightwatch, Protractor

Prerequisites​

To run Selenium tests on HyperExecute from your local system, you need:

Set Up the HyperExecute CLI and Credentials​

Download the HyperExecute CLI binary and keep it in the root directory of your test suite:

PlatformHyperExecute CLI
Windowshttps://downloads.lambdatest.com/hyperexecute/windows/hyperexecute.exe
macOShttps://downloads.lambdatest.com/hyperexecute/darwin/hyperexecute
Linuxhttps://downloads.lambdatest.com/hyperexecute/linux/hyperexecute

Export your TestMu AI credentials as environment variables so the CLI can authenticate:

export LT_USERNAME="undefined"
export LT_ACCESS_KEY="undefined"
note

On macOS, if you get a permission denied warning while executing the CLI, run chmod u+x ./hyperexecute to grant permission. If a security popup appears, allow it from System Preferences > Security & Privacy > General.

Run a Selenium Test in Your Framework​

Pick your language, then your framework. Clone the matching sample repository (each includes a ready-to-run HyperExecute YAML) and trigger the job with the HyperExecute CLI using the credentials and CLI you set up above.

Java​

Running TestNG Framework Tests on HyperExecute​

TestNG is a widely-used testing framework for Java applications, designed to simplify and enhance the testing process for developers. It provides a flexible and powerful platform for running test suites, enabling effective unit testing, integration testing, and end-to-end testing of Java applications.

HyperExecute is an AI Native Test Orchestration Cloud Platform that empowers you to run end-to-end tests quickly and efficiently. It provides Just-in-Time (JIT) testing infrastructure with fast execution speeds, smart orchestration, and detailed logs.

Execute your TestNG framework tests on HyperExecute using YAML 0.2 via two different methods:

1. Testing Using Local System​

Follow the step-by-step guide to execute your test on HyperExecute.

Step 1: Configure Your Test Suite​

You can use your own project to configure and test it. For demo purposes, we are using the sample repository.

Sample repo

Download or Clone the code sample for the TestNG from the TestMu AI GitHub repository to run the tests on the HyperExecute.

Image 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.

Update your TestNG test configuration to point to the TestMu AI hub and set capabilities as needed:

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", "TestMu AI SampleApp");
capabilities.setCapability("name", "TestMu AI JavaSample");

You can also use dev and beta browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 Capabilities Generator.

Step 2: 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. You can also opt for Matrix or Hybrid mode.
  • Pre and Post commands
  • Reports and Artefacts that will be generated after the completion of tests
  • and other necessary YAML Parameters
HyperExecute AutoSplit YAML
loading...
Step 3: 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:

./hyperexecute --config RELATIVE_PATH_OF_YOUR_YAML_FILE

OR use this command if you have not exported your username and access key.

./hyperexecute --user undefined --key undefined --config RELATIVE_PATH_OF_YOUR_YAML_FILE
TestNG HyperExecute Terminal LogsTestNG HyperExecute Terminal Logs
Step 4: Monitor the Test Execution​

Visit the HyperExecute Dashboard and check your Job status.

automation-dashboard
Step 5: Download Artifacts and Reports​

HyperExecute also facilitates the provision to download the Artifacts and Reports on your local machine. Click on the corresponding button to download your generated artifacts and reports.

automation-dashboard
2. Testing Using Gitpod​

You can also use the Gitpod platform to execute our sample repository. It will fetch all the sample codebases and trigger the CLI to execute the tests.

Follow the below steps to run Test using Gitpod:

Step 1: Click 'Open in Gitpod' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.

Run in Gitpod

Step 2: Login with TestMu AI 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.

Gitpod popup

Step 3: Choose your preferred editor (we recommend VS Code Editor)

Image

Step 4: As you are running a sample project, Fetching of the Test Scripts, HyperExecute YAML, HyperExecute CLI and Triggering your tests using the Execution Command will be automated.

Image

Step 5: Once you see the Job Link in the logs, you can visit the HyperExecute dashboard to see the tests getting executed.

tip

You can also implement Secret Keys in your YAML file.

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 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.

automation-dashboard

The snapshot below shows the videos, logs and other meta data for that specific test_ID

automation-dashboard

Python​

Running PyTest Framework Tests on HyperExecute​

PyTest is a testing framework for Python that is widely used with Selenium for automated testing. Known for its simplicity and powerful features, Pytest allows efficient test organization, parameterization, and fixtures.

HyperExecute is an AI Native Test Orchestration Cloud Platform that empowers you to run end-to-end tests quickly and efficiently. It provides Just-in-Time (JIT) testing infrastructure with fast execution speeds, smart orchestration, and detailed logs.

Run your PyTest framework tests on HyperExecute via two methods:

1. Testing Using Local System​

Follow the step-by-step guide to execute your test on HyperExecute.

Step 1: Configure Your Test Suite​

You can use your own project to configure and test it. For demo purposes, we are using the sample repository.

Sample repo

Download or Clone the code sample for the JUnit from the TestMu AI GitHub repository to run the tests on the HyperExecute.

Image 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:

capabilities = {
"build": "Sample PY Build",
"platformName": "Windows 11",
"browserName": "Chrome",
"browserVersion": "latest",
}

You can also use dev and beta browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 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 as described in the page-level prerequisites.

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. You can also opt for Matrix or Hybrid mode.
  • Pre and Post commands
  • Reports and Artefacts that will be generated after the completion of tests
  • and other necessary YAML Parameters
---
version: 0.1
globalTimeout: 90
testSuiteTimeout: 90
testSuiteStep: 90

runson: linux

autosplit: true
retryOnFailure: true

maxRetries: 1
concurrency: 2

env:
#  PAT: ${{ .secrets.testKey }}
 TARGET_OS: LINUX

cacheKey: '{{ checksum "requirements.txt" }}'
cacheDirectories:
  - CacheDir
pre:
  - pip install py
  - pip install -r requirements.txt --cache-dir CacheDir
post:
  - cat yaml/linux/pytest_hyperexecute_autosplit_sample.yaml

runtime:
  language: python
  version: "3"

mergeArtifacts: true
uploadArtefacts:
  - name: TestReports
    path:
    - reports/**

report: true
partialReports:
    type: json
    location: reports/
    frameworkName: extent

testDiscovery:
  type: raw
  mode: remote
  command: grep -nri 'class' tests -ir --include=\*.py | sed 's/:.*//'

testRunnerCommand: pytest -s  --verbose --html=reports/report.html $test

jobLabel: [selenium-pytest, linux, autosplit]
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.

Run the below command in your terminal at the root folder of the project:

./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.

./hyperexecute --user undefined --key undefined --config RELATIVE_PATH_OF_YOUR_YAML_FILE
JUnit HyperExecute Terminal LogsJUnit HyperExecute Terminal Logs
Step 5: Monitor the Test Execution​

Visit the HyperExecute Dashboard and check your Job status.

automation-dashboard
Step 6: Download Artifacts and Reports​

HyperExecute also facilitates the provision to download the Artifacts and Reports on your local machine. Click on the corresponding button to download your generated artifacts and reports.

automation-dashboard
2. Testing Using Gitpod​

You can also use the Gitpod platform to execute our sample repository. It will fetch all the sample codebases and trigger the CLI to execute the tests.

Follow the below steps to run Test using Gitpod:

Step 1: Click 'Open in Gitpod' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.

Run in Gitpod

Step 2: Login with TestMu AI 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.

Gitpod popup

Step 3: Choose your preferred editor (we recommend VS Code Editor)

Image

Step 4: As you are running a sample project, Fetching of the Test Scripts, HyperExecute YAML, HyperExecute CLI and Triggering your tests using the Execution Command will be automated.

Image

Step 5: Once you see the Job Link in the logs, you can visit the HyperExecute dashboard to see the tests getting executed.

tip

You can also implement Secret Keys in your YAML file.

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 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.

automation-dashboard

The snapshot below shows the videos, logs and other meta data for that specific test_ID

automation-dashboard

For any query or doubt, please feel free to contact us via 24×7 chat support or you can also drop a mail to support@testmuai.com.
Happy testing!

C#​

Running NUnit Framework Tests on HyperExecute​

NUnit is a testing framework for .NET languages, commonly used with Selenium for automated testing. It provides a structure for organizing and executing tests, supporting features like test fixtures, assertions, and setup/teardown methods.

Run your NUnit framework tests on HyperExecute via two methods:

1. Testing Using Local System​

Follow the step-by-step guide to execute your test on HyperExecute.

Step 1: Configure Your Test Suite​

You can use your own project to configure and test it. For demo purposes, we are using the sample repository.

Sample repo

Download or Clone the code sample for the NUnit from the TestMu AI GitHub repository to run the tests on the HyperExecute.

Image 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:

DesiredCapabilities capabilities = new DesiredCapabilities();
capabilities.SetCapability(CapabilityType.BrowserName, "Chrome");
capabilities.SetCapability(CapabilityType.Version, "96");
capabilities.SetCapability(CapabilityType.Platform, "Windows 10");

You can also use dev and beta browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 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 as described in the common steps above.

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. You can also opt for Matrix or Hybrid mode.
  • Pre and Post commands
  • Reports and Artefacts that will be generated after the completion of tests
  • and other necessary YAML Parameters
---
version: 0.1
globalTimeout: 150
testSuiteTimeout: 150
testSuiteStep: 150

runson: linux

autosplit: true
retryOnFailure: true

maxRetries: 1
concurrency: 2

project: NUnitHyperTestDemo/NUnitHyperTestDemo.csproj
solution: NUnitHyperTestDemo.sln

env:
  NUGET_PACKAGES: '/home/ltuser/.nuget/packages/'
  NUGET_HTTP_CACHE_PATH: '/home/ltuser/.local/share/NuGet/v3-cache'
  NUGET_PLUGINS_CACHE_PATH: '/home/ltuser/.local/share/NuGet/plugins-cache'

pre:
 - dotnet restore
 - dotnet list $project package > packages.txt
 - dotnet build -c Release

post:
  - cat yaml/linux/nunit_hyperexecute_autosplit_sample.yaml

mergeArtifacts: true

uploadArtefacts:
  - name: ExecutionSnapshots
    path:
     - NUnitHyperTestDemo/Reports/**

report: true
partialReports:
    type: json
    location: NUnitHyperTestDemo/
    frameworkName: extent

testDiscovery:
  type: raw
  mode: remote
  command: grep 'Category' NUnitHyperTestDemo -ir --include=\*.cs --exclude=DriverFactory.cs --exclude=HyperTestDemo.AssemblyInfo.cs | awk '{print$2}' | grep -o '".*"'

testRunnerCommand: dotnet test $solution --filter TestCategory=$test 

jobLabel: [selenium-Nunit, linux, autosplit]
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.

Run the below command in your terminal at the root folder of the project:

./hyperexecute --config RELATIVE_PATH_OF_YOUR_YAML_FILE

OR use this command if you have not exported your username and access key in the previous step.

./hyperexecute --user undefined --key undefined --config RELATIVE_PATH_OF_YOUR_YAML_FILE
JUnit HyperExecute Terminal LogsJUnit HyperExecute Terminal Logs
Step 5: Monitor the Test Execution​

Visit the HyperExecute Dashboard and check your Job status.

automation-dashboard
Step 6: Download Artifacts and Reports​

HyperExecute also facilitates the provision to download the Artifacts and Reports on your local machine. Click on the corresponding button to download your generated artifacts and reports.

automation-dashboard
2. Testing Using Gitpod​

You can also use the Gitpod platform to execute our sample repository. It will fetch all the sample codebases and trigger the CLI to execute the tests.

Follow the below steps to run Test using Gitpod:

Step 1: Click 'Open in Gitpod' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.

Run in Gitpod

Step 2: Login with TestMu AI 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.

Gitpod popup

Step 3: Choose your preferred editor (we recommend VS Code Editor)

Image

Step 4: As you are running a sample project, Fetching of the Test Scripts, HyperExecute YAML, HyperExecute CLI and Triggering your tests using the Execution Command will be automated.

Image

Step 5: Once you see the Job Link in the logs, you can visit the HyperExecute dashboard to see the tests getting executed.

tip

You can also implement Secret Keys in your YAML file.

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 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.

automation-dashboard

The snapshot below shows the videos, logs and other meta data for that specific test_ID

automation-dashboard

Ruby​

Running Ruby Framework Tests on HyperExecute​

RSpec is a behavior-driven development (BDD) framework for Ruby commonly used in conjunction with Selenium for automated testing. It facilitates expressive and readable specifications, making it easier to define and manage Selenium test cases. RSpec supports a variety of assertions and provides powerful reporting tools, enhancing the efficiency and clarity of Selenium test scripts written in Ruby.

HyperExecute is an AI Native Test Orchestration Cloud Platform that empowers you to run end-to-end tests quickly and efficiently. It provides Just-in-Time (JIT) testing infrastructure with fast execution speeds, smart orchestration, and detailed logs.

Run your RSpec framework tests on HyperExecute via two methods:

1. Testing Using Local System​

Follow the step-by-step guide to execute your test on HyperExecute.

Step 1: Configure Your Test Suite​

You can use your own project to configure and test it. For demo purposes, we are using the sample repository.

Sample repo

Download or Clone the code sample for the JUnit from the TestMu AI GitHub repository to run the tests on the HyperExecute.

Image 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.

You can also use dev and beta browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 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.

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. You can also opt for Matrix or Hybrid mode.
  • Pre and Post commands
  • Reports and Artefacts that will be generated after the completion of tests
  • and other necessary YAML Parameters
---
version: "0.1"
globalTimeout: 90
testSuiteTimeout: 90
testSuiteStep: 90

runson: linux

autosplit: true
retryOnFailure: true
maxRetries: 1
concurrency: 2

pre:
  - bundle install --deployment

cacheKey: '{{ checksum "Gemfile.lock" }}'
cacheDirectories:
  - /vendor

env:
   CONFIG_NAME: "linux"

testDiscovery:
  type: raw
  mode: remote
  command: grep -nri -E 'it ".*." do' spec/*.rb | awk '{print$1}' | sed 's/\(.*\):/\1 /'

testRunnerCommand: bundle exec rspec "$test" --format html --out rspec_results.html

mergeArtifacts: true
uploadArtefacts:
 - name: report
   path:
     - rspec_results.html

report: true
partialReports:
 location: rspec_results.html
 type: html

jobLabel: [selenium-Rspec, linux, autosplit]
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.

Run the below command in your terminal at the root folder of the project:

./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.

./hyperexecute --user undefined --key undefined --config RELATIVE_PATH_OF_YOUR_YAML_FILE
JUnit HyperExecute Terminal LogsJUnit HyperExecute Terminal Logs
Step 5: Monitor the Test Execution​

Visit the HyperExecute Dashboard and check your Job status.

automation-dashboard
Step 6: Download Artifacts and Reports​

HyperExecute also facilitates the provision to download the Artifacts and Reports on your local machine. Click on the corresponding button to download your generated artifacts and reports.

automation-dashboard
2. Testing Using Gitpod​

You can also use the Gitpod platform to execute our sample repository. It will fetch all the sample codebases and trigger the CLI to execute the tests.

Follow the below steps to run Test using Gitpod:

Step 1: Click 'Open in Gitpod' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.

Run in Gitpod

Step 2: Login with TestMu AI 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.

Gitpod popup

Step 3: Choose your preferred editor (we recommend VS Code Editor)

Image

Step 4: As you are running a sample project, Fetching of the Test Scripts, HyperExecute YAML, HyperExecute CLI and Triggering your tests using the Execution Command will be automated.

Image

Step 5: Once you see the Job Link in the logs, you can visit the HyperExecute dashboard to see the tests getting executed.

tip

You can also implement Secret Keys in your YAML file.

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 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.

automation-dashboard

The snapshot below shows the videos, logs and other meta data for that specific test_ID

automation-dashboard

JavaScript​

WebdriverIO is a widely-used testing framework for Java applications, designed to simplify and enhance the testing process for developers. It provides a flexible and powerful platform for running test suites, enabling effective unit testing, integration testing, and end-to-end testing of Java applications

Run your WebdriverIO framework tests on HyperExecute via two methods:

  • Using Local System - You can use your own local machine to execute tests.
  • Using Gitpod Platform - Execute tests using GitPod. (Requires a Gitpod account)

1. Testing Using Local System​

Follow the step-by-step guide to execute your test on HyperExecute.

Step 1: Configure Your Test Suite​

You can use your own project to configure and test it. For demo purposes, we are using the sample repository.

Sample repo

Download or Clone the code sample for the JUnit from the TestMu AI GitHub repository to run the tests on the HyperExecute.

Image 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:

capabilities: [{
  browserName: 'chrome',
  platform: 'Windows 10',
  version: 'latest',
  name: "single-test",
  build: "wd-lambdatest-sample",
  geoLocation : "US"
}]

You can also use dev and beta browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 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 and set up your environment variables as described in the sections above.

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. You can also opt for Matrix or Hybrid mode.
  • Pre and Post commands
  • Reports and Artefacts that will be generated after the completion of tests
  • and other necessary YAML Parameters
---
version: 0.1
globalTimeout: 150
testSuiteTimeout: 150
testSuiteStep: 150

runson: linux

autosplit: true
retryOnFailure: true

maxRetries: 1
concurrency: 2

pre:
  - npm install

cacheKey: '{{ checksum "package-lock.json" }}'
cacheDirectories:
  - node_modules

mergeArtifacts: true

uploadArtefacts:
  [{
    "name": "Reports",
    "path": ["Reports/*"]
  }]

report: true
partialReports:
    type: json
    location: Reports/
    frameworkName: extent
  
testDiscovery:
  type: automatic
  args:
    featureFilePaths: Features/
    frameWork: java
    specificTags: ["@ToDoOne", "@ToDoTwo", "@ToDoThree"]

testRunnerCommand: npx wdio wdio.conf.js --spec=$test

jobLabel: [selenium-webdriverIO, linux, autosplit]
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.

Run the below command in your terminal at the root folder of the project:

./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.

./hyperexecute --user undefined --key undefined --config RELATIVE_PATH_OF_YOUR_YAML_FILE
JUnit HyperExecute Terminal LogsJUnit HyperExecute Terminal Logs
Step 5: Monitor the Test Execution​

Visit the HyperExecute Dashboard and check your Job status.

automation-dashboard
Step 6: Download Artifacts and Reports​

HyperExecute also facilitates the provision to download the Artifacts and Reports on your local machine. Click on the corresponding button to download your generated artifacts and reports.

automation-dashboard

2. Testing Using Gitpod​

You can also use the Gitpod platform to execute our sample repository. It will fetch all the sample codebases and trigger the CLI to execute the tests.

Follow the below steps to run Test using Gitpod:

Step 1: Click 'Open in Gitpod' button. You will be redirected to Login/Signup page. This button is configured to redirect you to the Gitpod platform where you will be able to execute our sample repository.

Run in Gitpod

Step 2: Login with TestMu AI 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.

Gitpod popup

Step 3: Choose your preferred editor (we recommend VS Code Editor)

Image

Step 4: As you are running a sample project, Fetching of the Test Scripts, HyperExecute YAML, HyperExecute CLI and Triggering your tests using the Execution Command will be automated.

Image

Step 5: Once you see the Job Link in the logs, you can visit the HyperExecute dashboard to see the tests getting executed.

tip

You can also implement Secret Keys in your YAML file.

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 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.

automation-dashboard

The snapshot below shows the videos, logs and other meta data for that specific test_ID

automation-dashboard

Monitor Your Test Execution​

Every test run has a unique jobId. Once the CLI prints the job link, open the HyperExecute Dashboard to watch tests execute in real time, review isolated logs and videos per test, and download artifacts and reports.

Next Steps​

Continue with these related guides:

Last updated on

Test across 3000+ combinations of browsers, real devices & OS.

×
Schedule Your Personal Demo
Book Demo

Help and Support

Related Articles

On this page