Associate Vice President at Maveric Systems Limited
Consultant
2020-10-21T18:34:00Z
Oct 21, 2020
Automation has two aspects: what is the tool you are using? and what is the framework you are using to implement it? I think it is always the framework that is standard, and our framework is far more in line with the RFT. That's how we managed to implement it so easily. At the time, it was more data-driven. There weren't a lot of parameters, we could just go ahead and execute many things. On the other hand, we couldn't do distributor programming or schedule dictation. These are problems that we used to have, just like any other conventional automation. Otherwise, it used to work really well on the web-based hi-interactive mode application. That was one of the selling points for us. Today, I don't think anyone is interested in RFT because currently, there are a lot of open-source tools on the market. There are a lot of tools out there and customers want the best solutions available. If there is a more advanced solution that can support multiple applications, then the customer will choose that solution. I honestly don't think customers are interested in RFT. Customers are not open to change. Some people are overconfident when going through a change, and others don't like the idea at all. This is especially true for older organizations — they don't see a need to change. I don't see any reason why customers have not moved ahead. We ourselves are telling people that it's time to move ahead from RFT. It's not a vote against RFT or something like that, the technology as a whole just needs change. RFT definitely is not in line with the times, but I haven't heard anything from IBM regarding new technology or a new tool which is far more robust and easier to manage. If you look at today's current context, I wouldn't recommend RFT because there are far more advanced solutions and products available. I would, however, recommend RPT because their workbench has some principal components, including RFT. My recommendation is to go with RPT — we might be doing so in the near future. RPT in certain circumstances still has an edge. On a scale from one to ten, I would give RFT a rating of five.
We're IBM partners, not resellers. We handle large-scale enterprise projects. I can't recall what version number we have right now, but we are using the current version of RFT. It is 100% compatible with all sorts of database integrations and is compatible with all types of open source TFT-based applications, which makes it a great product to have. I'd advise others to first evaluate the product. IBM provides new users with a 30 or 60-day evaluation period whereby companies can try out the solution. Companies should leverage this and use the product and all of its tools. They will be able to make all sorts of scripts. It will give users a lot of good hands-on experience to get a feel for IBM. If it works well, they can then get a license. I'd rate the solution eight out of ten overall.
Test Specialist at a financial services firm with 201-500 employees
Real User
2020-01-22T12:44:00Z
Jan 22, 2020
As many of our products are moving from PC to mobile, the most important thing that this solution needs is mobile app support. I would rate this solution a seven out of ten.
I rate IBM Rational Functional Tester eight out of ten.
Automation has two aspects: what is the tool you are using? and what is the framework you are using to implement it? I think it is always the framework that is standard, and our framework is far more in line with the RFT. That's how we managed to implement it so easily. At the time, it was more data-driven. There weren't a lot of parameters, we could just go ahead and execute many things. On the other hand, we couldn't do distributor programming or schedule dictation. These are problems that we used to have, just like any other conventional automation. Otherwise, it used to work really well on the web-based hi-interactive mode application. That was one of the selling points for us. Today, I don't think anyone is interested in RFT because currently, there are a lot of open-source tools on the market. There are a lot of tools out there and customers want the best solutions available. If there is a more advanced solution that can support multiple applications, then the customer will choose that solution. I honestly don't think customers are interested in RFT. Customers are not open to change. Some people are overconfident when going through a change, and others don't like the idea at all. This is especially true for older organizations — they don't see a need to change. I don't see any reason why customers have not moved ahead. We ourselves are telling people that it's time to move ahead from RFT. It's not a vote against RFT or something like that, the technology as a whole just needs change. RFT definitely is not in line with the times, but I haven't heard anything from IBM regarding new technology or a new tool which is far more robust and easier to manage. If you look at today's current context, I wouldn't recommend RFT because there are far more advanced solutions and products available. I would, however, recommend RPT because their workbench has some principal components, including RFT. My recommendation is to go with RPT — we might be doing so in the near future. RPT in certain circumstances still has an edge. On a scale from one to ten, I would give RFT a rating of five.
We're IBM partners, not resellers. We handle large-scale enterprise projects. I can't recall what version number we have right now, but we are using the current version of RFT. It is 100% compatible with all sorts of database integrations and is compatible with all types of open source TFT-based applications, which makes it a great product to have. I'd advise others to first evaluate the product. IBM provides new users with a 30 or 60-day evaluation period whereby companies can try out the solution. Companies should leverage this and use the product and all of its tools. They will be able to make all sorts of scripts. It will give users a lot of good hands-on experience to get a feel for IBM. If it works well, they can then get a license. I'd rate the solution eight out of ten overall.
As many of our products are moving from PC to mobile, the most important thing that this solution needs is mobile app support. I would rate this solution a seven out of ten.