My main use case for Selenium Grid in the Cloud is testing the applications that I'm developing in an integrated, user-facing sort of environment. I had set up Selenium Grid in the Cloud on which we were running our application, and we had automated some tests using a common framework. It was Node.js based and we used Selenium Grid in the Cloud to test that across various browsers and various versions of these browsers so that we could ensure compatibility for our end users and also ensure that our app worked as intended.

The best features Selenium Grid in the Cloud offers include being able to test the application from a user perspective. Testing from a user perspective stands out as a feature for me, and I find parallel execution and cross-browser support to be basic—not having those is a deal-breaker for me.

Selenium Grid in the Cloud by itself does not provide any reporting. Mostly it's the frameworks that do that for me. WebdriverIO was the one that we were using, and it allowed us to do reporting while keeping parallel execution and cross-browser support. It also allowed us to scale pretty effectively and gave us debuggability so that we could keep our tests stable.

Selenium Grid in the Cloud definitely saved a lot of time for my organization. We do not have a specific QA team that tested each and every release, so we followed test-driven development. We ensured that tests were written alongside development, and they helped guide our product lifecycle. It definitely reduced costs a lot. Additionally, being able to get the reliability of running the entire test suite at a whim and with each and every release gave us a lot of confidence in each and every release.

Selenium Grid in the Cloud can be improved by providing more ready-to-use solutions and one-click setup. Right now, I had to go through a lot of hoops just to get it set up in a dockerized, containerized environment. Having a single-click sort of solution right in the open-source projects would be a godsend feature.

Being previously in startups, support did not matter as much for Selenium Grid in the Cloud, but integration has definitely been done well because of the W3C standards and very standardized frameworks which implement that. Documentation has definitely been a strong suite for Selenium Grid in the Cloud. However, being open-source, support lacks a lot, which definitely stops a lot of organizations from picking up a solution such as an open-source Selenium Grid. Being open-source, there is no support.

I have been using Selenium Grid in the Cloud for more than six years.

Selenium Grid in the Cloud is as stable as you make it, but overall, we were able to make it pretty stable.

We were able to scale Selenium Grid in the Cloud as per our needs. We did not have to have anything specifically for our needs or do anything specifically. Selenium out of the box does not provide scalability, so because we used some open-source projects which allowed us to do that, we were able to scale it. However, out of the box, I would say it does not rank great on scalability by its own.

I have dabbled in QTP before choosing Selenium Grid in the Cloud, but being a VB Script based and very old framework, it did not make sense to continue with it. Selenium was the perfect framework for our use since our application was web-based.

We saved about an entire team's worth of salaries with Selenium Grid in the Cloud, which came to about 100k per year. The release confidence is difficult to quantify, but the time saved was significant with each release. I would say at least three to four days were saved per release, and we were doing a release every week, if not every two or three days.

Having not had to hire an entire QA team to test each and every release with Selenium Grid in the Cloud definitely saved us about 100k per year in USD. Additionally, we saved a lot on release timelines. For each release, we saved up to two to three days of manual testing effort at the very least. While it is difficult to quantify that in money terms, this was definitely a huge return on investment.

My experience with pricing for Selenium Grid in the Cloud involved just the infrastructure cost, as being open-source, there was no licensing or setup cost.

I looked at Puppeteer for a while before choosing Selenium Grid in the Cloud, but the cross-browser support wasn't there. Selenium provided me the familiarity because I had worked with it before, so it was an obvious choice.

I would advise others looking into using Selenium Grid in the Cloud to get someone who understands it at a grassroots level. You would be in good standing as long as you're testing a web-based application. It does have support for native apps as well, up to a certain extent, especially if you're also using something like React Native for testing across Android and iOS for cross-platform development. It could be great in that as well, but for web-based applications, I would say this is the best tool out there right now. I would rate this product seven out of ten overall.

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.