Shared execution for QA-authored and developer-authored tests
Functional Testing and Functional Testing for Developers both target the same lab, so coverage stays consistent across teams.
OpenText • Test automation
OpenText Functional Testing Lab for Mobile and Web
Functional Testing Lab is the execution home for mobile and cross-browser tests authored in OpenText Functional Testing and Functional Testing for Developers. Merito wires the lab into real CI pipelines.
Merito sells OpenText Functional Testing Lab for Mobile and Web and delivers real-device and cross-browser execution wired into CI/CD, with coverage coordinated across Functional Testing and Functional Testing for Developers.
- Best for
- QA Leaders owning mobile and cross-browser coverage, SDET Managers integrating mobile execution into CI/CD, Test Architects designing device and browser coverage matrices
- Hosting
- Hybrid
- Time to value
- First CI-triggered mobile or browser run in as little as one week. First CI-triggered mobile and cross-browser runs in four to six weeks. Full device and browser matrix coverage in three to four months.
- Security posture
- SOC 2 Type II, ISO 27001, GDPR
- Last reviewed
- 2026-04-26
What it is
OpenText Functional Testing Lab for Mobile and Web in the enterprise stack
OpenText Functional Testing Lab for Mobile and Web (formerly UFT Mobile and Mobile Center under Micro Focus) is the device and browser execution companion to Functional Testing and Functional Testing for Developers. It provides access to real iOS and Android devices and a controlled grid of desktop browsers so tests author once and execute across device and browser matrices.
Functional Testing Lab is not a standalone authoring tool. It is the execution surface for tests already authored in Functional Testing or Functional Testing for Developers. Its value is removing the infrastructure burden of maintaining local device farms or BrowserStack-style third-party lab spend that grows unpredictably with program scope.
Merito's engagement scopes the device and browser matrix first and what platforms actually need coverage, what volumes run per release, and what concurrency is required during release windows. Over-provisioning the lab is as expensive as under-provisioning it.
Ideal use cases
- Real-device iOS and Android execution for mobile regression
- Cross-browser desktop execution (Chrome, Edge, Firefox, Safari)
- CI-triggered device and browser matrices on every pull request or release
- Controlled execution environments for regulated industries
- Consolidating off BrowserStack, Sauce Labs, or maintained local device farms
What it is best at
Where OpenText Functional Testing Lab for Mobile and Web earns its seat
Controlled environment for regulated programs
On-prem and private cloud deployment keep test execution inside customer governance boundaries. Devices stay on networks compliance teams control.
CI-native with concurrency controls
Lab concurrency is budgeted per project and per pipeline so mobile regression scales with release frequency without runaway spend.
Core capabilities
OpenText Functional Testing Lab for Mobile and Web capabilities, grouped by outcome
Mobile execution
Real iOS and Android devices, physical or cloud-hosted, available to authored tests.
iOS and Android coverage
Native, hybrid, and web mobile testing across OS versions and device form factors.
Device farm management
On-prem or private-cloud device management with reservation, debugging, and logs.
Real-device debugging
Screencast, device logs, and network capture for triaging mobile test failures.
Cross-browser execution
Desktop browser matrix execution with controlled version pinning and concurrency.
Chrome, Edge, Firefox, Safari
Full desktop browser matrix with controlled version pinning for regression stability.
Parallel execution
Browser concurrency budgeted per project for predictable release-time throughput.
Headless and headed modes
Fast headless runs for CI plus headed runs for visual and accessibility validation.
Pipeline integration
Functional Testing Lab wired into the same pipelines that run functional and performance tests.
CI/CD triggers
Jenkins, Azure DevOps, GitHub Actions, GitLab CI triggers with per-job device allocation.
Concurrency budgeting
Reservation rules so release-time surges do not starve development teams of devices.
Core SDP and AQM reporting
Lab execution results flow into Core Software Delivery Platform and Application Quality Management dashboards.
Where it fits in the stack
How OpenText Functional Testing Lab for Mobile and Web connects to the rest of your landscape
OpenText DevOps catalog (native)
Native- OpenText Functional TestingPrimary authoring environment; tests execute in the lab.
- OpenText Functional Testing for DevelopersDeveloper-authored tests execute in the same lab.
- OpenText Core Software Delivery PlatformExecution results consolidated in Core SDP dashboards.
- OpenText Application Quality ManagementTraceability for lab execution against test cases in AQM.
Open-source frameworks (certified)
Certified- AppiumStandard Appium protocol for mobile automation against lab devices.
- Selenium, Cypress, PlaywrightWebDriver-based web tests execute against the browser grid.
- XCUITest, EspressoNative iOS and Android unit and UI tests execute on lab devices.
CI/CD (custom)
Custom- Jenkins, Azure DevOps, GitHub Actions, GitLab CILab execution triggered from build pipelines with reservation rules.
- Corporate identity and device policySAML SSO and device policy enforcement for regulated execution environments.
Deployment and implementation
How it rolls out
- Hosting
- Hybrid (North America, EMEA, APJ)
- Implementation complexity
- Moderate
- Typical time to value
- First CI-triggered mobile or browser run in as little as one week. First CI-triggered mobile and cross-browser runs in four to six weeks. Full device and browser matrix coverage in three to four months.
- Prerequisites
- Device and browser coverage matrix agreed with product and QA leaders
- Network access for device farms, or private-cloud device hosting decision
- CI pipeline integration points identified
- Existing Functional Testing or Functional Testing for Developers footprint if shared
- What Merito usually handles
- Merito handles Functional Testing Lab setup, device-farm sizing, browser-grid provisioning, CI integration, and concurrency rules. Lab administration typically stays with the customer after cutover; Managed Services and Staff Augmentation cover ongoing operations when the program wants Merito to run them.
Licensing and packaging
How it is bought
- Model
- Subscription
- What to expect
- OpenText Functional Testing Lab for Mobile and Web is subscription-licensed with packaging keyed to device slots, browser concurrency, and user counts. Pricing depends on concurrent device count, browser grid size, and private-cloud versus on-prem deployment. Merito sells Functional Testing Lab alongside Functional Testing and Functional Testing for Developers when both author tests against the same execution surface.
- Editions and modules
Functional Testing Lab standard
Shared device and browser lab with concurrency budgeting across teams.
Best for: Programs consolidating mobile and cross-browser execution.
Functional Testing Lab private cloud
Dedicated device hosting inside customer-controlled cloud boundaries.
Best for: Regulated industries requiring controlled execution environments.
- Common expansion areas
- Additional device slots as mobile scope grows
- Browser concurrency upgrades for release-time surges
- Functional Testing seats for teams sharing the lab
- Core Software Delivery Platform consolidation
- Managed Services for long-term run support
Merito services
How Merito helps you win with OpenText Functional Testing Lab for Mobile and Web
Merito sells licenses and the delivery work around them. Pick the service that matches where you are in the lifecycle.
01
Functional Testing Lab Rollout
Device and browser matrix design, lab provisioning, and CI integration.
Explore service02DevOps Consulting
Mobile and cross-browser execution wired into release pipelines.
Explore service03Upgrade and Migration
Mobile Center and UFT Mobile transitions into current Functional Testing Lab.
Explore service04Premium Support
Named engineer, priority SLAs, and release-time coverage for lab availability.
Explore service05Managed Services
Long-term run support for Functional Testing Lab including device-farm operations.
Explore service06Training and Enablement
Administrator and CI integration training for teams consuming the lab.
Explore service07Staff Augmentation
Merito-placed mobile and CI engineers embedded on long-running programs.
Explore serviceFunctional Testing Lab licensing
Buy the lab from the partner that also designs the coverage matrix.
Merito sells OpenText Functional Testing Lab for Mobile and Web and delivers device and browser matrix design, CI integration, and concurrency rules that scale with release cadence.
Merito point of view
Device matrices are a governance problem, not a procurement problem.
Merito has seen customers stand up device farms without a coverage matrix, over-provision to feel safe, and find themselves carrying devices that never get booked. The problem is that device and browser decisions are treated as an infrastructure line item rather than a release-governance decision. Merito starts lab engagements with the matrix and what platforms are we required to support, at what concurrency, at what release cadence.
Private cloud could be the right answer for regulated programs. Public cloud device farms are often faster to adopt but put test execution outside customer governance boundaries. For financial services, healthcare, and defense customers, Functional Testing Lab's private-cloud option is usually worth the incremental cost.
Functional Testing Lab and OSS frameworks coexist. Merito routinely sees programs authoring in Cypress or Playwright and still using the lab for browser concurrency and real-device access. That is a perfectly good pattern; the lab does not force an authoring choice.
What buyers usually underestimate
- Provisioning a device farm without a release-tied coverage matrix.
- Picking public cloud device hosting when regulatory boundaries require private hosting.
- Skipping concurrency budgeting, so release surges starve development teams.
- Buying Functional Testing Lab when BrowserStack or Sauce Labs actually meets the scope and regulatory profile.
- Not wiring the lab into CI, so mobile runs still happen locally on laptops.
Related from Merito
Continue exploring OpenText Functional Testing Lab for Mobile and Web on Merito
Related solutions
Related services
Related products
- OpenText Functional TestingAuthoring environment whose tests run in the lab.
- OpenText Functional Testing for DevelopersIDE-authored tests execute in the same lab.
- OpenText Core Software Delivery PlatformExecution results consolidated in Core SDP dashboards.
- OpenText DevOps AviatorAI-assisted defect categorization from lab runs.
- OpenText (vendor portfolio)OpenText hub and the full DevOps and Content catalogs.
Frequently Asked Questions
OpenText Functional Testing Lab for Mobile and Web FAQs
Consultation request
Talk to Merito about OpenText Functional Testing Lab for Mobile and Web
Share the device and browser matrix you need to cover and whether regulated execution applies. A Merito lab specialist follows up within one business day.
Controlled execution
Private cloud for regulated programs
Functional Testing Lab's private-cloud option keeps device execution inside customer-controlled boundaries.
Matrix first
Coverage tied to release governance
Merito sizes the lab from the required coverage matrix, not from a generic hardware catalog.
Next step
Size the matrix. Pick the hosting. Wire CI.
A Merito lab engagement starts with the device and browser matrix, picks the deployment shape, and wires CI into release gates.