OpenText Functional Testing Lab for Mobile and Web Reviews

OpenText Functional Testing Lab for Mobile and Web can be used for a range of applications, not just web and mobile. It works very well for SAP, which is an enterprise platform. It can be used for Salesforce and other enterprise platforms where we have implemented these solutions.

Similar to how Tricentis has various tools within their portfolio, OpenText also has LoadRunner and ALM comparable to Qtest. They have their own suite of tools similar to Tricentis. In fact, Tricentis has the same set of tools that OpenText also has because OpenText has been in the market longer.

For mobile and desktop applications, we integrate with third parties such as BrowserStack or Sauce Labs. This is typically requested from the customer standpoint, and OpenText Functional Testing Lab for Mobile and Web allows direct integration with these third-party solutions.

Regarding CI/CD pipeline, there have not been any challenges. It is capable of delivering continuous testing and releases. As part of release cycles, when there is a push in a continuous integration model, we can trigger smoke testing and sanity testing. Once the test results indicate the release is fit for purpose, we implement impact-based testing from an automation standpoint and run regression tests. We have also enabled businesses in automation of UAT test cases. They perform witness tests of the automation scripting, occasionally requesting more data variety. From an automation standpoint, we enable it and it runs on a CI/CD pipeline.

OpenText Functional Testing Lab for Mobile and Web offers flexibility of deployment, from on-premises to UFT One which is on the cloud. They provide capability for immediate deployment, and assets can be migrated easily. They include enablers specifically for quick migration of test assets. While I have not personally been involved in these migrations, I have observed some clients using it directly while others make a complete shift from OpenText to Tricentis platforms. There have not been many clients moving from OpenText platforms from on-premises to cloud because most shifts have been toward different product categories such as Tricentis altogether.

We use it in financial services companies to automate mobile solutions and applications.

It allows multiple devices to be used and gives flexibility in adding devices when a project is needed. Most of the time, I have several devices where it is predefined. We can use it, but sometimes, we must scale it in a particular situation. It's very flexible.

It is very important because we can use a different approach to software testing, for example, to find a way to execute UFT software testing with only one execution. This reproduces all the platforms that we need.

There are various use cases, each tailored to the specific needs of our customers. When we consider Application Lifecycle Management (ALM), the use case significantly differs from Unified Functional Testing (UFT). Our primary objective is to assist customers in optimizing their software development life cycles. This involves facilitating decisions based on platform usage and the data entities they input into the system. We help them link these components, conduct automated functional and performance testing, and ultimately provide a definitive decision-making process. The goal is to ensure that when a customer is ready to launch a product or software, they can make a well-informed decision, either to proceed confidently or address any issues that may arise based on the data and testing results available within their systems.

There are numerous valuable features such as automation, the ones that facilitate importing and synchronization capabilities between our platform, Jira, and Azure DevOps. Also, traceability between various entities is of paramount importance. When introducing a new requirement or user story, it's crucial to establish links to associated defects, track test runs, and monitor test statuses. This traceability allows us to comprehensively map and document every aspect of the application delivery life cycle.

I use the solution in my company to test desktop applications.

The decision-making capabilities of the product help the product grow.

The product is easy to use.

OpenText UFT Digital Lab’s price could be better. They should introduce a pay-per-use subscription model.

The solution is easy to use. There are features to orchestrate mobile testing, including mobile testing automation. You can test different devices at the same time. 

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. 

We are a system integrator and this is one of the solutions that we provide for our customers.

The deployment model varies depending on the customer because some use this solution on-premises, and others use the cloud version.

The most valuable feature of this solution is virtualization.

The integration with Oracle projects is very simple and easy to use.

The fact that it allows users to test on real mobile devices instead of emulators is something that projects have told us is beyond compare. Your app or your website won't behave on an emulator like it will on a real mobile device, no matter how great the emulator is - even if it's the one that comes from the OS developer that ships with the development studio. There's just no substitute for a real mobile device with its hardware constraints and the way it will behave in the hands of a user.

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.