OpenText Functional Testing Reviews

We use the solution for defect tracking and test automation features.

They should include AI-based testing features in the solution for assessment and identifying potential databases.

We have been using the solution for more than ten years.

It is a scalable solution. I rate its scalability as a ten.

The solution's customer service is excellent. They always prioritize our tickets.

Positive

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

We purchase the solution's yearly license. It costs 700k. There are no additional costs involved.

The solution is easy to integrate and adapt for manual testing. It manages tests very well. It is an excellent tool in terms of customization. I rate it as a nine.

We use the solution for API functional testing to analyze user interface, business logic outputs, etc.

The solution's user interface is good. It is easy to use for a nontechnical test as well.

They should improve the solution's tracing functionality. There should be an automated feature to load the backlog of test requirements.

We have been using the solution for eight years.

It is a stable solution. I rate its stability as an eight.

We have three solution users in our organization.

The solution's technical support team is good. Although it could have been faster while resolving the licensing error issue, we encountered some time back.

Positive

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

The solution's price is reasonable compared to other vendors. I rate its pricing as a four.

I advise others to speak with automation engineers to know the success criteria for the solution's proof of concept. Moreover, UFT needs to give insights on production status like Worksoft or Tricentis. Thus, I rate it as a seven.

I recently took became a QA for our company and was trained on various tools including the solution as part of job orientation. 

We have 100 engineers in our company who use the solution for automation testing. 

It is very easy to create shared repositories that can be used throughout all testing. This feature makes our jobs easier. 

The speed could be improved because a large test suite takes some time to execute.

The solution's size could be improved because it takes up a lot of space. 

I have been using the solution for one year. 

The solution is very stable. 

The solution is scalable. 

There was one issue so support was emailed for assistance. I am not sure of support's response because it was handled by our unit manager.

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. 

Technical support from Edgewood guided us through the initial setup and installation. 

One in-house engineer can handle ongoing maintenance. 

Our engineers were also were trained on and use TestComplete. 

I like the direction the solution is heading and am really happy with how they keep adding new features. 

I rate the solution an eight out of ten. 

We use Micro Focus UFT One for testing web pages and the script is in AngularJS.

Micro Focus UFT One could improve by having more maintenance. Every time when we run the solution and develop something, the next time when we run it it doesn't recognize the object. I have to redesign the object again and then run the solution. It's really a headache, it's not consistent.

I have been using Micro Focus UFT One for approximately three years.

Micro Focus UFT One is not stable.

The scalability of Micro Focus UFT One is good.

The support from Microsoft is not good. They are very lazy in answering anything. If we create a request, it takes months for them to respond to us.

I have used previously C Sharp and Selenium HQ, and I prefer them over Micro Focus UFT One.

The setup of Micro Focus UFT One is easy.

I would advise others to use Selenium HQ and C Sharp because they are better, consistent, reliable, and scalability than Micro Focus UFT One.

I rate Micro Focus UFT One a five out of ten.

Micro Focus UFT One is an automation tool, that is primarily used to automate web and desktop applications.

It is very simple to use, and the scripting language is even easier.

Object Identification is very easy. 

The integration with other test management tools is good, which is very good.

When it comes to pricing Micro Focus is expensive, and it doesn't support test case panel execution.

I think that over time, Micro Focus has not really understood the market needs.

They are still improvising the UI. 

They need to really understand how this tool fits into the DevSecOps ecosystem. We have been giving that advice, but they have not taken it into account.

I would want to see a significant improvement in the tool's features. The most significant enhancements are support for panel execution and integration with DevSecOps.

I have been working with Micro Focus UFT One for ten years.

We are working with the latest version.

It's very nice. The stability is good.

Micro Focus UFT One is a scalable product.

We have approximately 100 end users in our company who use this solution.

I am reducing my usage slowly. I am reducing 30 to 40% of the licenses.

