The desktop applications have performance issues since they don't work properly or don't detect objects properly, making it in an area where improvements are required. The product's object detection method needs to be improved since it can help testers do perfect testing.
I believe there's always room for improvement in various aspects. For the most part, the key challenge is ensuring that customers fully utilize the product as intended and adopt the appropriate frameworks to implement the solutions effectively.
We need to scale devices easily. Some customers would like to loop in AWS or other cloud providers to check if their devices have the cloud factor. OpenText UFT Digital Lab needs to improve it.
Developer Automation Tests at a tech services company with 10,001+ employees
Real User
2019-08-05T06:23:00Z
Aug 5, 2019
I think the interface is not good very good and I have used other solutions that are easier to learn. Also the time it takes to connect the mobile and the interface is not up to speed. I think that there are other ways the product could be configured to detect devices more quickly in order to speed up use. When I connect my device to evaluate it can take a few minutes to see the device on my computer. I want to see better documentation because it was not so good in the last version. It needs a better explanation for implementing everything in Mobile Center. In the beginning, I had constant problems to connect Mobile Center because I could not find a good explanation to document Mobile Center working with EFT (Unified Functional Testing). I think that you cannot do this job without that kind of product support.
Learn what your peers think about OpenText Functional Testing Lab for Mobile and Web. Get advice and tips from experienced pros sharing their opinions. Updated: June 2025.
We like to host the tools centrally. We would need them to be multi-tenants, so different projects could log on and have their own set of devices and their own set of apps, and they wouldn't see data from other projects that are using it. Right now, the way that we're managing it is we're requiring no clients are able to access it, so if we do happen to see something that belongs to another project, it's not a big deal. But true segregation of devices and apps, packaged apps, that have been uploaded to the tool, is something that is important to us. It's not there right now.
OpenText Functional Testing Lab for Mobile and Web offers integration with HPE and non-HPE tools, real device testing, and device management. It supports real-time analytics and multi-platform testing, ensuring traceability and flexibility with decentralized devices.OpenText Functional Testing Lab for Mobile and Web is designed to enhance testing efficiency for mobile and desktop applications by allowing ease of integration with different testing environments. It features real-time analytics,...
Sometimes, it's challenging to have relations with OpenText support.
The desktop applications have performance issues since they don't work properly or don't detect objects properly, making it in an area where improvements are required. The product's object detection method needs to be improved since it can help testers do perfect testing.
I believe there's always room for improvement in various aspects. For the most part, the key challenge is ensuring that customers fully utilize the product as intended and adopt the appropriate frameworks to implement the solutions effectively.
We need to scale devices easily. Some customers would like to loop in AWS or other cloud providers to check if their devices have the cloud factor. OpenText UFT Digital Lab needs to improve it.
I would like to see more integration with automation tools. The integration and configuration should be made easier with tools on the same platform.
I think the interface is not good very good and I have used other solutions that are easier to learn. Also the time it takes to connect the mobile and the interface is not up to speed. I think that there are other ways the product could be configured to detect devices more quickly in order to speed up use. When I connect my device to evaluate it can take a few minutes to see the device on my computer. I want to see better documentation because it was not so good in the last version. It needs a better explanation for implementing everything in Mobile Center. In the beginning, I had constant problems to connect Mobile Center because I could not find a good explanation to document Mobile Center working with EFT (Unified Functional Testing). I think that you cannot do this job without that kind of product support.
We like to host the tools centrally. We would need them to be multi-tenants, so different projects could log on and have their own set of devices and their own set of apps, and they wouldn't see data from other projects that are using it. Right now, the way that we're managing it is we're requiring no clients are able to access it, so if we do happen to see something that belongs to another project, it's not a big deal. But true segregation of devices and apps, packaged apps, that have been uploaded to the tool, is something that is important to us. It's not there right now.
I try to find the backs and try to pull the future and quality of the development. For me, it's a great idea, but the tool is not finished now.