Skip to main content

Running Your First Job on HyperExecute

This page outlines how you can run your first test execution job on HyperExecute.

Before you start​

We recommend to run your first test execution job using a sample project on HyperExecute. This can be done in 3 different ways as mentioned below:

  1. Using Quick Run - Execute tests directly from the HyperExecute Portal. (Recommended for new users)
  2. Using Local System - Execute tests from your Local System. (Requires HyperExecute CLI)
  3. Using GitPod - Execute tests using GitPod. (Requires a GitPod account)

1. Using Quick Run​

As you are running tests directly from the HyperExecute GUI, you don't need to do anything. The platform automatically gets the instructions from the HyperExecute YAML file and starts the execution using the HyperExecute CLI.

  1. Go to the Quickstart page.

  2. Select your preferred test automation framework and hit Get Started.

    Image

  3. You can overwrite the HyperExecute YAML here (Optional). Otherwise just click on Trigger test to run your first job.

    Image

  4. At this step the test execution is initiated using the HyperExecute CLI in the background.

    Image

  5. Click on View Test Result to navigate to HyperExecute Dashboard where you can see the job getting executed and the test results.

    Image

2. Using Local System​

Image

To run your Test Scripts on HyperExecute from you Local system, you'll need the following:

We will be taking care of everything one by one, just follow the steps given below:

  1. Go to the Quickstart page.

  2. Choose your test automation framework, Select Run on Local System and click on Get Started.

    Image

  3. Download a sample project by clicking on Code Sample. (Skip this step if you already have a project you want to test)

    Image

  4. Download the HyperExecute CLI as per the OS that you are on.

    Image

  5. Select the OS on which you want to run your tests and then download the HyperExecute YAML file shown on screen. This contains all the configurations required for running tests on HyperExecute.

    ImageImage

    Note: Your Yaml file should be in the root directory of your project. If you are renaming it, also change the file name in the execution script as well. You can learn more about the advanced configurations here, however for the given sample projects you can simply download the file using the small icon on top right.

  6. In order to run your tests, copy the command from screen and run in your terminal:

    Image

  7. The generic command required to initiate test execution is given below. You will need to insert the Username, Access key and name of your YAML file in place of the <your_username>, <your_acess_key> and <your_yaml_file_name> before running this command. (Skip if you already used the command from Step 6. )

    ./hyperexecute --user <your_username> --key <your_access_key> --config <your_yaml_file_name>"

    In case of MAC, 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.

  8. When you run this command, the HyperExecute CLI will send your test scripts to the HyperExecute Platform for execution across multiple parallel Test Execution Nodes.

  9. Once your Job is running, you can click on View Test Results to navigate to HyperExecute Dashboard where you can see the job getting executed along with the test results.

    Image

If you are facing any issues in running your first job? Watch our Webinar Video

3. Using Gitpod​

  1. Go to the Quickstart page.

  2. Choose your test automation framework, select Run test on Gitpod and click on Get Started.

    Image

  3. You will need to login into your Gitpod account, or create a new one.
    (If you are creating a new account, choose your preferred editor. We recommend VS Code)

    Image

  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.

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

HyperExecute Webinar Video​

Last updated on