We have contacted technical support. They're fine. I don't see the benefit in the chats I had with them about the issues we were having. They are, nonetheless, fine. Our requirement was a far more serious issue. As a result, they were unable to assist us. They're fine, though. They are quite knowledgeable.

Previously, we did not use another solution.

The initial setup was very straightforward.

We did not need any assistance. We are good with the knowledge that we have internally.

We have to pay for licenses. The licensing fee is paid on a yearly basis.

The price is one aspect that could be improved.

I would not recommend this solution to others who are considering it.

I would rate Micro Focus UFT One a five out of ten.

We use it for automation. It helps to automate test scenarios for graphical user use cases.

Historically, we have faced a lot of maintenance issues with automation using traditional UFT, because UFT has a mechanism for identifying an object where you have to add object properties. However, if a change happens in the application and your object properties change, then you have to go and update the object properties again, only then can you use those scripts. So, we were using a lot of personnel for script maintenance. Whereas, in UFT One, I like that our maintenance costs have been reduced by a lot because UFT One is using an artificial intelligence feature to identify objects visually.

We use it to do multi-platform testing. 

UFT One Automation provides Codeless Test Automation.

The solution will automatically run a script, so you need less knowledge to run a script.

OpenText UFT One gives us integration capabilities with both API and GUI components. I like the user interface. It doesn't require that much skill to use and has automatic settings, which is useful for users who don't know what to select. It also has dark and light themes.

It improves automation efficiency.

The AI feature needs improvement. For banking applications, we input formatted text from documents, but the AI feature is recognizing three fields as one field, e.g., for a phone number, it puts all 10 digits in the international code or country code. Then, the script fails. 

I have been using UFT for the last seven or eight years. UFT One was just launched three or four months back, so I have been using it for a couple of months. 

It is reliable. Sometimes, the GUI does crash.

It is highly scalable. 

There are around 150 users of UFT One with 8,000 test scenarios running four times a month. We are also running around 500 scripts in UFT One.

Our internal team is sufficient for technical issues.

We have used a lot of different tools. We have used Selenium and Python as well as Java-based REST API for regular testing. With UFT one, we have all the solutions under an umbrella, so we don't have to think about other tools. It also supports API and HTML testing. Selenium only supports Java, and there is no support for HTML.

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.

Object maintenance is reduced.

We have not yet implemented the license for the AI features. However, I got a chance from OpenText to join a Hackathon for India when they launched the product, which included the AI feature. I am hoping that my company will implement this feature soon because the solution's AI capabilities will reduce my test creation time.

Every day, tools are getting smarter. UFT One is like this.

Before implementing, do a demo with your existing applications.

I would rate this solution as an eight out of 10.

We are responsible for automation of the regression test cases. We have a standard set of regression test cases, which are comprised of SAP solutions, web-based applications, as well as some Windows-based applications. We have test cases which cater to each of these solutions individually.

In addition, we have test cases to test things from end-to-end. That means the data has to flow from one application to another and it has to be validated. We write reusable pieces of code, which are stitched together to create the end-to-ends.

In SAP, transaction codes are available and they are automated. They are stitched together to form a test case. For example, if a customer places an order on the website, we will get an order number in SAP. We will process that order in SAP to create the delivery with a particular T-code. Once we process that delivery, we will mark it as "good session," which means the order itself will flow out of our warehouse via the transportation. Once the customer receives it, we have the invoicing process. We automate these individual T-codes, and then stitch them together.

In our organization, a developer will develop a piece of code and give it to us. We will test it and tell them about any issues or defects. The way we do that is we automate some piece of their code, whatever the core functionality is, and get ready for the next iteration. That means that when the sprint goes from Sprint 1 to Sprint 2, we make sure that Sprint 1 is not impacted because of new code deployment. The way we have benefited from UFT is that we are not using manual regression testing. Whatever code we have developed will be enhanced in Sprint 2 , and we keep that piece ready for Sprint 3 regression. Therefore, over a period of time, we will have the flow ready, and we don't have to do manual testing from scratch for every release.

