Upgrades are usually uninstalling and reinstalling, because you never really know how the upgrades are going to take. Lately, I just uninstall and reinstall because I have usually found that if I have an issue, the first thing they say is, "Well, have you tried uninstalling it and installing it fresh?" Kind of like, did you turn it on and off again? So, I usually just do that.

I don't even know if it's feasible, but if there was a magic box that said, "Here are all my machines and push the upgrade to all of them." It would be awesome.

The installation is pretty much a piece of cake. If you don't know what technologies you are testing, I would argue installing it might not be the first thing you should do anyway.

The initial setup is straightforward and I give it a nine out of ten.

The initial setup was not easy. I purchased three licenses because we were planning to hire people. When I started working on the solution, at a certain point, I got stuck and regretted purchasing it. My client had paid for it. I had a good experience later. However, in the beginning, it was really frustrating.

The solution's initial setup process is easy. I rate it as a ten.

The solution was straightforward to set up. I'd rate it seven out of ten in terms of ease of setup. It wasn't too complex. 

However, I wasn't directly involved with the initial setup and cannot speak to the deployment process. 

The initial setup of Micro Focus UFT One was not difficult. However, we had an IT team do it.

Deployment was quick. We're not on the cloud and all, so everything was done manually. We haven't faced any challenges in deployment.

The setup of Micro Focus UFT One is easy.

Initial setup is very straightforward and takes about 45 minutes, including one system restart. The tool installs the bare minimum of add-ins. To add more, it takes about 15 minutes.

Installing the Terminal Emulator add-in is easy, but configuring it is a bit tricky. This being a bit of a horse and cart issue, as you can't see the configuration option unless the Emulator is up and connected first.

I believe it was satisfactory. But the only challenge we had was whether there was support or not. The installation within the technology was fine, but if I wanted to use it across multiple technologies in an end-to-end integrative scenario, it was a little lacking. Unlike other tools.

They provide customized packages for each technology, just like other Windows, but we don't see that type of library with the UFT. They do have one, but I don't think it's very advanced.

The initial setup is pretty easy.

When I installed it on my virtual machine, it was less than an hour, and then it's up and running. We are well trained in such things, so maybe for one who is really new, this will take two or three hours to set up. I don't know. That said, it's not a major concern.

Setting up Micro Focus UFT One is straightforward. 

Setup is straightforward. It takes time, but it depends on the CPU that you have. It's a one-time effort. At maximum, you need one admin person to handle maintenance and deployment.

The initial setup for UFT is straightforward.

We didn't need to do too much with the initial setup because there is an installation team.

It takes one or two days to create test automation scripts.

Our deployment was completed in-house, and we have an in-house software development and architecture team. We do all our products and services and also provide services to third parties.

We found the initial setup to be very easy. It is very robust and leaves no room for making errors. The availability of config files for setting up all the installations from a single master configuration is nearly perfect. The customer would have no problem simply opening the machine and using it.

As for deployment, the time can vary. Sometimes there are only minor changes and sometimes there are a lot more changes. Including tests, and to be sure it’s working in all cases, it should take no more than one business day.

It’s the same for upgrades. OpenText support has advised us that, in case of an error or a problem with upgrades, they cannot be sure whether that problem would exist on a clean installation. So we always uninstall the entire product and install it on a clean system.

We use one or two people for deployment and maintenance, in the role of test automation engineers.

The solution is easy to install. The setup process takes a few hours and requires only one executive.

The implementation was carried out by the vendor but the rest was done either in-house or using third party providers. We carry out the maintenance using our admins. We're using the product intensively right now and we have around 80 or 90 users using it every day. 

The installation and setup of UFT One were relatively easy. I had to install it on my computer, and the only requirement was access to a license server. Overall, it wasn't a complex installation process. The deployment took about an hour.

It's extremely easy to set up.

The initial setup was very straightforward.

The setup process could be improved because reinstallation is required if you miss an add-in during initial setup. It would be beneficial to have an installation outline or information about selecting add-ins. 

Deployment is quick and takes only a couple of minutes. 

I did this kind of work for some years, so when I did the setup in the organization where I am now, I knew how to set up the product. It was a little bit simple. From that point of view, it is a normal installation; so it's okay.

The UFT is a simple product. With the exception of the licence server, a six-year-old can do it.

