Selenium Grid in the Cloud

Our main use case for Selenium Grid in the Cloud  is running the automation test cases which we have, as running that locally is not a possibility because there are too many, and we want to run them in parallel in a reliable way, making it a must for us to utilize Selenium Grid in the Cloud .

Selenium Grid in the Cloud has positively impacted my organization by decreasing the time to test and deliver in production, significantly improving our DORA metrics. We are able to run more test cases on the same application and before using Selenium Grid in the Cloud, the time taken would have been prolonged, limiting our ability to test on different versions or browsers concurrently. This improvement helps in decreasing incidents, increasing customer satisfaction, and significantly reducing the time to deployment and testing, thereby positively impacting my organization.

The best features Selenium Grid in the Cloud offers include the capability to run test cases in parallel, and we implement customizations for identifying flaky tests or tests that are not running fine. Whenever test cases fail, we receive full logs and screenshots, which help us significantly. Selenium Grid in the Cloud assists us in parallel execution and enables us to distribute the workload effectively; if the workload is light, we can free up machines, and if it's heavy, it scales up automatically with multiple machines. It also allows us to test our applications across various versions of the same browser and on different browsers, as well as test mobile websites to see performance across different platforms, features that are definitely helpful for us.

We manage the tests on Selenium Grid in the Cloud based on the rankings, so we do ranks and decide when we are going to run based on which intervals. For some applications, we maintain an Excel sheet in which we do the ranking and the intervals, while in other cases we have config map files that categorize particular test cases based on their priority. We write the priority using annotations as well, which is how we manage everything on Selenium Grid in the Cloud.

Sometimes Selenium Grid in the Cloud requires manual intervention for very long-running test cases, which can get stuck and block the machine. We attempt to set up some customizations that facilitate automatic failure, and giving alerts at that moment would be really beneficial for debugging. This expectation of features in Selenium Grid in the Cloud is important to reduce our manual workload; having more customization options without switching to a paid version would be advantageous.

There are areas where Selenium Grid in the Cloud can be improved; we need to undertake many customizations on our end. The iteration speed for new features should be faster, incorporating market feedback effectively. Additionally, enhancements around Kubernetes  could improve our configuration ease, and features like KEDA could optimize the upscaling and downscaling processes. Opportunities for integrating observability metrics through OpenTelemetry  also exist, which would be useful for analysis. I would appreciate seeing more rapid iterations aligned with industry advancements, and incorporating AI features like chatbots for information retrieval would be beneficial.

There are smaller improvements needed as well; for instance, better test management integrations that allow direct session pushes to TestRail , Xray, or Allure would be great. Notifications to teams via Slack or PagerDuty alerts regarding issues will also aid in informing developers about failures. Implementing AI-based resource prediction capabilities would provide valuable insights into resource utilization based on past run data, which would certainly enhance our operations.

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

Regarding the scalability of Selenium Grid in the Cloud, it is not particularly scalable when configured manually, as we need to set up several custom solutions to enhance scalability.

The customer support for Selenium Grid in the Cloud is decent, but I would not describe it as great since we have to handle many tasks ourselves.

We did not use a specific solution prior to adopting Selenium Grid in the Cloud; however, we tried various paid tools such as BrowserStack , which performed well but was not cost-effective or suitable for running high-scale tests. Thus, we shifted to the open-source option and configured everything ourselves.

Before choosing Selenium Grid in the Cloud, we evaluated several other options, including paid tools like BrowserStack , Sauce Labs , and Perfecto , but found them lacking for our needs. We also checked self-hosted options such as Selenide and Moon before deciding to set up Selenium Grid in the Cloud on our public cloud.

My advice for others considering Selenium Grid in the Cloud is that if you have a capable DevOps engineer to manage scalability issues and can operate the platform independently, the open-source solution is the way to go. However, if you prefer low-maintenance options, I recommend looking into paid solutions like BrowserStack that offer significant benefits and CI/CD integrations. I would rate this product a seven out of ten.

Parallel testing is my main use case for Selenium Grid in the Cloud , which I use extensively. I have approximately 5,000 test cases, and I need to reduce execution time by running tests on different machines to enable parallel execution and decrease the overall time required.

I use Selenium Grid in the Cloud  through BrowserStack , where I have access to real devices to execute those test cases and reduce time. The recordings and logs provided have been helpful for debugging issues.

Recordings are the best features Selenium Grid in the Cloud offers for me, and they are helpful for debugging issues. Having the recording of the execution is sufficient for my needs.

Selenium Grid in the Cloud has positively impacted my organization by improving execution time. Daily, I am able to save five to six hours of execution time, which has helped considerably.

Currently, there are no improvements I would suggest for Selenium Grid in the Cloud, as what I am using has been sufficient for me. I will share any issues or improvement requirements in the future if they arise.

I have been using Selenium Grid in the Cloud for three years.

Selenium Grid in the Cloud is stable; however, I sometimes face challenges, but overall it is almost stable.

I am not certain about the scalability of Selenium Grid in the Cloud, but I think it would be better if there were CI pipeline integration with Selenium Grid. With cross-browser devices, it could be better if I could use cross-platforms incorporating both mobile and web.

The customer support for Selenium Grid in the Cloud is good, as they respond within 24 hours. I would rate the customer support an eight out of ten.

