it_user313965 - PeerSpot reviewer
Consultant with 10,001+ employees
Vendor
Being able to code tests in C# is valuable, though its stability needs to be improved.

What is most valuable?

The most valuable feature is the possibility to code the test framework with C# and Java and therefore, use the development teams.

How has it helped my organization?

The technical part of test automation does not need a separate technology for developing test suites for end-to-end testing, regression testing and user acceptance testing.

What needs improvement?

Improvement is still needed for stability and performance. Still, it is at the beginning of a technological shift for HP test automation. The tool would be best if HP made the OR functionality and performance similar to the HP UFT one.

For how long have I used the solution?

The solution has been used in a pilot alpha testing project.

Buyer's Guide
Functional Testing Tools
April 2024
Find out what your peers are saying about OpenText, SeleniumHQ, Tricentis and others in Functional Testing Tools. Updated: April 2024.
767,095 professionals have used our research since 2012.

What was my experience with deployment of the solution?

Yes – deployment was not yet production ready.

What do I think about the stability of the solution?

For several browsers it needed some special settings which affected the stability of the product.

What do I think about the scalability of the solution?

Scalability was not an issue for the pilot, and it's not expected to be an issue in the future, as all development resources can be used on an as needed basis.

How are customer service and support?

Customer Service:

The support in the alpha/beta test phase was especially good.

Technical Support:

The technical support was perfect as we could talk directly to architects developers and product managers.

Which solution did I use previously and why did I switch?

Previously we used HP UFT and Selenium because there was actually no alternative products at the market.

How was the initial setup?

The setup was well-prepared, but quite complex. When related to our environment, there have been setup problems. These problems could be resolved by an intimate technical customer service.

What about the implementation team?

The implementation happened in-house.

What was our ROI?

You could cut the technical part of the test automation processes by about 50%.

What's my experience with pricing, setup cost, and licensing?

Setup cost was around €10,000. Day-to-day processes would be 0 as the technical part of test automation will be integrated completely into development. This will save the extra part of technical test automation, which sums up to the yearly license costs.

Which other solutions did I evaluate?

All options in the test automation market are evaluated at all times. Rational Robot, Tosca, Soap UI, etc.

What other advice do I have?

Make sure that you have test management at the same level as test automation otherwise money will be lost.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user313965 - PeerSpot reviewer
it_user313965Consultant with 10,001+ employees
Vendor

Its time for an update:

Actually we have LeanFT now running for a year implementing new projects using the same framework we were using before for UFT.

From the valuable features we use Java and could make use of our experienced programmers to optimize the framework code. The E2E testing still need improvement as we did not yet integrate it in ALM - nor the Jenkins processes. The OR functionality of UFT is still missing.

We will continue to setup new projects with LeanFT, especially when moving the organisation to agile methodologies. Still the old UFT framework does the massive regression workload at 90%+...

it_user482850 - PeerSpot reviewer
Enterprise DevOps Leader, Program Manager at a media company with 1,001-5,000 employees
Real User
I believe the main feature for using it is the flexibility across different platforms. It needs to be able to be used on Chrome, Firefox, and other browsers on Macs.

Valuable Features

I believe the main feature for using it is the flexibility across different platforms. For example, I can use it whether it's Eclipse using any of the programming languages. The multi-platform usage of LeanFT is really useful.

Improvements to My Organization

It's still in the early days, but still I see that we'll move over to it fore the effort savings once the LeanFT roadmap comes into place.

Room for Improvement

It needs to be able to be used on Chrome, Firefox, and other browsers on Macs and not just Safari. That's a very key requirement for my organization.

Scalability Issues

It's very scalable. Given the power that it provides in terms of any programming language and any development platform you can use it on, such as Eclipse or any ID platform. So definitely it's more scalable but still there will be room for improvement in terms of the Mac browsers compatibility/support.

Customer Service and Technical Support

We hardly have incidents. There hasn't been much activity as compared to UFT. We will see how it goes in the future.

Initial Setup

The complexity was pretty much okay, it's acceptable, so that was good. Once you implement the infrastructure within the organization, the complexity is pretty much similar to any other automation tool.

Other Solutions Considered

We didn't actually choose it. Our customers provide LeanFT, so we started using it.

Other Advice

