We performed a comparison between Eggplant Test and OpenText Silk Test based on real PeerSpot user reviews.
Find out in this report how the two Test Automation Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We are able to now automate tests, which so far have been manual."
"The solution is a stable one."
"Good text reading ability."
"The most valuable features of Eggplant Digital Automation Intelligence are bug hunting and OCR technology."
"The most valuable features would be the image recognition and the OCR."
"The main feature of Eggplant Test is that it can do fully automated web testing and app testing."
"We did see a massive return on investment from using Eggplant."
"DAI's newest release allows us to test via scripts rather than models, because we have done 95 percent of our development in functional, not through modeling. I am really happy that then we can use the controller to run scripts rather than having to translate things to models. There are lots of options."
"The scalability of the solution is quite good. You can easily expand the product if you need to."
"The feature I like most is the ease of reporting."
"Scripting is the most valuable. We are able to record and then go in and modify the script that it creates. It has a lot of generative scripts."
"The ability to develop scripts in Visual Studio, Visual Studio integration, is the most valuable feature."
"The statistics that are available are very good."
"The major thing it has helped with is to reduce the workload on testing activities."
"A good automation tool that supports SAP functional testing."
"In terms of additional features, it would be helpful to have one package for all testing. You have the manager, the AI, then you have functional, and about 10 different packages for installing."
"Eggplant Digital Automation Intelligence could improve by lowering the price."
"I would like to see standardized actions already built into Eggplant. For example, "wait eight seconds". That way, I wouldn't need to create it as an action. Right now, I have to program that wait and describe it as an action so that everybody knows it is an action that waits eight seconds... That way, somebody who is not familiar with programming processes like "if-else", or "for", or "while", would be able, from the first moment, and without programming, to put some easy-to-use, standardized, actions in place."
"A step forward would be to have event support, because it is more or less linear at the moment."
"It has low productivity."
"If one area could be improved, it would be some of their documentation. In particular, some of their online help and user support documentation is a little bit out of date and could be revised and updated on a more frequent basis. Other than that, I haven't really found any issues or problems."
"The solution would crash from time to time."
"They need to update the Linux. I think it's kind of an outdated Java Swing application."
"Could be more user-friendly on the installation and configuration side."
"The solution has a lack of compatibility with newer technologies."
"We moved to Ranorex because the solution did not easily scale, and we could not find good and short term third-party help. We needed to have a bigger pool of third-party contractors that we could draw on for specific implementations. Silk didn't have that, and we found what we needed for Ranorex here in the Houston area. It would be good if there is more community support. I don't know if Silk runs a user conference once a year and how they set up partners. We need to be able to talk to somebody more than just on the phone. It really comes right down to that. The generated automated script was highly dependent upon screen position and other keys that were not as robust as we wanted. We found the automated script generated by Ranorex and the other key information about a specific data point to be more robust. It handled the transition better when we moved from computer to computer and from one size of the application to the other size. When we restarted Silk, we typically had to recalibrate screen elements within the script. Ranorex also has some of these same issues, but when we restart, it typically is faster, which is important."
"They should extend some of the functions that are a bit clunky and improve the integration."
"The pricing is an issue, the program is very expensive. That is something that can improve."
"The support for automation with iOS applications can be better."
"Everything is very manual. It's up to us to find out exactly what the issues are."
Earn 20 points
Eggplant Test is ranked 12th in Test Automation Tools with 16 reviews while OpenText Silk Test is ranked 24th in Test Automation Tools. Eggplant Test is rated 7.8, while OpenText Silk Test is rated 7.6. The top reviewer of Eggplant Test writes "Empowers effective test automation with comprehensive platform coverage and scalability". On the other hand, the top reviewer of OpenText Silk Test writes "Stable, with good statistics and detailed reporting available". Eggplant Test is most compared with Selenium HQ, Tricentis Tosca, Katalon Studio, froglogic Squish and SmartBear TestComplete, whereas OpenText Silk Test is most compared with OpenText UFT One, Selenium HQ, OpenText UFT Developer, Apache JMeter and froglogic Squish. See our Eggplant Test vs. OpenText Silk Test report.
See our list of best Test Automation Tools vendors and best Regression Testing Tools vendors.
We monitor all Test Automation Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.