We performed a comparison between OpenText Silk Test, ReadyAPI Test, and Tricentis Tosca based on real PeerSpot user reviews.
Find out what your peers are saying about Tricentis, OpenText, Perforce and others in Functional Testing Tools."The major thing it has helped with is to reduce the workload on testing activities."
"The scalability of the solution is quite good. You can easily expand the product if you need to."
"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 feature I like most is the ease of reporting."
"The statistics that are available are very good."
"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."
"It clearly makes it easy to test APIs based on the SOAP protocol. We are a logistics company, and we have lots of tracking calls coming in. We provide APIs for tracking services, and it makes sense for us to use SoapUI to test them thoroughly."
"We used to write our own solutions, from small scripts to task web services, so this saves us thousands of hours."
"SoapUI is uncomplicated and user-friendly."
"The tool’s scalability is very good."
"The solution has some good scanning features."
"The utmost importance lies in the performance of the application."
"It's a very simple solution to use."
"API mockups, functional testing, and load testing are valuable features."
"It can provide all levels of testing from design to execution to reporting."
"We have to automate thousands of test cases and complete end-to-end SAP on business processes. To manually execute these tasks, it would take us at least two months. By automating these tasks using Tosca, now it takes five to 10 days maximum. Tricentis Tosca is a codeless or scriptless automation tool."
"The most valuable features of Tricentis Tosca are all the test automation functionality. It is a full-scale automation tool."
"Very user-friendly and the low code automation is really helpful."
"The feature that I have found the most valuable is the recovery and cleanup process. Suppose there is a list of test cases and one test case has failed, it should not impact the other test cases. We can reuse the same test case. We can change the configuration of parameters and then use the test cases on the same thing. So, that's a useful thing. Otherwise, we have to use the cleanup process. Another useful feature is to have our own library files. We can create our objects in the libraries and reuse them. There is no need to create duplicate data for that. They have been giving some enhancements recently which means integration is also there. They've integrated with different software like Jenkins, Bamboo. So, we can also create pipeline points. They have recently given SAP and everything, which is very useful."
"With one click, it will scan all the elements on the screen, so that the user can select the required elements for automation tests."
"The tool can be handled without any knowledge in parameterisation, especially the TestCaseDesign which makes the tool mighty and stable."
"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."
"Could be more user-friendly on the installation and configuration side."
"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."
"Everything is very manual. It's up to us to find out exactly what the issues are."
"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."
"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 UI could be a bit more flexible."
"There aren't any plugins for UI automation. You need to make a custom code and download a job to put into the libraries. If it were panelized, then it would be straightforward. It should be in a panel of the tools, so you can add those tools as your test step in your test cases."
"The documentation needs to be improved because the interface is not easy for a first-time user."
"Grouping of the cases is not possible in SoapUI, to my knowledge. When working with critical cases or the, we were not able to group them properly. We can definitely create a suite and add them there, but within a whole suite, we have to identify them, which was not easy."
"SoapUI Pro is a little heavy due to the number of features. Previously it was not that heavy. Now the tool is too heavy, they should work on fixing this issue because until your system has lots of resources, you won't be able to use it seamlessly. The performance of the application itself could improve."
"I would like more documentation, training, tutorials, etc. Also, I don't particularly appreciate that I have to save everything. It takes up a lot of space on my laptop, but I have to install the WSDL again If I don't save it."
"Occasionally, when you are saving, the solution can hang."
"Could integrate the graphing module for load testing."
"Their license management should be improved. One of our customers is a global customer. They want to use one licensed server and then split the licenses based on the different users of the different business units, but currently, there is only one license server that everybody can access. There is no control, and that's why sometimes congestion can happen."
"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."
"I would like to see more implementation of AI on the self-healing aspect. That would be like the next step."
"It needs better integration with JIRA."
"You need to spend much more time learning the tool and how to use it, compared to others."
"The solution is expensive."
"They can make it more stable. I have used this tool for SAP applications. They have an alliance with SAP, and it mostly worked fine, but there were a few glitches. However, we got the required support from the Tricentis team. They are coming up with their new versions and upgrades with respect to how the Tricentis systems as cloud applications are updated, and it would be good if they have a robust accelerator pack."
"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."
Earn 20 points