Skip to main content

GitHub Actions Pipeline Integration with Hyperexecute

GitHub Actions is a continuous integration and continuous delivery (CI/CD) platform that allows you to automate your build, test, and deployment pipeline. You can create workflows that build and test every pull request to your repository, or deploy merged pull requests to production.

This document will show you how to integrate GitHub Actions Pipeline with HyperExecute to greatly shorten your test cycles.

How To Integrate GitHub Actions Pipeline with Hyperexecute

To integrate GitHub Actions Pipeline with HyperExecute, follow the below steps:

1. Log into your GitHub account

  • Navigate to the main page of the repository.
  • Under your repository name, click Actions.

2. Create a New Workflow

In the left sidebar, click the New workflow button.

Create New Project

3. Create the GitHub Actions work-flow YAML file:

To create the GitHub Actions pipeline YAML file, follow the sample command below:

name: Hyperexecute-Playwright
required: true
description: LT Username
description: LT Access Key
required: true
description: Link to the HyperExecute sample repo
required: true
runs-on: ${{ matrix.os }}
timeout-minutes: 15
fail-fast: false
os: [windows-latest]
- name: Checkout sources
uses: actions/checkout@v2

- name: Starting CLI testing
shell: bash
run: |
echo "STEP 1 ) Downloading sample suite"
git clone ${{ github.event.inputs.sampleRepoLink }}
echo "STEP 2) Download CLI and setting environment variables"
cd HyperExecute-Playwright-Vanilla-Javascript
curl -o hyperexecute.exe
export LT_USERNAME=${{ github.event.inputs.username }}
export LT_ACCESS_KEY=${{ github.event.inputs.accessKey }}
./hyperexecute --user $LT_USERNAME --key $LT_ACCESS_KEY --config yaml/win/.hyperexecute_autosplits.yaml

  • On:
    • Workflow_dispatch: In the workflow_dispatch section, you should declare the pre-defined variables that will be used before running the GitHub Actions PipeLine as an input.
  • Jobs: In the Jobs Section, declare the workflow of the pipeline execution.
    • runs-on: Runs-on contains the value of the OS flavor you would like to execute the GitHub Actions Pipeline on.
  • Steps: In the steps section, you should declare the execution commands.
    • The first step in the above sample YAML changes the path of the root directory.
    • In the second step it downloads the HyperExecute CLI binary.
    • The third step is the execution command which executes The Hyperexecute CLI binary. This contains LambdaTest username, access key, and path of the Yaml created for Hyperexecute. You can find more information on this here.
Create New Pipeline

4. Run the Workflow

To run the new pipeline that you just created, click the Run workflow button on the workflow page.

Create New Project

Below is an example of how a test that is run on the GitHub Actions pipeline gets executed:

Create New Project

Below is an example of a Hyperexecute job that was triggered through the above pipeline:

Create New Project

Run your tests at speeds never seen before. Happy testing! :)