Previously, we were doing manual testing for each sprint, and when we got to an advanced sprint, like Sprint 4 or 5, we would have to stop and test that entire functionality again. UFT has helped us a lot in reducing the manual effort and in passing the savings along to our client. Regression efforts have been reduced by at least 20 percent, if not more.

Initially, we were using UFT 12 or 12.53 and then we started slowly increasing by installing the patches and moving to the next versions. When compared with UFT and manual execution, we have definitely saved a lot of effort, somewhere in the range of 60 to 70 percent when compared with our efforts to manually test. A script which takes around half an hour to execute in automation takes around 3.5 hours for manual execution, along with documentation because we execute things in a way that it creates the documentation as well.

It is easy to automate and new personnel can start learning automation using UFT One. You don't have to learn any scripting. There are many people on my team who have started learning automation.

I have been using UFT for a couple of years, but I have only been using UFT One for the past two to three months. I am still learning many things about UFT One.

We haven't faced many issues with UFT One in terms of stability. If your system meets the requirements they indicate, you should not face problems. In a machine where we had less memory, we did have some trouble. Since we upgraded the memory for that machine, we have not faced any memory issues or stability issues with UFT One.

Scalability, for our needs, has worked spectacularly well. There were some issues that we were facing with some of the patches. They were taken under consideration by OpenText and we got proper updates from the team.

When we want to increase the number of people in a team, because our licenses are limited, we sometimes face an issue, but that is not their problem because we have chosen limited licenses. We sometimes find it difficult to get people onboarded when we have a lot of work and that sometimes hinders the work. With an open source tool, you don't have any such problem. If you have a lot of work and you want to onboard more people you get it done.

Because our project was already in UFT, we are trying to utilize UFT One to have proper capabilities in AI and for automation from screenshots. But it is good to see a lot of changes and we are trying to utilize them in our upcoming releases and projects.

Support is okay. We have not faced many problems. But if we do face some issue, we can definitely raise a ticket and the ticket is looked into. I don't have any complaints about customer support. I would rate it about an eight out of 10.

It's not a 10 because what happens with some of our issues is that we might not get a patch quickly and we have to hold on to an application until we get a proper solution.

I have certification in Tosca and UiPath.

Tosca is basically scriptless automation which is also good. UiPath is not technically for regression testing, it's an RPA tool. You don't have validations, per se; you have to create them. Because I have a longer period of association with UFT, and some of the other tools did not help me in some situations, I go with UFT.

From my experience, UFT One is good in terms of automation of multiple applications. For example, if you have five applications and any one of them is not suitable for automation by UFT One, you may have to re-think using it. But if all the applications are compatible with UFT One and you are able to automate, it's better to go with UFT One. 

We don't have much continuous testing in our process because we don't do Agile testing, but we do have some amount of testing for what we call "rapids," for defects or announcements. It is useful when it comes to the second or third sprints where there are use cases in which we can leverage speeding up the testing. But we haven't used UFT One for a continuous delivery, as in from build to deployment.

There are several new features which we can explore and use for continuous testing, but our project, not being Agile right now, has limitations in that regard. Management is looking to convert it into an Agile project soon and I expect we will start using UFT One full-fledged, with all its features.

I'm very comfortable with the UFT One for our project needs.

UFT (erstwhile QTP) is a widely popular test automation tool. During my initial days, I used UFT extensively to automate test cases. Now, with the latest version of OpenText UFT One, there are added features that address the new-age testing requirements. In my current position as Practice Head of Test Automation competency at a Tier 1 company, we propose various befitting tools to our existing or new customers. Whenever we work on a particular solution or requirement, we propose automation tools to support the entire environment to support end-to-end automation. If my customer is looking for an automation solution, they will typically ask, "Can you provide a solution to automate my end-to-end scenario?" Every proposal or potential requirement is a new business case for us.

