The solution can be improved by removing the need for object matching in the framework.

The latest version has increased load time before testing can be run. The reason is that changes were made to how it works with the browser and the startup takes some time. Adjusting those changes to speed up the load time will improve the solution.

If the solution is running on Linux, there are some issues around application compatibility.

There needs to be more effort made to make the solution more relevant to the application.

Didn't find any since they provide light weight usage for execution and script development without tool dependency than compared to other commercial products.

RFT needs to think from a contemporary point of view — from the current context. They need to look at the way they're positioning the tool. They need to do a complete revamp so that even a non-technical person can manage the tool. These are the aspects IBM needs to look into it. The moment they look into it, I think they might come up with something new, which can be contextual to the current needs and demands.

I would like to see the UI change analysis functionality for mobile apps. 

The object repository used for identifying objects can be made better. It has been noticed that the RFT tool is unable to identify some objects, due to which we are unable to add them to the object repository. In this case, the user has to manually add the objects to the object repository. This takes time and effort. It would be good if RFT was able to create a framework to identify objects that are not recognized by the tool.

• It should be more flexible when it comes to integration with test management tools like QC or agile tools like Rally
• It should support more browsers

Reports - Default results log has a lot of useless info, and this is hiding the actual information needed. I have to use customized reports, which we don't expect from paid tool.