

OpenText Functional Testing and mabl are two competitors in test automation. While OpenText earns praise for its customer support, mabl is often seen as superior due to its feature set.
Features: OpenText Functional Testing provides extensive automation capabilities, detailed reporting tools, and robust support. mabl offers advanced automation solutions by integrating machine learning, supporting continuous delivery, and providing innovative automation features.
Ease of Deployment and Customer Service: OpenText is straightforward to deploy with strong customer support, ensuring quick issue resolution. mabl's cloud-based deployment seamlessly integrates but may require technical expertise to maximize its potential. OpenText is more accessible for users prioritizing ease of setup, while mabl attracts those focused on advanced technology.
Pricing and ROI: OpenText Functional Testing has a higher initial setup cost, reflecting its comprehensive support structure, which enhances ROI through reliable support. mabl offers a competitive pricing model with significant ROI potential due to advanced features, though additional investment in training and integration may be necessary. OpenText is valuable for customer support and ease of use, while mabl's features may justify further investment for those valuing functionality.
| Product | Mindshare (%) |
|---|---|
| OpenText Functional Testing | 8.7% |
| mabl | 1.0% |
| Other | 90.3% |

| Company Size | Count |
|---|---|
| Small Business | 20 |
| Midsize Enterprise | 13 |
| Large Enterprise | 74 |
mabl is the agentic testing harness that helps quality keep pace with AI-powered development. It combines specialized testing agents with deep application context to continuously validate customer experiences across web, mobile, and APIs, independently from the developers and coding agents that wrote the code.
Coding agents let teams create and change software faster than ever, but testing, maintenance, and failure investigation haven't kept up. mabl brings validation into the tools developers and coding agents already use, keeps tests current as the application changes, and records the evidence behind every release decision. Teams spend less time maintaining tests and chasing failures, and more time building.
What features make mabl valuable?
Independent validation: mabl tests every change separately from the systems that created it, checking real customer workflows across web, mobile, and APIs, including MFA logins, API calls, database checks, and PDF downloads.
Testing in the tools developers use: mabl's MCP server and installable skills connect to Claude Code, Cursor, VS Code, and other coding agents. Developers can build coverage, run the tests a change affects before a pull request merges, and debug failures against a local build.
Agentic test creation: Describe a test in plain language or hand mabl a Jira ticket. mabl builds the test, replays it to confirm it passes, and saves it in a step-by-step editor anyone on the team can read.
Adaptive auto-healing: When the UI changes, mabl updates the affected tests and scores every heal for confidence. Assertions are never healed, so real defects still fail.
Agentic failure analysis: Every failed test comes with a likely root cause and a recommended fix, separating application bugs from test and environment issues.
Traceable evidence and control: Every run produces a tamper-evident record that connects to Jira, Xray, TestRail, and Azure Boards. Agent activity tracking and agent instructions let teams see and set how mabl's agents work.
What benefits and ROI can be expected?
Less time validating software: SealingTech cut test execution time by 86%, and JetBlue runs tests 9x faster.
Faster test creation: Mercedes-Benz cut test creation time from 10 hours to 1 hour.
Lower maintenance burden: Momentum Energy reduced test maintenance time by 90%.
More capacity and more reliable releases: LeadingReach avoided hiring five senior QA engineers, saved $500K, releases 2x faster, and reports zero production bugs since adopting mabl.
mabl is built for companies with business-critical applications, especially where quality is non-negotiable and auditability matters. In financial services, healthcare, and insurance, teams use mabl's tamper-evident evidence and proof that testing happened before deployment to support audit and compliance requirements. In travel and retail, teams use mabl to keep high-traffic customer journeys like booking and checkout working as release cadence increases.
OpenText Functional Testing provides automated testing with compatibility across technologies, browsers, and platforms. It targets APIs, GUIs, and applications like SAP and Oracle for efficient test automation, emphasizing usability and integration with tools such as Jenkins and ALM.
OpenText Functional Testing offers wide-ranging automation capabilities for functional and regression testing, API testing, and automation across web, desktop, and mainframe applications. It supports script recording and object identification, appealing to less technical users. Despite its advantages, it grapples with memory issues, stability concerns, and a challenging scripting environment. Its VBScript reliance limits flexibility, generating demand for enhanced language support and speed improvement. Users appreciate its role in continuous integration and deployment processes, managing test data efficiently, and reducing manual testing efforts.
What are the key features of OpenText Functional Testing?In industries like finance and healthcare, OpenText Functional Testing is leveraged for end-to-end automation, ensuring streamlined processes and accuracy in testing. Many companies utilize it for efficient test data management and integrating testing within continuous integration/deployment operations.
We monitor all Functional Testing Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.