We're still early on with our use but there are a lot of good things that have been promised. Those results have to be realized now. What has been told so far as well as the roadmap which I have been told should come into place pretty quickly.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Functional Testing Tools
April 2024
Find out what your peers are saying about OpenText, SeleniumHQ, Tricentis and others in Functional Testing Tools. Updated: April 2024.
767,095 professionals have used our research since 2012.
it_user484959 - PeerSpot reviewer
Director, Service Transition and Quality Management at CareFirst BlueCross BlueShield
Vendor
We use it to streamline workflow and enable productivity in a business context. I'd like to be able to do headless scripting and not just always be UI serving.

Valuable Features:

LeanFT is used a lot more by our less experienced testers and developers who want to get more point-and-click type automation. Then obviously I also manage the automation team, so we use UFT for a ton of all of our XLC automation as well as anything with a UI. So we also bring it into our business functions as well. If we need to do clean-up, data entry, management of manual tasks where you're putting yourself in a UI scenario, we'll run scripts for that for productivity.

We pretty much use that to streamline workflow and enable productivity in a business context in our business unit as well as in our IT shop, so just reducing workload on IT people as well as testing. It's used pretty extensively beyond that.

Room for Improvement:

I'd like to not have to use Selenium. I'd like to be able to do headless scripting and not just always be UI serving.

Stability Issues:

It's stable.

Scalability Issues:

We're already at enterprise scale, so it's used across the enterprise. I would say that we're at that point.

Initial Setup:

I have an entire team, so I'm a director and I have an entire tools team that does that. I did get involved in the planning and the strategy of how we're going to do it. My team said that first installation is relatively easy. When we go to upgrade and migrate, that's where there's pain.

Other Advice:

We're still trying to get the adoption on that for the user community. It's very usable though. I rate adoption pretty high, so when people are using it, for instance, UFT, I'd definitely give that a ten because we use that a lot. I'd like to see some enhancements in the product, and we're working with HPE on that.

Have a well-defined process, have a strong reporting structure, meaning in your process you want a lot of measurability. If you define your output, the reports and the questions you need to answer from what you're doing, which your process should be managing for you. In our company, we are very specific about what our executives and stakeholders want.

We have a very well-defined set of measurements that we have to take. We then put a process designed to ensure those measurements are always taken. That then allows you to deal with your outputs and your reporting structure, which then allows you to properly architect your tooling. The technology is very flexible. You have to decide as a client area how you really want to use it and that's going to start with what your business needs are the values that you're trying to get out of it.

That's the biggest advice that I have, it's not even on the technology. The technology will do great things for you if you have a plan and a structure and you know what you want it to do for you. Half the time they don't know, they want the tool to do it for them and it's the other way around. So that's what I advise people to do.

Think about it, have a vision, have a plan, tie that to outcomes, and measure those outcomes. If you're answering the right questions and asking the right questions, your technology will really enable you. You've got to look at it from that standpoint.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Manager PMO Specialists at a construction company with 10,001+ employees
Real User
Good stability but it is complex to set up and should support module-based testing
Pros and Cons
  • "The most valuable feature is stability."
  • "Easier connectivity and integration with SAP would be helpful."

What is our primary use case?

I primarily use this solution for the automation of regression testing in SAP.

What is most valuable?

The most valuable feature is stability.

What needs improvement?

This is a script-based tool and the usability needs to be improved.

Easier connectivity and integration with SAP would be helpful.

In the future, I would like to see module-based tests instead of scripting.

For how long have I used the solution?

I have been working with UFT for about one year.

What do I think about the stability of the solution?

The stability is quite good and we haven't had any issues.

What do I think about the scalability of the solution?

Scalability is not an issue except that you need to create quite a few scripts. It is not easy to just create new test cases for new solutions. When you have to consider other solutions or applications then it's a bit tricky.

The number of people using the UFT application is quite limited, at perhaps three or four. However, there are a couple of hundred people responsible for performing the tests it creates.

How are customer service and technical support?

I would rate the technical support as okay, but not better. There are bugs between UFT and HTLM that they have not been able to solve. 

How was the initial setup?

The initial setup is complex because of the integrations. A lot of knowledge is required to do the scripting, we did not have it, and it is difficult to find. Our deployment took about two months.

What about the implementation team?

A consultant assisted us with the deployment and we were satisfied with the service.

What other advice do I have?

Ultimately, due to the scripting, integration, and other functionality that is missing, we may switch to another solution in the future.

I would rate this solution a five out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user470490 - PeerSpot reviewer
Technologies Consultant at a tech company with 10,001+ employees
Real User
It gives us the opportunity to introduce developer testing. They can use the same language that they're using for their unit testing.

