Introduction
The primary factor for successful test automation lies in identifying the appropriate automation tool for the application under test (AUT). Of the many test automation tools available on the market, it is very important to choose the most suitable tool for general requirements.
HP has released some functional automation testing tools like QTP and UFT. HP UFT combines HT QTP, QTP plug-ins, and HP Service Test to form a single package. Automate the creation and execution of functional and regression tests. Allows you to record, verify, and rerun user interactions. This helps to quickly identify and report any inconsistencies in the application. HP UFT is very suitable for business analysts, subject matter experts, test automation engineers, quality assurance analysts, and testers. But it also has a very limited ability to support continuous integration, continuous deployment, and systems focused on continuous delivery. It is heavy and has a very large learning curve.
To address these challenges, HP has released another functional testing tool. LeanFT is a very lightweight, powerful, and developer-oriented testing tool. Built specifically for Agile and DevOps methodologies, it supports continuous integration, continuous deployment, and continuous delivery.
LeanFT can be fully integrated with standard IDEs like Eclipse, Visual Studio and naturally integrates with the Dev and QA ecosystems. Harness the power of object-oriented programming languages and their commonly used IDEs. LeanFT targets technical automation engineers and development testers in 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 record and playback function. UFT is still required for web services testing and visual API testing. Business Process Testing (BPT) is only possible through UFT.
It will not be correct to say that LeanFT is here to replace UFT. If that had been the case, UFT 12.5, an improved version of UFT, would not have been released. UFT 12.5 improves Chrome’s recording feature. This has made it easier to create cross-browser test scripts. Therefore, only one test script can be used for testing in all major browsers. It is also possible to exclude a browser from being tested. UFT12.5 can be further integrated with HP Mobile Solution. The reporting function in UFT12.5 is HTML-based which has facilitated the exchange of information between team members.
The only goal of switching from UFT to LeanFT would be to take advantage of the features of the object-oriented programming language. LeanFT offers the maximum benefit of scrolling to the left to offer applications with less effort. To move from LeanFT to UFT, the following options can be followed:
– Rewriting the scripts in LeanFT: this can take longer and is also an expensive solution.
– Migrate from UFT to LeanFT using automated tools: Using automated tools for script migration is a more feasible solution. QuickLean is the first tool to migrate from UFT to LeanFT.
conclusion
It would be a mistake to say that LeanFT is the ultimate solution. LeanFT and UFT address very different problems. UFT test cases are written to fit the test environment. Scripts in LeanFT are used to adapt to Agile and DevOps environments. Better to mix and match using LeanFT and UFT for better test coverage.