HyperExecute GUI App - Speed Simplified
HyperExecute GUI is currently in BETA and supports the Java TestNG Framework (with Java Version 11 or higher). We're actively working on expanding support to more frameworks. If you have specific framework requests, please reach out to our support team.
HyperExecute Graphical User Interface (GUI) is designed to streamline your test automation workflow and bring HyperExecute's power of test orchestration with the most intuitive way to interact. HyperExecute GUI makes testing simple, fast, and powerful. It abstracts all technical complexity to make high-performance test execution available to everyone. The goal is to save your valuable time and effort to enable a more efficient testing process.
Why HyperExecute GUI?
HyperExecute has been a cornerstone for automation testing, offering unparalleled flexibility with its YAML configurations and command-line interface. Now, with HyperExecute GUI, you can experience AI-powered automatic test detection, set up test environments with simple clicks and run your tests without coding.
Pre-Requisites
1. HyperExecute Access : You need a LambdaTest account to use the HyperExecute GUI. If you don’t have one, sign up now. Ensure your account includes HyperExecute access (free or paid plan) to get started.
2. UnderPass App Download : Before getting started, download the HyperExecute GUI installer from your LambdaTest dashboard and install it on your system. Run the installer by following the on-screen instructions and launch HyperExecute GUI from your applications menu.
Currently HyperExecute GUI is a part of the LambdaTest UnderPass Application. If you already have UnderPass app on your system, please update it to the latest version.
You can download the app directly from your HyperExecute Dashboard or simply click the links below based on your operating system:
Demo Walkthrough
For those who prefer a hands-on, visual approach, we’ve created a comprehensive video tutorial to get you up and running quickly. Checkout this video demo which walks you through the step by step process of using the GUI App using a demo project.
All the steps taken in this video are explained in detail in the following step by step guide too.
Getting Started
Step 1: Select and Analyze Your Project
Launch the application, log in with your LambdaTest credentials, and select your test project folder. The GUI will automatically analyze your project i.e.:
- Detect your testing framework and language
- Verifies network connectivity (enabling a tunnel if needed) and checks LambdaTest URL access (prompting for proxy settings if required)
- Set up a secure connection to your account
If you do not have a project handy, please feel free to use this Sample Project for trying out the GUI.
The GUI will check the system and your project to ensure everything is ready. If any issues are found, you'll see clear instructions to resolve them. Some common issues faced by the users are:
- Missing programming language or package manager: If your project uses a language or package manager that isn't installed on your computer, the GUI will guide you through installing it.
- Network connectivity issues: If the GUI can't connect to LambdaTest servers, it will ask you to set up the necessary network settings through proxy.
Step 2: Discover and Select Tests
Once you land on the Project Screen, the app will automatically initiate Test Discovery. Test Discovery is an automated process that scans your project to identify and group all test cases by Suites, Files, Classes or Methods.
This feature eliminates the need for manual test configuration and makes it easy to select which tests to run. Once you have selected the tests from "Test List" tab according to your preferences, either you can directly run the job or move to the next step for additional configuration.
Search within tests is not yet available on the GUI. We are working to make it available soon.
Step 3: Specify Run Config [Optional]
The Run Config tab in HyperExecute GUI offers an intuitive visual interface to configure your test environment and execution settings. You’ll find the basic preset configurations displayed just below your project name. If you need to modify or customize these settings, simply navigate to the Run Config tab and adjust your execution environment effortlessly — no YAML editing required.
To learn about any configuration in detail, please search for the keyword in the HyperExecute YAML Documentation.
Step 4: Run Tests and View Job
Click on the Run Test button to start the test execution. A pop with job status and creation logs will appear with options to Expand and View Job. Click on the View Job button to get redirected to the job dashboard once the job is created. The HyperExecute-GUI displays the job logs in real-time as your tests run. Once complete, you can view the detailed test results in the HyperExecute Dashboard.
Already Using HyperExecute via YAML?
If you’re a HyperExecute YAML user, you can easily import your existing YAML configurations into the GUI. Here’s how:
1. Pop-Up on First Upload:
When you upload a project with YAML files, a pop-up will automatically appear listing the existing YAMLs in your project. Select a YAML file, and the app will import its settings for run config in the GUI.
2. Option to Import After Project Creation:
If your project is already set up or you want to update the run config using a YAML file later:
- Go to the Project Details screen.
- Click “Load Config.”
- Choose a YAML file from your project, and its settings will be applied.
Please note that using "Load Config" will reset your test selection
At its current state, the GUI will not self-discover the tests according to rules stated in the YAML file while loading it. This feature will be available soon in next release.
FAQs
1. Are Appium tests supported on GUI as of now?
No, Appium test support will be coming soon. Currently, the GUI is in beta and primarily supports TestNG framework.
2. If my tests are written using Chrome Driver or any other local driver, can I use that project?
Yes, you can use the project, but the associated test IDs will not be created. You would need to enable the "Screen Recording For Scenarios" key to record the entire scenario execution, with the video accessible from the HyperExecute dashboard. (This is applicable for non-Selenium based tests)
3. If I have a scenario where the project has two folders - one which creates the test dependencies and another which uses those dependencies to run the tests - how can I use that?
You would not be able to use such a project. Please ensure that each project is created from one folder only. We will be supporting this feature in the coming future.
Chat with Us
Ask the Community