How to configure Operating System and Browser in your Test Suite

This documentation will guide you through configuring the Operating System and Browser for your test suite on HyperExecute. We will cover the step-by-step method to implement the configuration for various test frameworks supported by HyperExecute. Each section provides practical examples to help you integrate HyperExecute with your existing automation suite.

For demonstration purposes, we use the TestNG sample repository. However, you can apply the same concepts to your preferred framework. You can access the sample repositories for your required frameworks:

Selenium

• TestNG
• JUnit
• Cucumber

• WebdriverIO
• Protractor
• Nightwatch

• NUnit
• SpecFlow

• PyUnit
• PyTest
• Robot
• Behave

• Ruby
• Capybara

Playwright

• JUnit

• VanillaJs
• CodeceptJs
• Jest

• .Net

• Python
• PyTest

Puppeteer

• Jest
• Mocha
• CodeceptJs

Cypress

• Cypress v9
• Cypress v10

Appium

• Mobile Application
• Emulator

Espresso

• Espresso

Maestro

• Maestro
• Emulator
• Simulator

XCUI

• XCUI

Step 1: Update LambdaTest Capabilities in your test suite

Configuring the capabilities is the first step to define the environment for your tests. These capabilities allow you to specify parameters such as the Operating System, Browser, and Browser Version on which your tests will run. LambdaTest capabilities serve as a bridge between your test framework and the HyperExecute cloud infrastructure.

Key Attributes to Configure

• platform : Specifies the operating system (e.g., Windows, macOS, or Linux).
• browserName : Indicates the browser to be used (e.g., Chrome, Firefox, or Edge).
• version : Defines the specific version or sets it as latest to always use the most recent version.

Below is a Java example using the TestNG framework:

Test.java

DesiredCapabilities caps = new DesiredCapabilities();
caps.setCapability("platform", "Windows");
caps.setCapability("browserName", "Chrome");
caps.setCapability("version", "latest"); //latest, dev, beta, latest-1, latest-2, ...

The above configuration ensures that your tests run on Windows OS using the latest version of Google Chrome.

Step 2: Configure your HyperExecute YAML file

The HyperExecute YAML configuration file is the blueprint for running your tests in the HyperExecute cloud environment. It defines the testing environment, execution strategy, and resource allocation. Properly configuring this file ensures that your tests are executed efficiently across the desired platforms and browsers.

AutoSplit

AutoSplit mode automatically splits your scenarios among the concurrent number of tasks and executes them parallelly. This ensures optimal utilization of resources and significantly reduces the overall execution time of your test suite.

In this method, you simply set the runson flag to specify the Operating System for running your tests.

hyperexecute_autosplit.yaml

runson: linux #linux, win, win11, mac, mac13

📕 Learn more about AutoSplit Test Method

Matrix

Matrix mode allows you to run the same set of tests across multiple combinations of environments, configurations, or parameters. This is particularly useful for ensuring that your software works correctly under different conditions, such as various operating systems, browser versions, or dependency files.

• runson: ${matrix.os} : Dynamically selects the operating system from the matrix.os list (Windows, macOS, Linux) for each test job.
• os : Lists the operating systems for testing: win, win11, mac, mac13, and linux.

hyperexecute_matrix.yaml

runson: ${matrix.os}

matrix:
  os: ["win", "mac", "linux"] #linux, win, win11, mac, mac13

📕 Learn more about Matrix Test Method