It is very straightforward in its install and setup. An extra layer of complexity exists when trying to integrate it with Quality Center, but this is done via some settings and an add-in. The nice thing about UFT is that it’s a mature tool that has massive user-forum support on the internet. Although there is a lot of support for C# (Coded UI) and Java (Selenium), there isn’t as much in regards to the testing side of those languages.

It is very easy to install and configuration is not required.

Deployment time takes three to four minutes, though it depends on the RAM and performance of the processor. However, if you install MS Office, that will definitely take some time.

The deployment is simple overall, takes less than 30 minutes, and I can handle it on my own. However, there's one thing. We have a UFT developer add-in built into UFT One. It takes more time to install if you aren't an expert. I think that needs to be communicated. This add-in isn't required, and it can slow down your system. That needs to be communicated, so only the useful add-ins need to be covered. Sometimes if there is an issue, and we need a deeper dive with the logs, we might need to contact support.

It is a straightforward product to implement.

It was straightforward, but there were typical issues, such as the normal configuration issues that you can predict, or you have to configure it to talk to the license server.

I was not involved in the initial setup. It was there when I got there. But I upgraded the licenses to a global license and we got both the full licenses and Run Time, so we're able to run it from continuous integration. That was

straightforward. Fairly easy.

The initial setup was straightforward. It did not take long to deploy because there are only two departments using it right now. It is not company-wide.

It's very straightforward.

The initial set-up of UFT is quick and easy. The set-up instructions are straightforward and easy to understand. However, for a few applications such as AS400 and POS, the set-up requires a few installation steps to be followed in a specific sequence. If this is missed, then UFT may not recognize application objects at all.

The initial setup was straightforward. It was easy to load and you're allowed to select the specific plugins you need to use with your applications.

The setup process was somewhere in between straightforward and complex. The vendor carried out the implementation for us; it would have been helpful to have better documentation. The solution doesn't require maintenance but when the version changes and you have to reinstall there might be some work involved. We're not using the solution on a daily basis, just when we need it.

The initial setup was a straightforward, step-by-step process.

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.

I was not involved in the evaluation of this product. I inherited it.

I would have been involved in the initial setup when it was originally installed. It was too long ago. It was originally QTP. That was a good few years ago. I used to look after the licensing, and the license servers, and all that kind of stuff and that's fine. It is very, very simple. The new licensing model is a lot easier.

There is a wizard for the set-up which I have always found to be simple and straightforward. That same wizard can be used to set up the license server, repair installations, install some add-ins, and some other features. It has always seemed pretty intuitive to me in terms of setting up QTP and UFT.

I was not a part of the initial set up. Installing the tool on my machine was straightforward based on my company’s instructions.

I'm not very involved in the technical part of setting up the solution. There's a specialized team that does the setup. There's another team using the setup and monitoring everything. Whenever there are some problems within the setup, I can refer to another team that can deal with issues.

My understanding is the setup requires some technical work, so those setting it up should be a bit knowledgeable.

Our team has also handled automation.

Due to the fact that the solution was in the organization before I began working with the company, I'm not sure how long deployment took.

I wasn’t involved in the installation, but it worked. It wasn't a big hassle.

The initial set up was straightforward once we cleared up some communication issues. The first end-to-end automated test was functional within a week.

It's straightforward.

The installation process of this software is very well organized. Here, all the prerequisites/supporting software are part of setup and it automatically configures your system for the best use during the installation. If in one or more parameters are missing the latest updates, it performs those updates automatically.

We faced a lot of problems during implementations, such as objection identification and cross-browser functionalities.

The initial step for me was straightforward as I have good technical skills. Therefore, it was easy for me to learn VB scripting and start preparing frameworks for UFT.

HPE UFT is quite complex to set up.

The setup was complex as we were required to have Windows updated. Also, there was apparently a Java conflict that had to be resolved first.

It was straightforward.

The initial setup was straightforward.

It was rather easy and you really can do it yourself.

Some parts of it were pretty easy to set up. Most of the issues we had were related to organizational stuff, such as managing licenses, etc.

Setup was easy and straightforward.

Everything is readable and easy to understand.

Initial setup was straightforward.

I don’t know, but I think it was fairly straightforward.

The initial setup is not complex. It's quite straightforward.

UFT setup is pretty straightforward.

It's hard to install the license seat because the web-based GUI is not user friendly.

It was already in place when I got here, so I don't know if the initial setup was straightforward or complex.

Depending on the approach you follow, the set-up is complex in different ways. Having an Object Repository that is not stored but built through the run is the most difficult and time consuming task. Custom libraries are also very time consuming to build.