Basically, before LeanFT was introduced by HPE, I was looking at a solution similar to Selenium to integrate some scenarios that UFT was doing well for us; we had to look for other solutions with LeanFT-like leverage. The most important thing about LeanFT is that it gives us the opportunity to introduce developer testing. Initially, because UFT was VBScript based and because of the infrastructure, developers wanted to contribute toward testing, but could not, so they used VBScript and went to eLanguages, which they can use with their development like Java or C#.
They can use the same language that they're using for their unit testing, so they can contribute to that in the very beginning of the lifecycle instead of after the application has been fully developed, at which point it is tested and comments are made on the features.
That is the main aspect: we can put the developer into the testing scenario.
Improvements to My Organization
Initially, although they developed some in-house tools, we were looking for a third party to lower the speed provided. With LeanFT, we are trying to create a kind of hybrid infrastructure where we can use our existing scripting and in the same infrastructure we can use LeanFT.
Room for Improvement
LeanFT is very new to us (we started six months ago). We are still in the process of using it and converting our scripts with it. That means we still need to see all of the built-in capabilities, but it is getting better and better.
Obviously, we are planning to scale in the future because with LeanFT via the service pack, we can do user checking with continuous integration tools, which was initially not possible with the UFT, so we are trying to convert as many scripts from UFT to LeanFT. It will give us the most flexibility with more ways of working with the CPU.
Customer Service and Technical Support
Technical support has been good so far. Sometimes it takes minutes, sometimes they take more time, but most of the time they're good.
We are doing a lot of testing and there are some scenarios where UFT does not fit into the scenario. Since then, we have been looking for a solution. Initially, we were looking at an open-source solution such as Selenium or some third-party tool to learn. We also wrote some of in-house processes, but they are not getting combined with ALM into the single repository, so we are looking for a sub-solution. We kept telling HP that we needed a solution; otherwise, we had to move from UFT and ALM. Ultimately, they told they came up with LeanFT and you can use it with either Eclipse or Visual Studio code.
I won't say initial setup was complex, but it was not clear how to setup because there was an issue with the licensing. The same licensing was not working with UFT that used to work before, but we got in touch with HP customer support, they got back to us and since then it has been very smooth sailing.
It depends on whether you already have a testing tool that is based on a different infrastructure, such as UFT or Selenium. Then, see how smooth the transition will be. However, to start from scratch, start with LeanFT as opposed to another solution because it can give you the power of managing your tests in ALM and the single repository so you don't have to worry about it. Once you install it, it is kind of the best tech with web-based infrastructure, so you don't have to worry about quality control and so on.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Oct 13 2016