OpenText Silk Test vs Ranorex Studio comparison

"The feature I like most is the ease of reporting."

"A good automation tool that supports SAP functional testing."

"The major thing it has helped with is to reduce the workload on testing activities."

"The statistics that are available are very good."

"It's easy to automate and accelerate testing."

"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 scalability of the solution is quite good. You can easily expand the product if you need to."

"I like the recording function and Ranorex Spy."

"The most valuable feature of Ranorex Studio is the capture and replay tool. You don't need to do script testing. When you launch any application from Ranorex Studio it automatically captures these test case steps. The next time you can replay the tool the flow automatically happens again. For example, when you do the logging and all the activity will be captured by the tool, and re-execute the same step by using automatization."

"The solution is stable."

"The solution is fast and includes built-in libraries that record and playback."

"Data security was prime for us. Being able to download and run tests on our local machines was a big plus. The flexibility Ranorex offers in terms of customization is outstanding."

"The most valuable feature of Ranorex Studio is its user-friendly interface."

"Code Conversion is one of the great features because sometimes, the automation tool doesn't have the capability of maneuvering around two specific evaluations."

"The solutions's regression testing is very important for our company, as is the continuous integration process."

"Could be more user-friendly on the installation and configuration side."

"Everything is very manual. It's up to us to find out exactly what the issues are."

"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 pricing could be improved."

"The pricing is an issue, the program is very expensive. That is something that can improve."

"They should extend some of the functions that are a bit clunky and improve the integration."

"The solution has a lack of compatibility with newer technologies."

"The support for automation with iOS applications can be better."

"When Ranorex is upgraded, the compatibility with other projects, in version control, in-house or on-premise, fails on occasion. However, overall, the stability is good."

"Other OS Support, Ranorex Spy performance improvement (Especially for Silverlight controls)."

"I would like to be able to customize the data grids. They are currently written in Visual Basic and we are unable to get down to the cell level without hard-code."

"We are mainly working for manufacturing OEMs but the integration is not available. It would be a benefit if they built one integration tool for all the Teamcenter home servers and software as the main PLM data source. It is a simple process at this time, the integration could be made easier."

"One of the areas the service could be improved would be to have the training in Italian."

"Binding to other sources is very good but the object recognition in .NET desktop applications often doesn't work."

"When we have updated the solution in the past there have been issues with the libraries. They need to make it clear that the libraries need to be upgraded too."

"There were a lot of issues we faced. One notable improvement would be better API integration within the tool itself, as we still rely on external tools like Postman."

"We paid annually. There is a purchase cost, and then there is an ongoing maintenance fee."

"Our licensing fees are on a yearly basis, and while I think that the price is quite reasonable I am not allowed to share those details."

"The licensing fees depend on the number of users."

"We paid €3,000 (approximately $3,300 USD) for this solution. When you add the runtime licenses it will be €3,500 (approximately $3,900 USD)."

"There are several types of licenses and you need to choose depending on your needs and level of usage."

"Our company has one license per user with each costing two lakh rupees."

"This solution is a more expensive solution compared to some of the other competitors."

"Licensing fees are paid on a yearly basis."