We performed a comparison between OpenText Silk Test, Perforce QA Wizard Pro, and Tricentis Tosca based on real PeerSpot user reviews.
Find out what your peers are saying about Tricentis, OpenText, Katalon Studio and others in Regression Testing Tools."The scalability of the solution is quite good. You can easily expand the product if you need to."
"The major thing it has helped with is to reduce the workload on testing activities."
"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."
"A good automation tool that supports SAP functional testing."
"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 most valuable feature is the option to pull changes from others or make local changes in your own change list."
"The technical support is good, we were satisfied."
"This solution is very easy to learn and any non-programmer or manual tester, with little experience in automation, can pick it up quite easily."
"The solution is script-less, so you don't need IT knowledge to use the solution in an operational way. This is the most valuable feature. It's also only one of two or three tools that can do good automation on SAP, and in my opinion, it's the best of those."
"The reporting is really nice."
"The model-based scriptless automation is the most valuable feature because it needs less maintenance as compared to script-based automation."
"Very user-friendly and the low code automation is really helpful."
"The mainframe testing and UI automation are the most valuable aspects of the solution."
"This tool has test data management capability along with test management."
"The support for automation with iOS applications can be better."
"The pricing is an issue, the program is very expensive. That is something that can improve."
"The solution has a lack of compatibility with newer technologies."
"They should extend some of the functions that are a bit clunky and improve the integration."
"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."
"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."
"It would be very helpful if a queue was implemented to handle, for example, 100 requests at the same time."
"More and more artificial intelligence (AI) is coming in. So, some amount of AI to create natural language processing (NLP)-based test cases and manage defects would be very helpful. This is because the technologies have evolved in the last five to six months, so there is a potential opportunity there."
"The user management could improve in Tricentis Tosca because it is confusing. It would be better to have it in one place. Having to add it to the cloud and to a specific project can be a mess."
"The integration with mobile testing could be useful."
"There should be ease of data manipulation within automation test cases."
"Many times when we have raised a ticket, we did not get an urgent response."
"With regard to areas of improvement, report customization should be easier. It would be good if Tosca could provide standard reports for at least 20 variants. At present, there are only three to four variants. The mobile engine needs to be faster and easier to use; it is a bit cumbersome. Also, the object identification in the mobile engine needs improvement. I would like to see easy-to-use customizations for reports in the next release."
"Tricentis Tosca's performance could be better. Sometimes when we are remapping or when it is loading it can take a lot of time. There are free solutions that have better performance in this area."
"Making it more stable would be good because we get around 90% stability."
Earn 20 points
Earn 20 points