What is most valuable?

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.

How has it helped 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.

What needs improvement?

I think the one thing we're basically asking for should be JavaScript support, but I think they will start adding JavaScript support in the future. We haven't moved into that; we’re still into LeanFT. We're still finding out what's in there. Once we know what we can really do in LeanFT, then I think we can start providing feedback regarding enhancements we want to see in the solution.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are 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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What other advice do I have?

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.
PeerSpot user
it_user253329 - PeerSpot reviewer
Senior Automation Engineer with 1,001-5,000 employees
Vendor
Most valuable features are the ability to customize, if needed, and to integrate with ALM because its our test management. The ability to implement with Jenkins for dev ops is also a valuable feature.

What is most valuable?

The most valuable features are the ability to customize, if needed, and to integrate with ALM because its our test management. The ability to implement with Jenkins for dev ops is also a valuable feature.

How has it helped my organization?

In our case, because we’re in the insurance industry, we have technologies from 20 years old to brand new. That’s one reason that LeanFT is so great -- because it can support all those technologies, even the older ones.

What needs improvement?

In the next release, I'd like to see ties into C# and Java, enabling us to work more closely with development. However, from what I’ve seen, LeanFT object recognition looks great. The identifiers for an object can be the same for multiple objects, and test automation can detect that. But LeanFT object identification center allows you to see that the identifiers are not necessarily unique, which is very beneficial.

What do I think about the stability of the solution?

The issues were variable. If you’re using the tools capabilities and the actual traditional test automation you put into a script, it can be unreliable. We try to use descriptive programming, but it becomes more of a test driver rather than creating automation for its test capabilities.

What do I think about the scalability of the solution?

It depends on how you design your solution. If you design a good framework then you can design a scalable solution.

How are customer service and technical support?

Technical support was not very good. We do reach out, but often they're unable to help. Customer support was similar.

Which solution did I use previously and why did I switch?

We are a subsidiary, so decision making was limited. Most recently they decided ALM would be the enterprise standard. For automation they decided to use UFT.

How was the initial setup?

Fairly straightforward because it integrates well with ALM. One issue is that if you're using compass, which has its own Java versions etc., it can conflict with LeanFT.

What other advice do I have?

My most important criteria when selecting a vendor is compatibility with my systems, applications, platforms, and whatever apps I am using.

Automate where you can and also try to shift your testing to the left. Testing management is key.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user403125 - PeerSpot reviewer
it_user403125Tech Lead at KPIT Technologies
Vendor

Hi Sharon,

Please share your experience of integrating leanft wit Jenkins.

Thanks,
Swaroop

PeerSpot user
Sales at a comms service provider with 10,001+ employees
Real User
It supports our approach in agile and DevOps deliveries.

What is most valuable?

It was very interesting to see that once we began using the traditional UFT for functional testing, we received a lot of feedback from our development and testing teams that it's clumsy, not modern, and so on. But once we upgraded to UFT Pro, it was an easy adoption, even though it's a commercial product. In that sense, it supports our approach in agile and DevOps deliveries really well.

How has it helped my organization?

The UFT Pro follows the same projects that are following the agile DevOps journey. They are also starting to use UFT Pro.

What needs improvement?

At the moment, we are happy as it is. We don't have any kind of specific technology requirements for improvements, at least not at the moment.

But, support for open source solutions, such as the Robot framework, which is actively used, might be really helpful.

What do I think about the stability of the solution?

So far, we are very happy with stability, even though knowing that there is quite a lot of new development. But so far, so good. I have nothing bad to say.

What do I think about the scalability of the solution?

We are at a very early stage in implementing this solution. But at the moment it looks promising. Although, it is difficult to say how far it goes. But at least, so far, we have started.

How is customer service and technical support?

So far, technical support is very good because we have been using HPE products, or the earlier Mercury products for a long time. We have a quite good collaboration with them. From that kind of background and knowing our kind of working environment and solutions, together with their technical support and help, we have been able to implement these tools in the right way the first time, without trying to invent the wheel on our side.

How was the initial setup?

Setup was pretty straightforward. Obviously, we kind of had a bit of discussion internally, because we didn't take a traditional migration from the earlier product. We really started from scratch. That is still somewhat an issue for some of the deliveries, that they don’t want to use the agile method. But we have highly recommended this because they are two different worlds and that it would be better to plan it carefully and not just carry on all the crap from history.

Which other solutions did I evaluate?

