Silk Test Room for Improvement
Director of Engineering at a energy/utilities company with 51-200 employees
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.
The initial setup is somewhat complex if you're deploying on-prem. It means we have to set up a database and application client machines, as well as Silk Meter which manages the licenses. It could be more user-friendly on the installation and configuration side.
Functional Testing Tools
Find out what your peers are saying about Micro Focus, SeleniumHQ, SmartBear and others in Functional Testing Tools. Updated: September 2022.
635,987 professionals have used our research since 2012.