What it does
UFT One is an OpenText functional test-automation product documented for GUI tests and API testing. A solution groups tests and libraries, while actions define a GUI test's sequence and technology-specific add-ins provide support for the application under test. The documented workflow can run tests from UFT One, ALM, runtime and batch tools, and produces a report when execution ends. Teams must provide their target application, test data and compatible add-ins.
Structure a GUI test around a solution
The UFT One tutorial uses a sample flight application to demonstrate a first GUI test. It asks the tester to create a solution, add a GUI test and its actions, and select the technology add-in needed by the sample. The guide notes that irrelevant add-ins can be cleared and that a missing add-in may need to be added through installation maintenance. For an application your team owns, the same approach means checking the support matrix before building a test around a particular framework or control.
Execution is not limited to pressing Run in the editor. OpenText's test-running guide describes GUI and API tests, result reports, and ways to launch tests through UFT One, ALM, UFT Runtime Engine, Test Batch Runner, Silent Test Runner or ParallelRunner. That makes UFT One relevant to established enterprise QA environments with a chosen execution host and test integration plan.
The product overview and trial page could not be retrieved directly in this research session, so no pricing or trial claim is made. The accessible tutorial uses UFT One branding for versions 23.4 through 24.2, while the newer 26.1 through 26.3 support matrix is titled OpenText Functional Testing. Confirm the current package and licensing relationship before selecting a new deployment.
Strengths
- The documentation covers both GUI test components and API testing, with execution reports after a run.
- Tests can be launched through desktop, ALM, runtime, batch, silent or parallel execution tools.
- Technology add-ins let a test environment load support suited to the application being tested.
Watch out for
- GUI automation depends on having the relevant technology add-in installed and selected for the application under test.
Best for
- Enterprise QA groups automating Windows GUI workflows with supported technology add-ins.
- Teams combining GUI and API test cases in established UFT or ALM execution environments.
- Organizations that need batch or parallel test execution and a report of each run.
Sources
- Support Matrix (Oct 25, 2026)
- Create your test structure (Oct 25, 2026)
- Run tests and components (Oct 25, 2026)