Integrate algoQA with HyperExecute

Modified on Wed, 2 Oct at 7:55 PM

TABLE OF CONTENTS

1. Overview

2. Prerequisites 

3. Setting Up your Test Suite

4. Setup Environment Variable

5. Configuring ApplicationSettings.xml file

6. Executing your Tests

7. Monitor the Test Execution

1. Overview

This article provides you on how to integrate your algoQA project with HyperExecute.

2. Prerequisites 

To run the Tests on HyperExecute from your local system, you require:

  • Your LambdaTest Username and Access key.
  • HyperExecute CLI in order to initiate a test execution Job. Download the appropriate operating system link to run the executable file. 
  • Setup the Environment Variable.
  • HyperExecute YAML file which contains all the necessary instructions.

3. Setting Up your Test Suite

You can use your own project to configure and test it or a sample project is attached for you to test it.

After downloading the sample project, you need to setup the CLI and the environment variable.

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:

Platform HyperExecute CLI
Windows https://downloads.lambdatest.com/hyperexecute/windows/hyperexecute.exe
MacOS https://downloads.lambdatest.com/hyperexecute/darwin/hyperexecute
Linuxhttps://downloads.lambdatest.com/hyperexecute/linux/hyperexecute


4. Setting Up Environment Variable

To export your environment variables LT_USERNAME and LT_ACCESS_KEY that are available in the LambdaTest Profile page, run the following commands in your Terminal to setup the CLI and the environment variables in your windows:


5.Configuring YAML in your Test Suite

---
version: 0.1
globalTimeout: 150
testSuiteTimeout: 150
testSuiteStep: 150


runson: win


autosplit: true


retryOnFailure: true
maxRetries: 1


concurrency: 2


cacheKey: '{{ checksum "pom.xml" }}'
cacheDirectories:
  - .m2


pre:
  - mvn -Dmaven.repo.local=./.m2 dependency:resolve


report: true
partialReports:
    type: json
    location: target/
    frameworkName: extent-native
  
uploadArtifacts:
  - name: FinalReport 
    path:
    - ExtentReports/**


testDiscovery:
  type: automatic
  mode: static
  args:
    featureFilePaths: src/test/java/features/
    frameWork: java


testRunnerCommand: mvn test `-Dplatname=win `-Dmaven.repo.local=./.m2 `-Dcucumber.features="$test"


jobLabel: ['HYP', 'algoQA']

 

6. Configuring ApplicationSettings.XML file

algoQA scripts generated follow an organized folder structure. Search and locate the ApplicationsSettings.XML file. For example, you can find Applications.XML file in an algoQA script generated folder for a web automation available at - ScriptGeneration_202310311222.zip\AlgoAFScript_202310311222\src\test\java.
In your ApplicationSettings.xml file, update the following parameters:

  • BrowserType : It  must be Lambda.
  • LambdaTestBuild : Provide your build name.
  • LambdaTestURL : Provide your HUB URL. For example, https://username:access-key@hub.lambdatest.com/wd/hub

6. Executing your Tests

  • Run the following command in your terminal at the root folder of the project:
    ./hyperexecute --config RELATIVE_PATH_OF_YOUR_YAML_FILE
    For example, /hyperexecute.exe --user <username> --key <value> --config <name of the YAML file>
    
    
  • Alternatively, use this command if you have not exported your username and access key in the step 2.

7. Monitoring the Test Execution

Navigate to the HyperExecute Dashboard to verify your Job status, as shown:



















Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article