Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/lambdatest/nunit-selenium-hyperexecute-sample
Demonstration of NUnit Selenium testing on HyperExecute Grid
https://github.com/lambdatest/nunit-selenium-hyperexecute-sample
hyperexecute hypertest lambdatest nunit nunit-framework parallel-testing selenium selenium-csharp selenium-testing selenium-webdriver
Last synced: 2 months ago
JSON representation
Demonstration of NUnit Selenium testing on HyperExecute Grid
- Host: GitHub
- URL: https://github.com/lambdatest/nunit-selenium-hyperexecute-sample
- Owner: LambdaTest
- License: mit
- Created: 2022-03-22T13:05:17.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2023-12-12T07:06:37.000Z (about 1 year ago)
- Last Synced: 2023-12-12T08:24:14.242Z (about 1 year ago)
- Topics: hyperexecute, hypertest, lambdatest, nunit, nunit-framework, parallel-testing, selenium, selenium-csharp, selenium-testing, selenium-webdriver
- Language: C#
- Homepage: https://www.lambdatest.com/hyperexecute
- Size: 148 KB
- Stars: 4
- Watchers: 7
- Forks: 10
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
HyperExecute is a smart test orchestration platform to run end-to-end Selenium tests at the fastest speed possible. HyperExecute lets you achieve an accelerated time to market by providing a test infrastructure that offers optimal speed, test orchestration, and detailed execution logs.
The overall experience helps teams test code and fix issues at a much faster pace. HyperExecute is configured using a YAML file. Instead of moving the Hub close to you, HyperExecute brings the test scripts close to the Hub!
* HyperExecute HomePage: https://www.lambdatest.com/hyperexecute
* Lambdatest HomePage: https://www.lambdatest.com
* LambdaTest Support: [[email protected]](mailto:[email protected])
To know more about how HyperExecute does intelligent Test Orchestration, do check out [HyperExecute Getting Started Guide](https://www.lambdatest.com/support/docs/getting-started-with-hyperexecute/)
[
](https://hyperexecute.lambdatest.com/?utm_source=github&utm_medium=repository&utm_content=csharp&utm_term=nunit)
## Gitpod
Follow the below steps to run Gitpod button:
1. Click '**Open in Gitpod**' button (You will be redirected to Login/Signup page).
2. Login with Lambdatest credentials and it will be redirected to Gitpod editor in new tab and current tab will show hyperexecute dashboard.
[
](https://hyperexecute.lambdatest.com/hyperexecute/jobs?type=gitpod&framework=NUnit)
---
# How to run Selenium automation tests on HyperExecute (using NUnit framework)
* [Pre-requisites](#pre-requisites)
- [Download HyperExecute CLI](#download-hyperexecute-cli)
- [Configure Environment Variables](#configure-environment-variables)
* [Matrix Execution with NUnit](#matrix-execution-with-nunit)
- [Core](#core)
- [Pre Steps and Dependency Caching](#pre-steps-and-dependency-caching)
- [Post Steps](#post-steps)
- [Artifacts Management](#artifacts-management)
- [Test Execution](#test-execution)
* [Auto-Split Execution with NUnit](#auto-split-execution-with-nunit)
- [Core](#core-1)
- [Pre Steps and Dependency Caching](#pre-steps-and-dependency-caching-1)
- [Post Steps](#post-steps-1)
- [Artifacts Management](#artifacts-management-1)
- [Test Execution](#test-execution-1)
* [Secrets Management](#secrets-management)
* [Navigation in Automation Dashboard](#navigation-in-automation-dashboard)
# Pre-requisites
Before using HyperExecute, you have to download HyperExecute CLI corresponding to the host OS. Along with it, you also need to export the environment variables *LT_USERNAME* and *LT_ACCESS_KEY* that are available in the [LambdaTest Profile](https://accounts.lambdatest.com/detail/profile) page.
## Download HyperExecute CLI
HyperExecute CLI is the CLI for interacting and running the tests on the HyperExecute Grid. The CLI provides a host of other useful features that accelerate test execution. In order to trigger tests using the CLI, you need to download the HyperExecute CLI binary corresponding to the platform (or OS) from where the tests are triggered:
Also, it is recommended to download the binary in the project's parent directory. Shown below is the location from where you can download the HyperExecute CLI binary:
* Mac: https://downloads.lambdatest.com/hyperexecute/darwin/hyperexecute
* Linux: https://downloads.lambdatest.com/hyperexecute/linux/hyperexecute
* Windows: https://downloads.lambdatest.com/hyperexecute/windows/hyperexecute.exe
## Configure Environment Variables
Before the tests are run, please set the environment variables LT_USERNAME & LT_ACCESS_KEY from the terminal. The account details are available on your [LambdaTest Profile](https://accounts.lambdatest.com/detail/profile) page.
For macOS:
```bash
export LT_USERNAME=LT_USERNAME
export LT_ACCESS_KEY=LT_ACCESS_KEY
```
For Linux:
```bash
export LT_USERNAME=LT_USERNAME
export LT_ACCESS_KEY=LT_ACCESS_KEY
```
For Windows:
```bash
set LT_USERNAME=LT_USERNAME
set LT_ACCESS_KEY=LT_ACCESS_KEY
```
The HYPERXECUTE_PLATFORM environment variable must be set to the platform (or operating system) on which you wish to perform the test execution. Here are the values that can be assigned to HYPEREXECUTE_PLATFORM
* win10 for Windows OS
* linux for Linux OS
* macOS Catalina for macOS
Use the commands mentioned below, to set the HyperExecute Platform (i.e. HYPEREXECUTE_PLATFORM) to Linux, macOS, or Windows respectively:
Host OS: Linux
```bash
export HYPERXECUTE_PLATFORM=win10
export HYPERXECUTE_PLATFORM=linux
export HYPERXECUTE_PLATFORM=macOS Catalina
```
Host OS: macOS
```bash
export HYPERXECUTE_PLATFORM=win10
export HYPERXECUTE_PLATFORM=linux
export HYPERXECUTE_PLATFORM=macOS Catalina
```
Host OS: Windows
```bash
set HYPERXECUTE_PLATFORM=wind10
set HYPERXECUTE_PLATFORM=linux
set HYPERXECUTE_PLATFORM=macOS Catalina
```
# Matrix Execution with NUnit
Matrix-based test execution is used for running the same tests across different test (or input) combinations. The Matrix directive in HyperExecute YAML file is a *key:value* pair where value is an array of strings.
Also, the *key:value* pairs are opaque strings for HyperExecute. For more information about matrix multiplexing, check out the [Matrix Getting Started Guide](https://www.lambdatest.com/support/docs/getting-started-with-hyperexecute/#matrix-based-build-multiplexing)
### Core
In the current example, matrix YAML file (*yaml/nunit_hyperexecute_matrix_sample.yaml*) in the repo contains the following configuration:
```yaml
globalTimeout: 150
testSuiteTimeout: 150
testSuiteStep: 150
```
Global timeout, testSuite timeout, and testSuite timeout are set to 150 minutes.
The target platform is set to Windows. Please set the *[runson]* key to *[mac]* if the tests have to be executed on the macOS platform.
```yaml
runson: win
```
The *matrix* constitutes of the following entries - *project* and *testmethods*. This is because parallel execution will be achieved at the method level.
```yaml
matrix:
project: ["NUnitHyperTestDemo/NUnitHyperTestDemo.csproj"]
testmethods: ["ToDoTest", "SeleniumPlayGround"]
```
The *testSuites* object contains a list of commands (that can be presented in an array). In the current YAML file, commands for executing the tests are put in an array (with a '-' preceding each item). The [*dotnet test*](https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-test) command is used to run tests located in the current project. In the current project, parallel execution is achieved at the *test method* level.
```yaml
testSuites:
- dotnet test $project --filter "(Category=$testmethods)"
```
### Pre Steps and Dependency Caching
Dependency caching is enabled in the YAML file to ensure that the package dependencies are not downloaded in subsequent runs. The first step is to set the Key used to cache directories.
```yaml
cacheKey: '{{ checksum "packages.txt" }}'
```
Set the array of files & directories to be cached. Separate folders are created for downloading global-packages, http-cache, and plugins-cache. Pleas refer to [Configuring NuGet CLI environment variables](https://docs.microsoft.com/en-us/nuget/reference/cli-reference/cli-ref-environment-variables) to know more about overriding settings in NuGet.Config files.
```yaml
NUGET_PACKAGES: 'C:\nuget_global_cache'
NUGET_HTTP_CACHE_PATH: 'C:\nuget_http_cache'
NUGET_PLUGINS_CACHE_PATH: 'C:\nuget_plugins_cache'
```
Steps (or commands) that must run before the test execution are listed in the *pre* run step. In the example, the necessary NuGet packages are fetched using the [*dotnet list package*](https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-list-package) command. All the local packages are cleared using the *nuget locals all -clear* command, post which the entire project is built from scratch using the *dotnet build -c Release* command.
```yaml
pre:
# https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-list-package
- dotnet list $project package > packages.txt
- nuget locals all -clear
- dotnet build -c Release
```
### Post Steps
Steps (or commands) that need to run after the test execution are listed in the *post* step. In the example, we *cat* the contents of *yaml/nunit_hyperexecute_matrix_sample.yaml*
```yaml
post:
- cat yaml/nunit_hyperexecute_matrix_sample.yaml
```
### Artifacts Management
The *mergeArtifacts* directive (which is by default *false*) is set to *true* for merging the artifacts and combing artifacts generated under each task.
The *uploadArtefacts* directive informs HyperExecute to upload artifacts [files, reports, etc.] generated after task completion. In the example, *path* consists of a regex for parsing the directory (i.e. *NUnitHyperTestDemo/Reports* that contains the test reports).
```yaml
mergeArtifacts: true
uploadArtefacts:
- name: ExecutionSnapshots
path:
- NUnitHyperTestDemo/Reports/**
```
HyperExecute also facilitates the provision to download the artifacts on your local machine. To download the artifacts, click on Artifacts button corresponding to the associated TestID.
Now, you can download the artifacts by clicking on the Download button as shown below:
## Test Execution
The CLI option *--config* is used for providing the custom HyperExecute YAML file (i.e. *yaml/nunit_hyperexecute_matrix_sample.yaml*). Run the following command on the terminal to trigger the tests in C# files on the HyperExecute grid. The *--download-artifacts* option is used to inform HyperExecute to download the artifacts for the job. The *--force-clean-artifacts* option force cleans any existing artifacts for the project.
```bash
./hyperexecute --config yaml/nunit_hyperexecute_matrix_sample.yaml --force-clean-artifacts --download-artifacts
```
Visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/hypertest) to check the status of execution:
Shown below is the execution screenshot when the YAML file is triggered from the terminal:
## Auto-Split Execution with NUnit
Auto-split execution mechanism lets you run tests at predefined concurrency and distribute the tests over the available infrastructure. Concurrency can be achieved at different levels - file, module, test suite, test, scenario, etc.
For more information about auto-split execution, check out the [Auto-Split Getting Started Guide](https://www.lambdatest.com/support/docs/getting-started-with-hyperexecute/#smart-auto-test-splitting)
### Core
Auto-split YAML file (*yaml/nunit_hyperexecute_autosplit_sample.yaml*) in the repo contains the following configuration:
```yaml
globalTimeout: 150
testSuiteTimeout: 150
testSuiteStep: 150
```
Global timeout, testSuite timeout, and testSuite timeout are set to 150 minutes.
The *runson* key determines the platform (or operating system) on which the tests are executed. Here we have set the target OS as Windows.
```yaml
runson: win
```
Auto-split is set to true in the YAML file.
```yaml
autosplit: true
```
*retryOnFailure* is set to true, instructing HyperExecute to retry failed command(s). The retry operation is carried out till the number of retries mentioned in *maxRetries* are exhausted or the command execution results in a *Pass*. In addition, the concurrency (i.e. number of parallel sessions) is set to 2.
```yaml
retryOnFailure: true
maxRetries: 5
concurrency: 2
```
## Pre Steps and Dependency Caching
Dependency caching is enabled in the YAML file to ensure that the package dependencies are not downloaded in subsequent runs. The first step is to set the Key used to cache directories.
```yaml
cacheKey: '{{ checksum "packages.txt" }}'
```
Set the array of files & directories to be cached. Separate folders are created for downloading global-packages, http-cache, and plugins-cache. Pleas refer to [Configuring NuGet CLI environment variables](https://docs.microsoft.com/en-us/nuget/reference/cli-reference/cli-ref-environment-variables) to know more about overriding settings in NuGet.Config files.
```yaml
NUGET_PACKAGES: 'C:\nuget_global_cache'
NUGET_HTTP_CACHE_PATH: 'C:\nuget_http_cache'
NUGET_PLUGINS_CACHE_PATH: 'C:\nuget_plugins_cache'
```
## Post Steps
The *post* directive contains a list of commands that run as a part of post-test execution. Here, the contents of *yaml/nunit_hyperexecute_autosplit_sample.yaml* are read using the *cat* command as a part of the post step.
```yaml
post:
- cat yaml/nunit_hyperexecute_autosplit_sample.yaml
```
The *testDiscovery* directive contains the command that gives details of the mode of execution, along with detailing the command that is used for test execution. Here, we are fetching the list of test methods that would be further passed in the *testRunnerCommand*
```yaml
testDiscovery:
type: raw
mode: static
command: grep 'Category' NUnitHyperTestDemo -ir --include=\*.cs --exclude=DriverFactory.cs --exclude=HyperTestDemo.AssemblyInfo.cs | awk '{print$2}' | grep -o '".*"'
```
Running the above command on the terminal will give a list of test methods:
* "ToDoTest"
* "SeleniumPlayGround"
The *testRunnerCommand* contains the command that is used for triggering the test. The output fetched from the *testDiscoverer* command acts as an input to the *testRunner* command.
```yaml
testRunnerCommand: dotnet test $solution --filter TestCategory=$test
```
### Artifacts Management
The *mergeArtifacts* directive (which is by default *false*) is set to *true* for merging the artifacts and combing artifacts generated under each task.
The *uploadArtefacts* directive informs HyperExecute to upload artifacts [files, reports, etc.] generated after task completion. In the example, *path* consists of a regex for parsing the directory (i.e. *NUnitHyperTestDemo/Reports* that contains the test reports).
```yaml
mergeArtifacts: true
uploadArtefacts:
- name: ExecutionSnapshots
path:
- NUnitHyperTestDemo/Reports/**
```
HyperExecute also facilitates the provision to download the artifacts on your local machine. To download the artifacts, click on Artifacts button corresponding to the associated TestID.
Now, you can download the artifacts by clicking on the Download button as shown below:
### Test Execution
The CLI option *--config* is used for providing the custom HyperExecute YAML file (i.e. *yaml/nunit_hyperexecute_autosplit_sample.yaml*). Run the following command on the terminal to trigger the tests in C# files on the HyperExecute grid. The *--download-artifacts* option is used to inform HyperExecute to download the artifacts for the job. The *--force-clean-artifacts* option force cleans any existing artifacts for the project.
```bash
./hyperexecute --config yaml/nunit_hyperexecute_autosplit_sample.yaml --force-clean-artifacts --download-artifacts
```
Visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/hypertest) to check the status of execution
Shown below is the execution screenshot when the YAML file is triggered from the terminal:
## Secrets Management
In case you want to use any secret keys in the YAML file, the same can be set by clicking on the *Secrets* button the dashboard.
Now create a *secret* key that you can use in the HyperExecute YAML file.
All you need to do is create an environment variable that uses the secret key:
```yaml
env:
PAT: ${{ .secrets.testKey }}
```
## Navigation in Automation Dashboard
HyperExecute lets you navigate from/to *Test Logs* in Automation Dashboard from/to *HyperExecute Logs*. You also get relevant get relevant Selenium test details like video, network log, commands, Exceptions & more in the Dashboard. Effortlessly navigate from the automation dashboard to HyperExecute logs (and vice-versa) to get more details of the test execution.
Shown below is the HyperExecute Automation dashboard which also lists the tests that were executed as a part of the test suite:
Here is a screenshot that lists the automation test that was executed on the HyperExecute grid:
## LambdaTest Community :busts_in_silhouette:
The [LambdaTest Community](https://community.lambdatest.com/) allows people to interact with tech enthusiasts. Connect, ask questions, and learn from tech-savvy people. Discuss best practises in web development, testing, and DevOps with professionals from across the globe.
## Documentation & Resources :books:
If you want to learn more about the LambdaTest's features, setup, and usage, visit the [LambdaTest documentation](https://www.lambdatest.com/support/docs/). You can also find in-depth tutorials around test automation, mobile app testing, responsive testing, manual testing on [LambdaTest Blog](https://www.lambdatest.com/blog/) and [LambdaTest Learning Hub](https://www.lambdatest.com/learning-hub/).
## About LambdaTest
[LambdaTest](https://www.lambdatest.com) is a leading test execution and orchestration platform that is fast, reliable, scalable, and secure. It allows users to run both manual and automated testing of web and mobile apps across 3000+ different browsers, operating systems, and real device combinations. Using LambdaTest, businesses can ensure quicker developer feedback and hence achieve faster go to market. Over 500 enterprises and 1 Million + users across 130+ countries rely on LambdaTest for their testing needs.
[
](https://accounts.lambdatest.com/register)
## We are here to help you :headphones:
* Got a query? we are available 24x7 to help. [Contact Us](mailto:[email protected])
* For more info, visit - https://www.lambdatest.com