Our development teams are using a lot of open source solutions, and other tools like JIRA. But for our business needs and purposes, we have seen that HPE solutions are still valid for our business. We need to have backwards traceability. We have to have the capability to show what has been done, what's been going on, and what. In some of the cases, there has been the discussions that, "Yes. We have all this information, but you have to go to the Jenkins, or this and that logs, and it's there." But that's not what the business wants to see. They want to have a high-level visibility on their business. That is why we are still keeping the HPE products, and probably also in the future we'll have them.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user671328 - PeerSpot reviewer
Test Automation Engineer at a financial services firm with 1,001-5,000 employees
Vendor
We have a test automation solution that is really developer friendly. You can really use the development tools.

What is most valuable?

The most valuable feature is that we have a test automation solution that is really developer friendly. So, you have Java as a programming language. You have Eclipse or the Intel HAS IDE and you can really use the development tools. That's the best part out of it. You can also have this with Selenium or any other developer friendly solution, but UFT Pro also supports different technologies. So, you can test web applications, you can test Java applications, you can test Windows applications. And, most other tools, at least the free-ware solutions, only cope with one specific technology.

Another big feature is the integration with ALM. It's quite easy to start the test cases from ALM and to have the results in ALM. And it's also possible to make business process tests with Lean FT or UFT Pro. And I think all these parts together make it the best possible solution.

How has it helped my organization?

For example, we had just recently had the new release of our web page, and there we had a lot of test cases for small tools like a calculator for tax savings when you invest in different products, or whatever. There were a lot of little pieces on the website which needed testing. And we had an agile methodology to develop the new website and from time to time a new tool got released on the test system. And then we needed little effort to automate it and do the tests. And also, we could redo all the tests when a new version was released. So, we always had the security that nothing important changed or nothing which already worked was destroyed with the new release.

What needs improvement?

There are still some stability issues. Also, the integration with ALM is not perfect. There issues with parameter parsing.

We don't have ALM Octane now and I've never used it, so I don't know whether it would beneficial. But I think we're too big to easily switch to another test management solution.

What do I think about the stability of the solution?

Now stability is quite good. At the beginning, we had a bit of trouble with our company environment because the browser or the Java version is specifically configured and we had to fight a little bit to make it work correctly. Right now, we are very happy. Also, with the integration into ALM, it works quite good. We had some issues with special characters from ALM, to bring them to UFT Pro and backwards, but this is the biggest pain point right now, so it's not really a big deal.

What do I think about the scalability of the solution?

We have around three and half thousand employees. It is quite scalable. It depends how you do it. You can make automated scripts which do not scale at all. But since it's a developer friendly tool, you have the ability to cut it in the right way to make modules, and then it is very nice to handle it with multiple applications with a lot of test cases.

How is customer service and technical support?

Right now, we have a good experience with support because we quickly get to developers with issues. When we contact the support, if it is a bigger problem, we have a call or a session with the developers themselves and that's quite nice. They have also been at PostFinance twice. And this gives you a good feeling about being important and you think they care about you and they want you to have a product that works.

How was the initial setup?

Since I used to use a lot of other automation tools, it was very straightforward. It is quite simple if you know Selenium or if you know IBM Rational Functional Tester.

Which other solutions did I evaluate?

Compared to IBM Selenium, LeanFT or UFT Pro is more stable. They have better object recognition functionalities and more support technologies. Maybe they have a bit less browser support than Selenium, but that's okay.

Compared to any of the competitors that I’ve looked at, the HPE tool is a bit smaller. So, it makes it more fun to use it because you don't have such a large application as the Rational test suite or the Functional Tester. And I think it was more stable. So, even at the beginning, we had fewer problems than with Functional Tester and object recognition. But, I think both tools are not bad.

The major advantage of LeanFT or UFT Pro is that it is easier to integrate it into ALM. So, with Functional Test we always had these space scripts in ALM, and then we had to call Functional Tester somehow and bring the results back to ALM. It's easier with LeanFT.

What other advice do I have?

Try to build a test automation framework so that part of it could be managed by the development teams. And at least the page objects should be released together with the software to test. This makes everything easier for the test automation team. And makes the test automation solution faster.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Buyer's Guide
Download our free Functional Testing Tools Report and find out what your peers are saying about OpenText, SeleniumHQ, Tricentis, and more!
Updated: April 2024
Buyer's Guide
Download our free Functional Testing Tools Report and find out what your peers are saying about OpenText, SeleniumHQ, Tricentis, and more!