Previously, I had not implemented Selenium Grid and just ran tests normally. After using Selenium Grid in the Cloud, it has helped considerably.

Before choosing Selenium Grid in the Cloud, I found a few alternative solutions, including Selenium.

Selenium Grid in the Cloud is deployed in my organization as a private cloud with one server and one Docker  instance using AWS , where I execute all test cases.

After implementing Docker  and Selenium Grid, I have seen a drastic reduction in execution time, which has helped improve productivity. My advice for others considering Selenium Grid in the Cloud is that they should pursue it, as it can reduce execution time significantly, improve productivity, and allow focus on critical issues. I rate this review a nine out of ten.

My main use case for Selenium Grid in the Cloud  is to run multiple devices and multiple OS browser combinations. I tested it on mobile devices as well as on laptops and systems. I wanted to specifically run certain sets of browser combinations or different versions of browsers, and we keep doing this because there are high chances that users directly use various browser configurations.

The best features that Selenium Grid in the Cloud  offers are scalability and parallel execution. The user interface is very simple. Selenium Grid in the Cloud has positively impacted my organization by enabling fast test cycles, and the setup was very smooth. We have obviously saved both people and money with Selenium Grid in the Cloud.

I believe the main feature that could improve Selenium Grid in the Cloud is providing an easier perspective. The main part is that sometimes the documentation is not clear, and we run into some problems. The UI features of Selenium Grid in the Cloud could be improved so that it will be easier to set up. The documentation side can also be improved.

I have been working in my current field for almost 16 years.

In my experience, Selenium Grid in the Cloud is stable.

The scalability of Selenium Grid in the Cloud depends upon usage.

Sometimes, I may have to reach out for customer support.

The solution I previously used before Selenium Grid in the Cloud was a standalone solution which we had, and then we made it as a nightly batch run.

Before choosing Selenium Grid in the Cloud, I evaluated many options available such as Sauce Labs , which are quite expensive and licensed. Selenium Grid in the Cloud is quite easy to set up.

My company has a partnership with this vendor as we consume that.

My advice for others looking into using Selenium Grid in the Cloud is that it is a fantastic solution, especially if they already have a cloud setup with the vendor.

Cost-wise depends on various factors.

Selenium Grid in the Cloud has positively impacted my organization by enabling fast test cycles, and the setup was very smooth.

How it is being used depends on the execution. I found this interview very clean, but there were on and off lags, so I think it was because of my internet connectivity or another factor, but overall it was good. I think providing a short poem or haiku that summarizes my review would be really useful. My review rating for Selenium Grid in the Cloud is 8.

My main use case for Selenium Grid in the Cloud  involves integrating Selenium and Appium  tests together. We are integrating them in the same case, running parallel tests, and we are using the BrowserStack  platform, which allows us to run in parallel and also access the video records of them.

A specific example of how I use Selenium Grid in the Cloud  for one of my projects is when we run our Appium  and Selenium tests on LambdaTest  while using a video meeting platform in Astrak. For example, we start a video meeting web-to-web, using Selenium on both sides, but if it is web-to-app, we use Selenium with Appium. This setup ensures the video reaches both sides, and the voice can be transmitted, allowing users to chat and control their cameras and audio.

Generally, we can get the video records of the tests, obtain the logs, run parallel tests, and utilize different capabilities, such as starting browsers and accepting permissions like camera and microphone.

The best features Selenium Grid in the Cloud offers include access to different Selenium versions, various browser versions, and the ability to run parallel tests. These are important parts.

These features help my team significantly because we are able to run tests faster and cover more cases. When we run different browsers, we can cover more cases, and running parallel tests allows us to execute tests faster.

One important aspect of the features is that when we face any issues, we can open the video records and logs. This is the main use case for me.

Selenium Grid in the Cloud has had a positive impact on my organization as we are able to run in an isolated area. It helps us because we are not running locally; we are running on Selenium Grid in the Cloud, which allows us to obtain healthier results and find common usage examples when we want to implement anything.

To improve Selenium Grid in the Cloud, I think it is important to integrate desktop recording because we need to use Selenium Grid in the Cloud with desktop applications in some cases. There are limitations that could be addressed with this integration, as we have limitations in the browser offerings.

I have been using Selenium Grid in the Cloud for around five years. I used it before on LambdaTest  for around three years, and now I am currently using it again for almost two years.

Selenium Grid in the Cloud is stable.

Regarding scalability, we are able to run more tests easily.

I haven't required customer support at this point. I talked with the BrowserStack  team on the Appium side, but I didn't need any help on Selenium Grid in the Cloud side.

I previously used LambdaTest, but not here. I worked directly for the LambdaTest company. I haven't used any other platform aside from LambdaTest and BrowserStack.

Before choosing Selenium Grid in the Cloud, I checked Sauce Labs , and I didn't explore any other options. I focused on LambdaTest.

I have seen a return on investment because it helps us save time. If we don't use the cloud, we need to set up Selenium Grid and other things ourselves, but in the cloud, everything is ready for us, which allows us to save our time.

My experience with pricing, setup cost, and licensing is that I think the price can be improved. The value is high, but for now, we are using it, and our expectation is better.

My advice to others looking into using Selenium Grid in the Cloud is that the logs and video records help us when some cases fail, and running in parallel allows us to save time and obtain results quicker. This is the most important part for me. I give this product a rating of 9.