OpenText UFT One provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable UFT to act as an
Integrated Development Environment (IDE) for the test, and UFT includes many standard IDE features, such as
breakpoints to pause a test at predetermined places.
Keyword view Keyword View lets users create and view the steps of a test in a modular, table format. Each row in the table represents a step that can be modified. The Keyword View can also contain any of the following columns: Item, Operation, Value, Assignment, Comment, and Documentation. For every step in the Keyword View, UFT displays a corresponding line of script based on the row and column value. Users can add, delete or modify steps at any point. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.
Expert view In Expert View, UFT lets users display and edit a test's source code using
VBScript. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.
Languages OpenText UFT One uses
VBScript as its scripting language. VBScript supports classes but not polymorphism and inheritance. Compared with
Visual Basic for Applications (VBA), VBScript lacks the ability to use some Visual Basic keywords, does not come with an integrated debugger, lacks an event handler, and does not have a forms editor. HP added a debugger, but the functionality is more limited when compared with testing tools that integrate a full-featured IDE, such as those provided with VBA, Java, or VB.NET. Some Windows script (WScript, WSH, WMI) and VB.Net code can be used in a script in the expert view.
Drawbacks OpenText UFT One runs primarily in Windows environments. It relies on largely obsolete Windows-only technologies such as ActiveX and VBScript which is not an object-oriented language. OpenText UFT One cannot test with all browser types and versions. In particular it does not support Opera. The Test Execution engine is combined with the GUI Test Code development IDE, so there is no way to run the tests independent of UFT, even though remote execution is still possible with HPE Unified Functional Testing running on a different machine. High licensing costs often mean that the tool is not widely used in an organization, but instead is limited to a smaller testing team. This encourages a
siloed approach to QA/testing where testing is performed as a separate phase rather than a collaborative approach where QA/testers work closely with the business and development teams (as is advocated by newer agile approaches to software development). ==Integration==