OpenText • Test automation
OpenText Functional Testing carries the UFT One lineage into a modern license, covering 200+ enterprise technologies in one tool and SAP, Oracle, Salesforce, Siebel, Epic EHR, Oracle Cerner, mainframe, web, mobile, and API. Merito builds the framework.
Merito sells OpenText Functional Testing and delivers framework design, SAP and cross-system automation, and CI/CD integration for regulated enterprises whose test scope crosses legacy and modern technologies.
What it is
OpenText Functional Testing (formerly UFT One under Micro Focus) is the enterprise functional automation product with the deepest coverage across legacy and modern stacks. It automates SAP GUI, Salesforce Classic and Lightning, Oracle EBS, Oracle Cerner, Epic EHR, Siebel, PeopleSoft, Microsoft Dynamics, web, mobile (through Functional Testing Lab), API, and multiple mainframe terminal technologies in one product, with 200+ enterprise technologies supported in total.
Python authoring is the modernization story. Automation engineers code around edge cases in Python instead of fighting low-code or no-code limits, plug AI assistants into a language the entire industry already speaks, and use the broader Python ecosystem (data libraries, OS automation, custom utilities) wherever scripts need it. The framework stays modern instead of locked into a proprietary surface.
Functional Testing's coverage breadth is the reason large regulated enterprises keep it. Programs that run automation across SAP GUI, mainframe, legacy thick clients, and modern web rarely find a single alternative that covers all of it. Replacing Functional Testing in those environments typically means adopting two or three separate tools, which creates more governance cost than it saves.
What kills Functional Testing adoption is framework drift. Tests authored script-by-script instead of as shared object-repository patterns create maintenance debt that grows faster than the test suite. Merito's engagement starts with object repository architecture, data-driven patterns, and CI/CD wiring so the investment compounds.
Ideal use cases
What it is best at
Native Python support lets automation engineers code around edge cases instead of fighting low-code or no-code limits. Engineers use AI assistants in a language they already know, integrate freely with the broader Python ecosystem, and skip the hassle of fragile drag-and-drop authoring.
SAP GUI, Salesforce, Oracle EBS, Oracle Cerner, Epic EHR, Siebel, PeopleSoft, web, mobile, API, and multiple mainframe technologies live in a single automation product, with 200+ enterprise technologies supported overall. Cross-technology flows do not hand off between tools.
Tests that reference shared repositories instead of hand-coded locators survive application changes. The framework design work compounds across the life of the automation footprint.
The QTP and UFT lineage means most enterprise QA teams have practitioners who know the product. Merito's framework discipline is the differentiator, not the tool itself.
Core capabilities
Enterprise and legacy technologies covered in a single automation product.
SAP automation engine
SAP GUI, Fiori, WebDynpro, and CRM coverage with SAP-certified recognition.
Cross-system automation
End-to-end flows that span SAP, Salesforce, Oracle Cerner, Epic EHR, Siebel, mainframe, and web in one test.
Mainframe coverage
3270, 5250, and VT100 terminal automation alongside modern web.
API and headless testing
REST, SOAP, and web service testing with data-driven orchestration.
Python authoring plus object-repository discipline separates sustainable automation from brittle scripts.
Python authoring
Engineers script around edge cases in Python, use AI assistants in a familiar language, and reach for the broader Python ecosystem when scripts need it. No low-code or no-code lock-in.
Shared object repositories
Reusable recognition patterns that survive application refactoring.
Data-driven patterns
Parameterized data sources, environment switching, and parallel execution.
Business Process Testing
Reusable business-component libraries layered above technical automation.
Functional Testing as the automation layer inside enterprise release pipelines.
CI/CD triggers
Jenkins, Azure DevOps, GitHub Actions, GitLab CI triggers at pull request, merge, or release stages.
Functional Testing Lab integration
Real-device and cross-browser execution via Functional Testing Lab for Mobile and Web.
Core SDP reporting
Results roll up into Core Software Delivery Platform dashboards and Application Quality Management traceability.
Where it fits in the stack
Deployment and implementation
Licensing and packaging
Functional Testing base
Authoring and execution for enterprise functional automation.
Best for: Automation programs covering SAP, Siebel, Oracle, web, and API.
Functional Testing with Functional Testing Lab
Adds real-device and cross-browser execution through the lab product.
Best for: Programs automating mobile and cross-browser web alongside enterprise apps.
Merito services
Merito sells licenses and the delivery work around them. Pick the service that matches where you are in the lifecycle.
Object-repository architecture, data-driven patterns, and CI/CD integration.
Explore service02SAP-specific test suites for S/4HANA, ECC, Fiori, and SAP GUI.
Explore solution03UFT One to OpenText Functional Testing transitions and legacy QTP modernization.
Explore service04Functional Testing wired into CI/CD pipelines across SAP and non-SAP pipelines.
Explore service05Named engineer, priority SLAs, and release-time coverage for Functional Testing in production.
Explore service06Role-based training for automation engineers and test architects.
Explore service07Merito-placed Functional Testing engineers and SDETs embedded on long-running programs.
Explore serviceFunctional Testing licensing
Merito sells OpenText Functional Testing and delivers the object-repository design, SAP regression authoring, and CI/CD integration that turn automation into a sustainable capability.
Merito point of view
Merito has seen large Functional Testing footprints (previously UFT One) where the tool works fine, object recognition is solid, and tests still require constant babysitting. The cause is almost always framework design and tests authored as scripts with hand-coded locators instead of shared object repositories. That is a framework problem, not a product problem, and no tool replacement fixes it.
Merito recommends Functional Testing specifically when test scope crosses SAP GUI, mainframe, legacy thick clients, and modern web. For web-only programs with strong SDET skill depth, Playwright or Cypress could be the better call; Merito delivers both. The honest question is whether Functional Testing's coverage breadth is actually being used.
For SAP-dominant programs, Merito typically pairs Functional Testing with Tosca or SAP Enterprise Continuous Testing rather than replacing one with the other. The two products cover different authoring profiles, and regulated programs often want both in the portfolio.
What buyers usually underestimate
Related from Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Consultation request
Share your application scope and automation posture. A Merito Functional Testing specialist follows up within one business day.
Coverage breadth
Functional Testing shines when automation crosses legacy and modern stacks. Merito advises on whether the breadth is being used.
Framework first
Merito's engagements start with object-repository architecture. That is what determines whether your automation footprint compounds.
Next step
A Merito Functional Testing engagement kicks off with object-repository architecture, data-driven patterns, and CI/CD wiring. Framework discipline in month one pays back for years.