https://store-images.s-microsoft.com/image/apps.48806.bfe0eca3-0536-4d92-b476-3a89886d605d.f5be727d-b9dc-404a-90cc-92f30f16d584.1c49a7aa-3e63-45d7-ac82-bd89b74b4a20
HyperExecute Private Cloud - End-to-End Test Execution and Orchestration
LambdaTest Inc
HyperExecute Private Cloud - End-to-End Test Execution and Orchestration
LambdaTest Inc
HyperExecute Private Cloud - End-to-End Test Execution and Orchestration
LambdaTest Inc
On-prem Selenium / Cypress / Playwright Test Execution and orchestration at the lightning-fast speed
One of the biggest challenges developers and testers face is the speed of test execution and the lack of smart test orchestration. But, so far, customers had only two options—depend on traditional cloud-based grids that haven’t really innovated to fulfill present demands or build their own in-house infrastructure.
Existing test execution solutions are inherently slow because of lots of network hops that happen during each test— triggered test scenarios are first sent to the automation hub, which in turn are scheduled to run on the best-suited automation node— resulting in unnecessary latency. Also, multiple network hops with separated components result in increased test flakiness.
On the other hand, local setups don’t have the smart features that can be offered on the cloud. It has always been a trade-off for customers.
HyperExecute by LambdaTest is a lightning-quick intelligent end-to-end test execution and orchestration platform that is framework and language agnostic. It is up to 70% faster than any cloud-based test execution grid. HyperExecute reduces developer friction and interrupts and ultimately helps businesses release features/products quicker.
HyperExecute achieves in-house-like performance by merging all the components into a single execution environment, thereby ensuring all the components ‘talk’ to each other just like they do in a local network
High-performing, highly scalable, and with intelligent features, the platform takes care of executing your tests in the least time possible so that you can focus on crafting your test cases. With smart features such as auto-grouping, auto-retry, and fail-fast mechanisms, HyperExecute takes away all the pain to run tests leaving the developers/testers to focus on other important tasks.
Through a simple YAML file, HyperExecute allows one to group and distribute tests intelligently across runner environments. This intelligent test orchestration takes into account past test run data, and automatically reorders the test runs to surface failures faster and thus cuts down developer feedback time.
HyperExecute ensures that all test execution data is available on a single platform thereby allowing teams to truly analyze the quality of their builds through insightful automatic reports generated for each build run.
HyperExecute’s other noteworthy features include artifacts management, automatic tunnel management, customizable test environments, dependency caching, etc.
Prerequisites
1) Resource provider
The following resource provider must be registered to install HyperExecute successfully.
- Microsoft.Compute
- Microsoft.OperationsManagement
Please follow this link to register a resource provider.
2) 'EnablePodIdentityPreview` Preview feature
- We use AAD Pod Identity feature to enable Kubernetes applications to access cloud resources securely with Azure Active Directory.
- To use this feature(preview), we need to register the `EnablePodIdentityPreview` feature. Please follow this link to register the preview feature.
3) CPU Quotas
In order to successfully deploy HyperExecute, we need to increase VM-family vCPU quotas. Please follow this link to increase the quotas
- Quota name - Standard DSv3 Family vCPUs. vCPU core count - 80
- Quota name - Standard FSv2 Family vCPUs. vCPU core count - 8 * no of parallel licenses.
Post deployment actions
1) VNet Peering and VNet Links
You need to provision a certain public machine inside the Vnet to access this private setup in your environment. This setup cannot access your private applications, URLs, and APIs directly due to the measures set in place for optimal security.
To solve this issue, we need to perform Vnet peering from the Vnet that is created inside the HyperExecute dedicated resource group to the Vnet that is already present in your account. This account must be the one which contains all of your endpoints, or your test execution account, as the test machines need to access those endpoints. You can enable Vnet peering and Vnet linking in your account by following the process documented on this link
Product Version : 1.138.0
https://store-images.s-microsoft.com/image/apps.11664.bfe0eca3-0536-4d92-b476-3a89886d605d.0d1d4aac-89f0-4e40-980e-1bffc8471d98.80a464c8-d8ea-4ad9-94eb-d48c814b0e2d
https://store-images.s-microsoft.com/image/apps.11664.bfe0eca3-0536-4d92-b476-3a89886d605d.0d1d4aac-89f0-4e40-980e-1bffc8471d98.80a464c8-d8ea-4ad9-94eb-d48c814b0e2d
https://store-images.s-microsoft.com/image/apps.8498.bfe0eca3-0536-4d92-b476-3a89886d605d.0d1d4aac-89f0-4e40-980e-1bffc8471d98.a4183f76-aaf0-4ee1-9038-9fe54c17fa23
https://store-images.s-microsoft.com/image/apps.9909.bfe0eca3-0536-4d92-b476-3a89886d605d.0d1d4aac-89f0-4e40-980e-1bffc8471d98.3d86d797-1ac7-44f9-b2e8-7b7e634a6c38
https://store-images.s-microsoft.com/image/apps.49584.bfe0eca3-0536-4d92-b476-3a89886d605d.0d1d4aac-89f0-4e40-980e-1bffc8471d98.f77f9cf7-dd87-492b-a03f-3bfe68961e00
https://store-images.s-microsoft.com/image/apps.28919.bfe0eca3-0536-4d92-b476-3a89886d605d.0d1d4aac-89f0-4e40-980e-1bffc8471d98.31168dfc-36e3-41b6-b3df-12d14de0c997