Mobile Spy Apps

UFT vs. LeanFT



The main factor for successful test automation lies in identifying the right automation tool for the test application (AUT). From the many test automation tools available on the market, it is extremely important to choose the most appropriate tool for the general requirements.

HP has released several functional automation testing tools such as QTP and UFT. HP UFT combines HT QTP, QTP add-ons, and HP Service Test to form a single package. It automates the creation and execution of functional and regression tests. It allows you to record, verify and re-execute user interactions. This helps to quickly identify and report any discrepancies in the application. HP UFT is very convenient for business analysts, subject matter experts, test automation engineers, QA analyzers and testers. But it also has a very limited ability to maintain continuous integration, continuous deployment and continuous delivery systems. It is heavy and has a very large training curve.

To meet these challenges, HP has launched another functional testing tool. LeanFT is a very lightweight, powerful, developer-oriented testing tool. It is designed specifically for Agile and DevOps methodologies and supports continuous integration, continuous deployment and continuous delivery.

LeanFT can be fully embedded with standard IDEs such as Eclipse, Visual Studio and naturally integrates with Dev and QA ecosystems. It uses the power of object-oriented programming languages ​​and their commonly used IDEs. LeanFT is aimed at technical automation engineers and developers on Agile teams.

LeanFT actually extends the functionality and features of UFT. LeanFT enhances UFT’s Object Repository and SPY tools. But compared to UFT, LeanFT does not come with a recording and playback function. UFT is still required for web service testing and visual API testing. Business Process Testing (BPT) is only possible through UFT.

It would not be correct to say that LeanFT is here to replace UFT. If so, then UFT 12.5, an improved version of UFT, would not be released. UFT 12.5 improves Chrome’s recording feature. This made it easier to create test scripts for the browser. This way, only one test script can be used for testing in all major browsers. It is also possible to exclude the browser from testing. UFT12.5 can be further integrated with HP Mobile Solution. The reporting feature in UFT12.5 has an HTML database that makes it easy to share information between team members.

The only purpose of switching from UFT to LeanFT would be to use the functions of the object-oriented programming language. LeanFT provides the ultimate benefit of shifting to the left to deliver applications with less effort. To switch from LeanFT to UFT, follow the options below:

– Rewriting scripts in LeanFT: This can take longer and is also an expensive solution.
– Migrate from UFT to LeanFT using automated tools: Using automated script migration tools is a more feasible solution. QuickLean is the first tool to migrate from UFT to LeanFT.


It would be wrong to say that LeanFT is the best solution. LeanFT and UFT solve many different problems. UFT test cases are written to fit into the test environment. Scripts in LeanFT are used to log in to Agile and DevOps environments. It is better to mix and match the use of LeanFT and UFT for better test coverage.


Source by Michael Wade Jr

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button