Selenium Grid in the Cloud

I used Selenium Grid in the Cloud  around five to six years ago, and I have more than four to five years of experience with it.

My main use case for Selenium Grid in the Cloud  is running parallel execution, and I want to ensure that my test cases run smoothly on a headless browser on a Linux system.

I use Selenium Grid in the Cloud for running my test cases by managing multiple instances for 5,000 to 10,000 test cases that must run on multiple locales. Since the test case count is huge, execution was taking around one or two days. I addressed that challenge by dividing my load across multiple environments, specifically multiple instances of AWS , where I created multiple instances and ran all scripts on individual machines with the power of Linux. This ultimately reduced the execution time to two hours, which was a success story for our execution by using the cloud for parallel testing.

The best features Selenium Grid in the Cloud offers include the hub and nodes setup, where the hub controls everything on a single machine as the main execution center, and nodes act as supportive machines for distributing load. Running test cases in parallel is a major feature. I also explored another tool called Zelenium, which has very stable features for running tests in parallel without any hassle by providing easy-to-run access.

Selenium Grid in the Cloud has positively impacted my organization by significantly reducing execution time. Previously it was taking around 30 to 35 hours, but now it is reduced to two to three hours, which allows more time for decision-making. The ability to collect reports from individual machines and execution data easily is very good, making it a proud moment for us with respect to speed and efficiency improvements.

There are several areas where Selenium Grid in the Cloud can be improved, particularly regarding connectivity issues. There are challenges with scripts getting stuck, which causes nodes to become unresponsive. Exploring features that Playwright has would be beneficial, such as threading of execution and load balancing, which would enhance performance. Furthermore, good integration with the latest tools and AI capabilities is needed for better functionality.

I have been working in my current field for 15 years.

When considering scalability, having a good Kubernetes  cluster with an open-source cloud like AWS  has fantastic scalability, but a physical structure for execution can be risky and labor-intensive.

I have never tried the customer support. For customer support, I would rate it a six.

Positive

Before choosing Selenium Grid in the Cloud, I created my own solution for my execution needs.

While Selenium Grid in the Cloud had many problems during development, I eventually stopped using it and created a customized solution, which yielded a good percentage of success.

I have seen a good return on investment, especially when skilled employees tackle real business problems. A skilled employee knows the business well. The importance of having skilled resources over generic tools is evident since tooling might not always yield a high success rate.

In my experience, many organizations prioritize open-source technology over pricing or initial setup costs to customize their systems based on needs. There are challenges with existing setups that can introduce rigidity, which makes businesses struggle.

My advice for others looking into using Selenium Grid in the Cloud is to first understand your business scenario and custom needs. Conducting a trial period or proof of concept is essential before fully committing, as it may pose challenges for new businesses.

I always recommend using stable and open-source solutions. Skilled employees are beneficial for reducing costs, but if resources are lacking, investing in initial tools to solve business problems is critical, as finding skilled labor can pose challenges. I would rate this review overall a six.

I run Selenium Grid in the Cloud  test cases using Selenium Grid in the Cloud  in AWS  to increase parallelization in automation test cases.

I have four nodes set up with Selenium Grid in the Cloud in AWS , which gives us a total of around 12 parallel Chrome Edge browsers. We trigger our Selenium Grid in the Cloud test cases from Jenkins  in those grids, which executes our test cases.

Execution time depends on how many test cases we have. If our number of test cases is higher, we increase the nodes.

Selenium Grid in the Cloud reduces our execution time by providing more Chrome browsers.

It gives more control over how we want to execute and how many nodes we want to add. We don't have any higher number of limits and can add as much capacity as needed in terms of execution frequency. It provides more flexibility towards the grid on our premises, so we don't have to rely on third-party providers.

Selenium Grid in the Cloud helps us reduce execution time for automation and gives us the ability to deliver faster.

We should have support from AWS or other cloud providers which can help us integrate Selenium Grid in the Cloud more easily.

Selenium should introduce some setting configurations at the grid level with Selenium Grid in the Cloud, which we can configure for increasing or decreasing nodes.

I have used Selenium Grid in the Cloud for around two years.

Selenium Grid in the Cloud is stable.

We can scale very fast with Selenium Grid in the Cloud by adding a number of nodes. If we have a single requirement, we can still operate using Selenium Grid in the Cloud. If we have a large-scale requirement, we can add a number of nodes, which gives large scalability to Selenium Grid in the Cloud.

Selenium Grid in the Cloud is easy to set up and easy to scale. We have full control over the tool and can configure it as we require.

We have seen return on investment as Selenium Grid in the Cloud reduces execution time.

We don't have rough numbers, but it saved 90% of time with Selenium Grid in the Cloud.

There is no pricing for Selenium Grid in the Cloud, as it is open source.

Selenium Grid in the Cloud is open source, so documentation is good and we don't face any issues. The overall review rating for this solution is 8.