UFT Vs LeanFT

[ad_1]

Introduction

The main factor for successful Test Automation lies in the identification of the right automation tool for the Application Under Test (AUT). Out of the many available test automation tools in the market, it is highly important to choose the most suitable tool for the overall requirements.

HP has released a few functional automation testing tools like the QTP and UFT. HP UFT combines the HT QTP, the QTP add ins and the HP Service Test to form a single package. It automates the creation and execution of functional and regression tests. It enables to record, verify and re-execute the user interactions. This helps to quickly identify and report any inconsistencies in the application. HP UFT is very convenient for Business Analysts, Subject Matter Experts, Test Automation Engineers, QA Analysts and Testers. But it also has a very limited ability to support continuous integration, continuous deployment and continuous delivery centric systems. It is heavy weight and has a very big learning curve.

To address these challenges, HP has released another functional testing tool. LeanFT is a very lightweight, powerful, developer oriented testing tool, It has been built specifically for Agile and DevOps methodologies and supports continuous integration, continuous deployment and continuous delivery.

LeanFT can be fully embedded with the standard IDEs like Eclipse, Visual Studio and it integrates naturally with the Dev and QA ecosystems. It harnesses the power of Object oriented programming languages and their commonly used IDEs. LeanFT targets the technical automation engineers and the dev testers in the Agile teams.

LeanFT actually extends the functionality and features of UFT. LeanFT enhances the Object Repository and SPY tools of UFT. But, compared to UFT, LeanFT does not come with a record and Playback feature. UFT is still required for Web Service Testing and Visual API Testing. The Business Process Testing(BPT) is only possible through UFT.

It will not be correct to say that LeanFT is here to replace UFT. Had it been so, then UFT 12.5, an enhanced version of UFT, would have not been released. UFT 12.5 enhances the recording feature of Chrome. This has made creating cross browser test scripts easier. Thus, only one test script can be used for testing across all major browsers. It is also possible to exclude a browser from being tested on. UFT12.5 can further be integrated with HP Mobile Solution. The report feature in UFT12.5 has an HTML base which has made it easier for sharing information among the team members.

The only goal of shifting from UFT to LeanFT would be to leverage the features of Object oriented Programming Language. LeanFT provides the ultimate benefit of shifting left to deliver applications with less effort. For moving from LeanFT to UFT, the options below can be followed:

– Rewriting the scripts in LeanFT: This can take a longer time and it is also a costly solution.

– Migrate from UFT to LeanFT using automated tools: Use of automated tools for migration of the scripts is a more feasible solution. QuickLean is the first tool for migrating fro UFT to LeanFT.

Conclusion

It will be wrong to say that LeanFT is the ultimate solution. LeanFT and UFT address very different problems. UFT test cases are written to fit in the test environment. Scripts in LeanFT are used for fitting into the Agile and DevOps environments. It is better to mix and match the use of LeanFT and UFT for a better test coverage.

[ad_2]

Source by Michael Wade Jr