We performed a comparison between Sauce Labs, Selenium HQ, and Tricentis Flood based on real PeerSpot user reviews.
Find out what your peers are saying about Tricentis, OpenText, Katalon Studio and others in Regression Testing Tools."There is a huge amount of open source, community provided resources."
"The Failure Analysis feature is really important for us, one of the most important aspects. What is the root cause? Is it because we have a defect or is it that we have a test case that we need to fix or modify? The Failure Analysis is one of the main functionalities that I am exploring all the time in Sauce Labs... The Failure Analysis helps us to discover which test cases we need to work on."
"Testing across multiple devices and environments is now possible to do quickly and effectively."
"The most valuable feature is cross-browser, cross-OS, cross-mobile device testing."
"The insights section provides a great overall state of the automation suite and can identify trends relatively quickly. If we see a dip in our passing rate over time, we can look at what changed when the test started failing to find the root cause rather than doing a quick fix to find that the test fails a short time later."
"Sauce Labs' dashboards contain multiple useful metrics in one place. Everything is represented to us visually on the dashboard, which helps us understand where to focus our attention, what the issues are, and what we need to resolve."
"They update for the latest browsers and mobile phones and support a lot of combinations. They have 1,000-plus desktop combinations and browser versions, which is really great. We need that at Applause. The all-in-one testing suite aspect of it is really important because most of our clients prefer to go to one place."
"It provides a comprehensive selection of browsers and platform versions for our test automations and CI/CD pipeline process. It also provides a comprehensive set of virtual mobile devices, which we can configure for our automation and availability. These features are valuable for us when it comes to testing our applications. We have a website and mobile applications that we want to test and diversify to various browsers and mobile devices as well as restore various versions. This helps us to find bugs that users might be facing and correct them."
"It supports multiple processes, which is great."
"It is programming language agnostic, you can write tests in most currently used languages."
"The most valuable features are ExpectedConditions, actions, assertions, verifications, flexible rates, and third-party integrations."
"My customer previously validated every file and it would take almost 15-20 minutes for a document. They used to randomly select and test only 100 out of the thousands, maybe 85,000, files, to pick up sampling. Each file would take around 20 to 25 minutes, so we were not able to do it manually, but with the help of Selenium, we were able to test all the files in two days. It saves a lot of time."
"Selenium HQ's most valuable feature is picking up and entering values from web pages."
"The grids, as well as the selectors, are the most valuable features."
"The most valuable feature of Selenium HQ is the ability to create automatic tests that can replicate human behavior."
"The most valuable features of Selenium HQ are the automation of all UI tests, its open-source, reliability, and is supported by Google."
"The most valuable feature is the support for Java, where we can quickly code what we need."
"Their technical support is awesome."
"You can utilize this tool on the cloud, and also access application on-premises. That is a very good part of the solution."
"We have found that during automated testing this can be very slow. This causes inconsistencies with the tests. It's very difficult to rely on a service when you can't be sure if a test will pass or fail the next time it runs. This means building in a lot of sync time into the tests which in turn slows them down. If this speed could be improved then the service would be much better."
"We have faced challenges with the availability of mobile devices. There was once or twice where there were no mobile devices available."
"We had some specific features that we opened tickets on, although they were not earth-shattering. For example, the way the menus scroll could be improved because it does not have a bar, the way that people are used to, where you can move up and down."
"The ability to configure the memory and CPU for the test machines should be included."
"With the desktop browser, we can inspect any screen with the web developer option, but they should provide something for mobiles so that we can quickly inspect elements on the device. To write the Selenium scripts, we require web locators. We have to capture them from the local and execute the script on Sauce Labs. If Sauce Labs can provide a solution where we can inspect any of the mobile devices online, it will be very helpful for us."
"Better and programmatic controls on request/response recordings and sharing with developers."
"If I had to speak of an area that could be improved it would probably have to be the speed of interaction with the devices. There is at times a considerable amount of lag while using some of the virtual and at times even physical device farm"
"We have had some issues with the Sauce Connect Proxy on our Jenkins servers failing to start, which makes the optimal CI/CD pipeline come to a halt."
"We'd like to see some more image management in future releases."
"Selenium HQ can be complex. The interface requires a QA engineer or an expert to use it."
"I would like to see automatic logs generated."
"It is not easy to make IE plus Selenium work good as other browsers. Firefox and Chrome are the best ones to work with Selenium."
"The drawback is the solution is not easy to learn."
"It would be better if we could use it without having the technical skills to run the scripting test."
"For now, I guess Selenium could add some other features like object communications for easy expansion."
"Technical support isn't very good. Sometimes their recommendations were not very clear."
"We used an implementation strategy to deploy the solution, not because of the tools, but mainly because of the scripting part of the tool."
"The solution is quite immature, it is not in an optimal state."
"The performance of the tool needs to improve."
