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 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.
Find out in this report how the two Website Accessibility Testing Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
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 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.
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.