In some of our recent customer requirements, we have proposed the OpenText UFT One tool. The primary reason behind this is that a customer may have different systems, for e.g., a mainframe system, which is a legacy technology, their current web applications, like AngularJS or ReactJS, could include SAP ERP. In such an ecosystem, UFT One is the right fit to automate end-to-end systems.

Scripting is a basic feature of UFT One. Some tools may use programming languages like Java, Python, or Ruby; but UFT One uses a very basic, simple programming language called VBScript. The advantage of VBScript for a manual tester is if he/she has a basic knowledge of automation, and loops/conditions, then he can easily understand whatever script is created in UFT One, using VBScript. The point is that VBScript is very easy to understand with minimal knowledge. It can easily be modified as per requirement. UFT One all the technologies including a legacy to modern technologies.

For one of our customers, we proposed integration between UFT One and Azure DevOps (ADO). We were able to easily establish that integration, which means the solution's integration capability with third-party tools is s. With some tools, you may need additional effort to communicate with source code management (SCM) tools, whereas UFT One connects easily. There is a keyword view available in UFT One. Using that keyword view, you can see all the statements in proper order.

UFT One has its own feature called Test Combinations Generator to prepare test data. If I have data in an Excel file, then it is very easy to create an object in either Notepad, file system object, or database object. We can easily retrace the data.

Particularly, I like the Help feature in UFT One. For example, if you are navigating a particular window, where there are different options. One wouldn’t know the purpose of every option, but there is no need to search because that window contains a Help button. If you click on that Help button, it directly navigates to the respective help needed.

UFT One supports AI features to automate web and mobile applications. For example, suppose, if earlier there was a button in the left corner, which now has moved to the right corner. In such a situation, we would need to update the script. However, with AI, there is no need to update the script. Within the screen, if that particular button is placed anywhere on the screen, then we can easily handle it and the script will not fail. The integration part is very easy for mobile automation, as well.

We can also automate PDF and forms, using UFT One. For example, one of our customers prepared a lot of macros in an Excel file and created their own custom options in the toolbar. Their requirement was to automate the Excel file, but not read the data, so we had to handle the different icons in the Excel file. Therefore, it generated the pivot table, selecting different options in the pivot table and validating some third-party applications.

UFT One can automate different technologies like SAP, Oracle, SFDC, Microsoft products, Mobile applications, and many more technologies.

From a sales pitch perspective, everyone is now looking for script less automation, whether they are using the feature or not. So, if UFT One is made as a script less tool entirely, that would be very good.

UFT also has a recording feature. They could make the recording feature window bigger for whatever activities that I am recording. It would improve the user experience if they could create a separate floating panel (or have it automatically show on the side) once the recording starts.

We have been using the solution for 13 to 14 years. I started by using an older version of UFT One, Quick Test Professional (QTP) 6.5.

UFT One is 100 percent stable. There have been no crashes of any kind.

It is easily scalable. It supports increases in automation as well as integrates with third-party tools, like ALM Octane and Jenkins.

OpenText technical support is prompt. They will try to get you a proper solution to your inquiry.

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.

Our customers are always looking to reduce their efforts. This solution will give you such an advantage.

Depending on the landscape and stability of the customer application, they should see ROI (or the breakeven point) within six to nine iterations.

The license is important. If the license is up and running when you open it, there won't be any issues.

Compared to other tools in the market, UFT One is very cheap. The recent Covid pandemic situation also hit customer budgets significantly, so OpenText offered some discounted prices, which is definitely competitive.

There are a lot of tools available in the market, however, the primary advantageous feature identified in UFT One is simple: It supports legacy to modern technologies. This is why I propose UFT One.

Everybody is aware of mainframe systems because of Y2K. This solution supports a lot of terminal emulators that communicate and connect to mainframe systems. That is one of its key advantages. Some automation tools provide only a fewer number of terminal emulators, but UFT One supports a lot of terminal emulators to communicate with mainframes.

If someone is new to test automation, we will typically propose UFT One.

OpenText recently started offering UFT One as a PaaS, which has been helpful for our customers.

I would rate this solution as a nine (out of 10).