External reviews are not included in the AWS star rating for the product.
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.
My main use case for Selenium Grid in the Cloud involves the company I work for, Telstra, which is a large-scale enterprise telecom company. Here we have many capability teams, and each team has its own automation suite. In order to effectively run this automation suite on their need-to-do basis, we use Selenium Grid in the Cloud using AWS Fargate instance, so that each team can use their own container to run their automation scripts without any interference.
I have something else to add about my main use case or something unique about how my team uses Selenium Grid in the Cloud, specifically for doing our automation runs to ensure that the regression suite is intact. The main reason that we use Amazon Fargate is because we feel the APIs are very good to understand the progress of the automation runs.
The best features Selenium Grid in the Cloud offers for my team include containerization, which isolates the run of one team from the other. The maintenance of the instances is pretty easier, so that the team doesn't have to focus more on the infrastructure point of view. Additionally, we ensure that we use resources only on the need-to-go basis, so we are not overusing any resources. When there is no automation run happening, there are no active instances running. This way, we control the cost as well.
Selenium Grid in the Cloud has positively impacted my organization, Telstra, because we provide more importance to security. All the environments in which our automation runs happen are thoroughly scanned by the internal audit team. Using a cloud service like AWS, where we have a proper security mechanism in place, has helped a lot. In terms of productivity, we feel creating images and other tasks on the go has improved the productivity of the run. Cost-wise, most of the resources are used only on our need basis, which has reduced the cost of our QA budget.
There are many improvement areas I feel that Selenium Grid in the Cloud can make.
I have been using Selenium Grid in the Cloud for the past one year, when I joined Telstra.
In my experience, Selenium Grid in the Cloud is stable and has been reliable for my team, as we noticed very few to minimal issues regarding its performance, making us quite satisfied about the tool.
Selenium Grid in the Cloud's scalability has handled increased demand and larger workloads smoothly. It auto-scales or auto-degrades based on the flow, which has definitely helped our costs effectively. There are no blockers during peak release days where the automation runs are effectively used by almost all the teams. It has managed to handle the releases on time without any complaints from teams about the non-availability of instances to run their automation scripts.
Customer support for Selenium Grid in the Cloud has been good. There is a dedicated team that communicates with the cloud provider and they have provided a satisfactory experience.
Negative
I have not had experience using a different solution before Selenium Grid in the Cloud during my time at Telstra. However, in a previous organization, we created a Jenkins agent node setup within the organization itself, using an in-house distribution with a node and agent connection, resembling a master-slave connection.
I have seen a return on investment, as at least 20% of work has been reduced effectively after going for Selenium Grid in the Cloud, which reduces the man-hours required to maintain and manage tasks. This increase in efficiency allows our team to focus on other aspects of automation, including effectively optimizing the CI/CD pipelines.
I did not evaluate other options before choosing Selenium Grid in the Cloud since I joined Telstra and the infrastructure was already in place, so I did not have the chance to explore other products.
Easy maintenance and resource optimization have helped my team significantly, specifically because the automation is pretty less most of the time. We need to effectively use resources, and in that case, setting up our Selenium Grid in the Cloud becomes the best option since we do not run these regression suites on a daily basis. Teams use them on the need-to-go basis, so whenever there is no automation happening, there will not be any instances running, which definitely helped the cost as we do not use the resources. For debugging purposes, there are proper APIs in place that help to track the failures and get them distributed to the mail distribution list.
The other feature I would like to add about Selenium Grid in the Cloud is the availability of resources. Whenever there is a need for a run, there is a container or instance available for us, which ensures that there is no manual overhead required to maintain the resources. I feel we have an effective infrastructure.
I cannot share specific numbers or estimates about time or money saved, but I can definitely say that productivity has improved by at least 20%. We do not have to spend much of our man-hours to maintain the infrastructure of Selenium Grid in the Cloud, which has reduced the number of people in our R&D team who specifically work on infrastructure and instead focus on other areas including effectively creating a common framework and setting up our CI/CD pipeline using the same.
My advice for others looking into using Selenium Grid in the Cloud is to understand its purpose, grasp the concepts and logging mechanism it has, be aware of pricing, and ensure that it matches your requirements and the pricing policies of your organization.
My main use case for Selenium Grid in the Cloud is to run tests in a way that is not dependent on any particular platform.
This approach has worked well, with the main benefit being that I can run tests in parallel. Since I have containerized the test with Java as the entry point, the image size is kept as small as possible for low-cost shipping to remote machines.
The entire CI/CD pipeline is configured in Jenkins, leveraging EC2 instances to run our tests.
The best features Selenium Grid in the Cloud offers are scalability and running tests in parallel.
The Docker-based approach allows me to spin up a specific Chrome version easily to run those tests, making it an adaptable solution for whatever versions of the browser I want.
Selenium Grid in the Cloud has positively impacted my organization by being more cost-friendly and providing better scaling and speed of execution than the legacy way of running things.
One way Selenium Grid in the Cloud can be improved is by having periodic releases or a ready-made Docker image with Selenium Grid in the Cloud to skip the manual setup.
I often see challenges in visibility, as sometimes I am unable to see the logs, which would be a point of improvement.
I think Selenium Grid in the Cloud can be refined and incorporate AI features, as AI could bring more intuitiveness to the grid and enhance its usability.
I have been using Selenium Grid in the Cloud for close to three to four years.
I personally have not faced many issues with stability; there are occasional failures that can be attributed to either test case issues or infrastructure issues.
The scalability of Selenium Grid in the Cloud is pretty good since I can spin up any number of containers with just one command.
Overall, customer support is good; I have not encountered many issues that required direct interaction with customer support.
Previously, we used the legacy way with around ten to fifteen VMs configured in our private network, facing many challenges that are now mitigated with the Dockerized approach and EC2's flexibility.
Before choosing Selenium Grid in the Cloud, we ran tests locally to prove that the Dockerized-based approach worked as intended before extending to AWS.
I can definitely comment on time saved; earlier, tests took close to three to four hours when run sequentially, but now it is drastically cut down by more than fifty percent, making it about two hours for end-to-end tests.
I would advise others to consider Selenium Grid in the Cloud as a great solution since it allows for hosting and scaling as needed. I give this review an overall rating of nine.
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.