Selenium HQ’s biggest advantage is that it is customizable. Its other most valuable feature is that the driver interface is really helpful and user-friendly; Selenium HQ makes it easy to navigate through pages and sections of an app quickly and easily, even including things like clicking, scrolling down, tagging, putting through SendKeys, as well as other actions that need testing in an application. One drawback to Selenium HQ is that there is no object repository like the one that can be found in QTP, which is ironic since continuous integration practices have lately become more common. Also, it can sometimes be hard to create locators for elements and because they are deeply embedded it can take a long time to do so.
Eggplant Digital Automation Intelligence is similarly fantastic. With their newest release, you can test via scripts instead of models using the controller. In addition, the model-based test automation they offer helps reduce the test maintenance process. The solution is also equipped to uncover critical bugs and to verify if and when they have been fixed. However, I think the integrated development environment could use some improvement. It lacks shortcut commands that can help create functions and it would also be helpful if the solution provided features to address complex plans, which at the moment it does not. Their online help and user support documentation is also outdated, which can be frustrating at times. In general, though, it is a good product and it has good scalability.
I think Eggplant Digital Automation Intelligence is a good solution for significantly reducing testing time spent while also increasing accuracy and producing precise results. However, if you are looking for the best tool out there for automated testing, I think Selenium HQ is best because it is highly customizable.
QA Analyst at a transportation company with 5,001-10,000 employees
Jun 3, 2021
In terms of deployment of the solution, we have an internal server in a private cloud running the licensing machine and we have three dev licenses for the product as well as two run-time licenses. The development license allows you to run Eggplant Digital Automation Intelligence and allows you to test it and run your script. The runtime license is what is used when you set up a schedule. All it needs is a run-time license to run the executables and run the tests. But since you don't need the full Eggplant Digital Automation Intelligence Functional IDE, you just need the run-time license.
Depending on your use cases, it's prudent to look around at some other solutions if you feel there are others that offer similar features. If you choose Eggplant, you should evaluate how you're going to use it and make a smart decision about the number of developer- and execution-only licenses you purchase to maximize your budget. We found that going heavier on execution-only licenses has been a way to reduce our costs and maximize our ability to benefit from the software. Beyond the standard licensing fees there is just the cost of the resources it takes to do the work of utilizing Eggplant. And that is much better than the alternative of manual testing. There are almost negligible hardware costs. We have Eggplant running on commodity workstations that aren't anything special or expensive. I wouldn't consider it a significant expense to host it.