We performed a comparison between OpenText UFT Developer, ReadyAPI, 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."It is a product that can meet regulations of the banking industry."
"The solution is very scalable."
"The most valuable feature is the automation of test cases."
"One aspect that I like about Micro Focus UFT Developer is the ability to integrate it into a testing framework as a library."
"The most valuable feature for UFT is the ability to test a desktop application."
"The most valuable feature of the solution is the number of plugins for object recognition. The predefined libraries allow us to automate tasks."
"This tool is really good. We don't need to write any code, but it writes the code itself, only record and play. And it is simple, and it is not heavy; I mean, it doesn't have a large footprint, and it works well for us."
"The most valuable feature for me is the number of protocols that can be tested. It not only tests Web, but also SAP, Siebel, .Net, and even pdf."
"The most valuable feature has been the assertion as a test step as this has allowed us to increase the scope of testing and validation."
"A single platform for functional testing, load testing security, and service actualization."
"ReadyAPI's best features are that it's user-friendly and its behavior-driven development is flexible."
"When you are working in sprints, you need to have continuous feedback. ReadyAPI definitely helps in automating very fast and rapidly. We have less coding, and we can more easily define our assertions. We don't use it for full-blown performance testing, but normally if you are doing your functional testing, it gives you the request and response time. Anybody who is doing functional testing can see what the request and response times are and raise a flag based upon their business affiliates, that is, whether it is meeting their affiliates. You can identify this during functional testing."
"One of the features of ReadyAPI that's worth mentioning is that it allows you to parameterize. I'm working with more than two hundred resources, so I don't have to go and make a small change at each point every time. I have the option to just parameterize in one place for the changes to reflect everywhere. Another valuable feature of ReadyAPI is that it provides a customized environment. In my company, you work in different environments, such as QA, UAT, and LT, so the URLs for every environment are different. In ReadyAPI, you can customize your environment, set it up, then start working on it. Another feature worth mentioning that's offered in ReadyAPI is automating your test value as the tool allows Groovy scripting. In your test case, you can use a Groovy script that says that in a particular test case, you have ten resources, but you just want to exhibit five and that you don't want to exhibit the remaining five. You can write a small Groovy script that lets you execute just five resources out of the ten resources. I also like that ReadyAPI allows you to read the data from CFC and Excel. It also allows you to create or customize your data, but that only works at a certain point because every application has its specific data. ReadyAPI cannot generate every data, but when I'm posting and I want to generate a random name, such as a first name, I can do it in ReadyAPI. The tool also has many different features which I find valuable, including Git integration."
"It is the best solution you can get across the globe for API, test automation, and API penetration testing."
"Reporting is more robust than other products because test reports can be exported in multiple ways."
"This solution is very intuitive. Once you finish your first few testing cases, you can change several parameters and create lots of testing cases. You could use the same testing cases for different purposes such as automation, performance and screen testing."
"Tricentis Tosca is a really cool tool that you don't have to be technical to use it. Additionally, the solution is easy to use. The modules, libraries, and reusable are in an efficient way to update all the tests. I find it spot on with that. We also started using the design which we switched from Excel. The design was superior to Excel."
"We can also create customized functions. For example, if something isn't supported in Tricentis Tosca Commander, we can create our own function to integrate it with Tosca Commander, so we can utilize it and integrate with the macros."
"It's integrated with different technologies, desktop applications, package solutions like SAP, and mobile applications."
"The item that is different from all the other tools is that it's module based."
"The tool's most valuable feature is Tosca Commander."
"Tricentis Tosca is well integrated with other products like Jira."
"The most valuable feature of Tricentis Tosca is the Tosca Commander. Functionality is another thing I find most valuable in the solution."
"The automation engine is very strong, and it is very competitive in the market in terms of features. They develop a lot of features."
"I have to keep the remote machine open while the tests are running, otherwise, it leads to instability."
"The pricing could be improved."
"The price of the solution could improve."
"The tool could be a little easier."
"The support from Micro Focus needs a lot of improvement."
"Integration with other tools can become a costly exercise."
"It would be improved by adding a drag-and-drop interface to help alleviate the coding."
"In the next release, I would like to see the connectivity improved to be less complex and more stable."
"Many users will consider this solution expensive compared to the layout. It is more expensive than other solutions."
"To generate a test suite in API, I had to create a separate one each time because otherwise it was just override the test. Each API had to be added separately. I thought I could just have one and then create different methods, but I had to add each API separately to create the test for that. That is an area that could be improved."
"The initial setup could be less complex."
"What needs improvement in ReadyAPI is its load testing feature because there was a hiccup when my team performed some load testing on the tool. My team had meetings with the ReadyAPI team and tried to get that issue fixed, but it still hasn't improved. This is a shortcoming of the tool, especially when you compare it with HP LoadRunner."
"It doesn't have connectors to the NoSQL database. This is one of the things where they do not have a very solid strategy today. Other solutions have an in-built mechanism where I can directly and easily connect. An API is more around a user submitting a request on the frontend. It then hits the backend, puts the data, and responds back. If I am hitting MongoDB or NoSQL databases, I do not have ready-made inbuilt solutions in ReadyAPI that can easily help me in automating it faster. In our organization, we deal with NoSQL databases, and therefore, we need Groovy. We just cannot have a connector from ReadyAPI to do that. I have to write Groovy scripts. If you have themes that are predominantly using MongoDB, it leads to more maintenance and support activity because we are introducing more code into our commission. In terms of additional features, it can have cloud support. This is one of the things where we are getting into cloud support. We'll see how it works, but it is one of the doubts that we still have."
"It is challenging doing upgrades and patches because sometimes the environmental variables or suits in the projects get erased."
"ReadyAPI could improve by having dynamic validation information."
"Areas for improvement include the security files, endpoints, and process sessions."
"It can be quite expensive."
"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."
"It requires some coding customization that requires expertise."
"I would like to be able to manage different projects in one repository or have better data exchange between repositories."
"One thing to improve in Tricentis Tosca is that it's not compatible with Excel based forms. Another area for improvement is that the tool is not compatible with OpenText applications. The support and licensing cost for it also need improvement. The tool also needs cloud support, as it's currently on-premises only."
"Making it more stable would be good because we get around 90% stability."
"I would like to see better integration with other testing tools."
"Running the regression – if multiple lists are executed at once or if a list contains 200+ tests, it’s a pain to stop the execution."