Judy ZemanQA Manager at Carrier Global Corp.
Anonymous UserTest Specialist at a financial services firm
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"The biggest feature is the fact that it's codeless. It takes away the problem of finding people with the correct programming language, since there are multiple such languages. It saves time in introducing people to the solution because they don't need programming knowledge, they just need to be able to think logically. This makes it vastly usable by more people who are not even acquainted with IT at all."
"It does allow for good reusability. When it's designed properly and utilized properly, we can put things in a way that allows for reusability, meaning a lot of reuse of VA01, if they're very similar flows, to keep it simple."
"Certify integrates with other tools and it works very well with other machine testing applications."
"It's pretty seamless with SAP and Salesforce because they've built in the field definitions and all the things that you need. You literally turn it on and execute your script and it records it. It's very simple. Then you can go back and put in some of the other functions. For example, instead of hard-coding field selections, you put in a data table so you can run it multiple times or with multiple data. It was actually written to work very well with SAP."
"Certify's web UI testing abilities for testing of modern applications like SAP Fiori was good when we started and they developed it to be even better. We all know that web applications can change objects in DOM quite fast and it breaks tests. To counter it Certify has made object recognition more flexible and generic, so we don't have any troubles."
"The scripting methodology is easy to learn. It is easy to maintain because it is presented in a simple, narrative way. You don't need to know programming." "It has reduced our test maintenance time by more than 50 percent because we don't have to do manual test processes. We have saved over 150 man-hours monthly. It has increased our delivery times. We went from 200 man-hours down (three weeks work time frame) to approximately 40 man-hours (three days work time frame)."
"The most valuable feature is the ability to automate quickly and to maintain and update scripts."
"The decoupling of the test scripts from the data and the application is a nice feature. When you are creating test scripts, for example, for a web application, you have to learn about Worksoft and how the controls of a screen can be interpreted by Worksoft. For that purpose, you create so-called maps. These maps are loosely coupled to your scripts, which means if the application is changed, the control will be changed from an identifier. You don't need to rework the entire script. You only need to do these adjustments in the map, and then you can automatically reuse the scripts. So, it is really a smart move to have the decoupling of scripts, maps, and data."
"The most valuable feature is the UI component tester."
"It is compatible with all sorts of Dark Net applications. Its coverage is very good."
"IBM Rational Functional Tester is very contextual."
"The interface is ok and they have the ability to re-load tests so that you can reuse them."
"The dashboards are very good and consolidate all of the tests that you are performing with the client."
"The most valuable feature of ReadyAPI is that it is user-friendly."
"It has the ability to combine it with different CI/CD tools."
"A single platform for functional testing, load testing security, and service actualization."
"The most valuable features are the integration with Jira and the test management tools."
"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."
"It's easy to learn how to use it."
"Performance on the web UI part, especially with some of the more comprehensive Fiori features, like the complex tables that are being used, could be improved. In those cases we have noticed a lot of execution-time increase with regards to the Certify solution."
"An area that I would like to see improved is how the permissions are applied. If you're applying permissions groups to a user, one of the options is to delete the group entirely and lose the entire permission group, rather than just deleting the permission from the user, which seems a little silly. In my opinion, that whole module of permissions is very confusing and lends itself to common errors."
"Pricing is a bit high and we would like to have the availability of a trail environment for beginners and training would be great to have and easier to expand and use by more and more consultants."
"Better automation capability would be helpful."
"With the codeless process automation across packaged applications, once in a while, if we get a weird application that's not widely used, it gets a little stickier. First, the software has to learn the fields, so you have to identify all the fields. Once you do that, as long as there isn’t any non-standard code in the application, then it works fine. But there's that one step that you have to do, a step you don't have to do with SAP and Salesforce, for example."
"When it comes to mobile testing, we have a small bottleneck there. You have to buy third-party separate licenses if you want to test on a mobile. Business wise we see room for improvement there, although it's that really critical for us."
"Worksoft Certify needs a bit of improvement for its web-based processes. It can be difficult because you need to recall the maps, then you still have to add-on for your browser. When you are using the browser-based testing, you cannot even move your mouse or do anything on your system when you are using the web-based testing. Therefore, it needs a bit of improvement on that side. While it does work, it needs improvement. From the SAP side, there is nothing better than Worksoft Certify. However, from the web-based, we are moving towards Fiori. SAP will soon be totally web-based. For Fiori, they need to be great with SAP testing. Thus, Worksoft has to improve the web-based testing part for Certify."
"We would like this to be able to be used outside of SAP applications, as it would be good for other types of products."
"As many of our products are moving from PC to mobile, the most important thing that this solution needs is mobile app support."
"If the solution is running on Linux, there are some issues around application compatibility."
"They need to do a complete revamp so that even a non-technical person can manage the tool."
"I would like to see a better dashboard for monitoring in the next release of this solution."
"If ReadyAPI had more integration with all of the big tools on the market then this would be very useful."
"Performance and memory management both need to be improved because other solutions use less memory for the same amount of data."
"The performance in some cases needs improvement. Sometimes it requires too many resources."
"Lacking flexibility of adding more custom verification for security testing."
"The reporting is not very robust and needs to be improved."
"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."
"Version control does not work well."
"The initial investment is probably a little high. It was a little hard for me to sell, but it was a one-shot deal and that's why it's so high. All we are doing now is paying annual maintenance, which we don't have to do if we don't want upgrades, but we do."
"Purchasing and licensing are okay. Go for the perpetual licenses. In that way, you own a license, then you can purchase maintenance and support on top of that, so you don't have to pay every year for it. Even if you don't want it a contract with Worksoft Certify in the future, you will have your own license of it. Then, if your usage is not that much, you can have one or two perpetual licenses. However, if you want to run your processes, you will need more licenses, e.g., using the run-only licenses. They are really cheap compared to the full licensing."
"I can only judge based on the situation that we had around six years ago when we did the tool evaluation. Worksoft was not the cheapest, but it provided the value. For 25 concurrent licenses, we paid more than €400,000, so it was not cheap. In the end, if you see how much time you are saving and compare it with others, its price is okay. We had also compared its cost with the licensing costs for HP and Tricentis, and they were at another level. Now, as we have already booked the licenses, we only have to pay an annual maintenance fee, which is 70%, and that is okay."
"Licensing is good but the prices for the products are expensive. A single-user license may go for something like $10,000 to $30,000. There are no additional costs, and support is included within that price."
"This is a cheap solution when you consider the money that will be saved in testing."
"The cost of a license is probably around $1,000 to $2,000. Accounting is done by my leadership. I am more into implementations and making sure all things and processes are taken care of and the frameworks are maintained and managed."
"There are costs in addition to the licensing fee. For example, if you want to add the load testing you would pay more."
ReadyAPI combines the power of SoapUI Pro, LoadUI Pro, ServiceV, and API Monitoring in AlertSite into a single pane of glass. From functional testing, to performance testing to post-deployment monitoring, SmartBear’s API tools help you to deliver accurate, fast, and secure APIs.
IBM Rational Functional Tester is ranked 24th in Functional Testing Tools with 3 reviews while ReadyAPI is ranked 10th in Functional Testing Tools with 8 reviews. IBM Rational Functional Tester is rated 6.6, while ReadyAPI is rated 7.8. The top reviewer of IBM Rational Functional Tester writes "Good coverage and compatibility with excellent stability". On the other hand, the top reviewer of ReadyAPI writes " A great single platform for functional testing, load testing security, and service actualization". IBM Rational Functional Tester is most compared with Selenium HQ, HCL OneTest, Micro Focus UFT One, Tricentis Tosca and Eggplant Digital Automation Intelligence, whereas ReadyAPI is most compared with SoapUI Pro, Apache JMeter, Katalon Studio, Tricentis Tosca and BlazeMeter. See our IBM Rational Functional Tester vs. ReadyAPI report.
See our list of best Functional Testing Tools vendors.
We monitor all Functional Testing Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.