Jump to content

UFT One

From Wikipedia, the free encyclopedia

OpenText UFT One
Developer(s)OpenText
Stable release
24.2 / April 17, 2024; 6 months ago (2024-04-17)
Operating systemMicrosoft Windows
TypeTest automation tools
LicenseProprietary
Websitewww.opentext.com/products/uft-one

OpenText™ UFT One, an AI-powered functional testing tool, accelerates test automation across desktop, web, mobile, mainframe, composite, and packaged enterprise-grade applications.

It was formerly known as Micro Focus Unified Functional Testing and QuickTest Professional (QTP).

UFT One supports keyword and scripting interfaces and features a graphical user interface.[1] It uses the Visual Basic Scripting Edition (VBScript) scripting language to specify a test procedure, and to manipulate the objects and controls of the application under test.[1] UFT allows developers to test all three layers of a program's operations from a single console: the interface, the service layer and the database layer.[2]

UFT was originally written by Mercury Interactive and called QuickTest Professional.[3] Mercury Interactive was subsequently acquired by Hewlett-Packard (HP) in 2006.[4] UFT 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,[5] which was available from the HP Software Division until 2016, when the division was ultimately sold to Micro Focus.[6]

Micro Focus was acquired by OpenText in 2023.

Description

[edit]

OpenText UFT One is automated testing software designed for testing various software applications and environments. It performs functional and regression testing through a user interface such as a native GUI or web interface.[7] It works by identifying the objects in the application user interface or a web page and performing desired operations (such as mouse clicks or keyboard events); it can also capture object properties like name or handler ID. HPE Unified Functional Testing uses a VBScript scripting language to specify the test procedure and to manipulate the objects and controls of the application under test. To perform more sophisticated actions, users may need to manipulate the underlying VBScript.[8]

Although UFT is usually used for "UI based" test case automation, it also can automate some "non-UI" based test cases, such as file system operations, database testing, Web services testing and API testing.[citation needed]

Exception handling

[edit]

OpenText UFT One manages exception handling using recovery scenarios; the goal is to continue running tests if an unexpected failure occurs.[9] Because UFT hooks into the memory space of the applications being tested, some exceptions may cause HPE Unified Functional Testing to terminate and be unrecoverable.

Data-driven testing

[edit]

OpenText UFT One supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. Data-driven testing is implemented as a Microsoft Excel workbook that can be accessed from UFT. UFT has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.[10]

Automating custom and complex UI objects

[edit]

OpenText UFT One may not recognize customized user interface objects and other complex objects. Users can define these types of objects as virtual objects or as insight objects (bitmap comparison). UFT does not support virtual objects for analog recording or recording in low-level mode.[11]

Extensibility

[edit]

OpenText UFT One can be extended with separate add-ins for a number of development environments that are not supported out-of-the-box. UFT add-ins include support for Web, .NET, Java, and Delphi.[12] HP QuickTest Professional and the HP QuickTest Professional add-ins are packaged together in HP Functional Testing software.[13]

User interface

[edit]

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

[edit]

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.[14]

Expert view

[edit]
VBScript code in 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.[15]

Languages

[edit]

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.[16]

Some Windows script (WScript, WSH, WMI) and VB.Net code can be used in a script in the expert view.[citation needed]

Drawbacks

[edit]

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.[17]

OpenText UFT One cannot test with all browser types and versions. In particular it does not support Opera.[18][19]

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.[20][21]

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).[22]

Integration

[edit]

OpenText UFT One and Quality Center work together for additional testing capabilities. Users can use HP Quality Center with UFT assets, such as tests, shared object repositories, libraries, recovery scenarios and external data tables.[23]

HP Application Lifecycle Management (ALM) enables IT staff in multiple roles to manage activities associated with their core application lifecycle, from requirements through development, testing, defect management and readiness for delivery.[24] The software was tailored to work with a number of testing tools, including UFT, to test for functional defects in the code.[25]

See also

[edit]

References

[edit]
  1. ^ a b "HP Release QTP 10.0". Automated Testing Institute. March 7, 2009. Retrieved January 27, 2011.
  2. ^ Jackson, Joab (November 6, 2012). "HP simplifies automated software testing suite". Retrieved August 10, 2018.
  3. ^ "Mercury QuickTest Professional (QTP) Evaluation". Devbistro.com. November 8, 2006. Retrieved January 27, 2011.
  4. ^ "HP Press Release: HP Closes Landmark Mercury Acquisition; Companies Unite to Lead in Business Technology Optimization Software". HP. Retrieved January 27, 2011.
  5. ^ "HP-UFT 11.50 (Unified Functional Testing)". selftechy.com. Retrieved August 10, 2018.
  6. ^ QA Financial, How the $8.8 billion HPE — Micro Focus merger will shake up testing, September 23, 2016.
  7. ^ "Software Testing FAQ: GUI Test Drivers". Testingfaqs.org. Archived from the original on December 21, 2010. Retrieved January 27, 2011.
  8. ^ "QTP with Descriptive programming". SlideShare. March 4, 2008. Retrieved January 27, 2011.
  9. ^ "Mastering QuickTest Professional (QTP)". Qtpautomation.com. March 16, 2009. Retrieved January 27, 2011.
  10. ^ "Using Global and Action Data Sheets in QTP ~ Guide to QuickTest Professional 10". Qtp10.com. July 5, 2009. Retrieved January 27, 2011.
  11. ^ "QuickTest Professional User's Guide.”
  12. ^ "QTP 10 Tutorial". Scribd.com. July 8, 2010. Retrieved January 27, 2011.
  13. ^ Software Quality Engineering IT (August 4, 2010). "Tool info : HP Functional Testing software". StickyMinds. Retrieved January 27, 2011.
  14. ^ "Working with Keyword View in HP QTP – QTP Tutorial 6 ~ Guide to QuickTest Professional 10". Qtp10.com. July 4, 2009. Retrieved January 27, 2011.
  15. ^ "Mercury Interactive QuickTest Professional" (PDF). Archived from the original (PDF) on April 19, 2009. Retrieved April 6, 2010.
  16. ^ "Key Differences Between VB and VB Script". HTMLGoodies. January 23, 2011. Retrieved January 27, 2011.
  17. ^ "HP Functional Testing software System Requirements"[permanent dead link]. HP. Retrieved May 2, 2011.
  18. ^ "HP QuickTest Professional 11.00 Product Availability Matrix". HP. October 1, 2010. Retrieved May 2, 2011.
  19. ^ "Firefox & VBScript". mozillaZine Forums. Retrieved August 10, 2018.
  20. ^ "Migrating from QTP to Microsoft Test Manager(MTM)".
  21. ^ "Run QTP script on system without QTP IDE". www.learnqtp.com. Retrieved August 10, 2018.
  22. ^ Hammant, Paul. "I think it is time for QTP to die". Paul Hammant's blog. Retrieved May 2, 2011.
  23. ^ "HP Quality Center 10.00 integration | HP Enterprise TV: Online Videos and Podcasts". H30423.www3.hp.com. Retrieved January 27, 2011.
  24. ^ "HP – HP Software ALM – Application Lifecycle Management". Rubric. Archived from the original on December 14, 2013. Retrieved December 11, 2013.
  25. ^ "HP fuses dev management and testing tools". Archived from the original on December 14, 2013. Retrieved December 11, 2013.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=UFT_One&oldid=1234597949"