HP QuickTest Professional
| HP UFT Icon. | |
| 300px
HP UFT 12.0 Start Page.
|
|
| Developer(s) | HP, HP Software Division |
|---|---|
| Stable release | 12.50 |
| Development status | Active |
| Operating system | Microsoft Windows |
| Type | Test Automation Tools |
| License | Proprietary |
| Website | HP Unified Functional Testing |
HP Unified Functional Testing (UFT) software, formerly known as HP QuickTest Professional (QTP),[1] provides functional and regression test automation for software applications and environments.[2] HP Unified Functional Testing can be used for enterprise quality assurance.[3]
HP Unified Functional Testing supports keyword and scripting interfaces and features a graphical user interface.[4] 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.[4]
HP Unified Functional Testing was originally written by Mercury Interactive and called QuickTest Professional.[5] Mercury Interactive was subsequently acquired by Hewlett Packard(HP) in 2006.[6] HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,[7] which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program's operations: the interface, the service layer and the database layer.[8]
Contents
Description
HP Unified Functional Testing 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.[9] 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. HP 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.[10]
Although HP Unified Functional Testing 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 or Web services testing.
Exception handling
HP Unified Functional Testing manages exception handling using recovery scenarios; the goal is to continue running tests if an unexpected failure occurs.[11] Because HP Unified Functional Testing hooks into the memory space of the applications being tested, some exceptions may cause HP Unified Functional Testing to terminate and be unrecoverable.
Data-driven testing
HP Unified Functional Testing 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 HP Unified Functional Testing. HP Unified Functional Testing 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.[12]
Automating custom and complex UI objects
HP Unified Functional Testing may not recognize customized user interface objects and other complex objects. Users can define these types of objects as virtual objects. HP Unified Functional Testing does not support virtual objects for analog recording or recording in low-level mode.[13]
Extensibility
HP Unified Functional Testing can be extended with separate add-ins for a number of development environments that are not supported out-of-the-box. HP Unified Functional Testing add-ins include support for Web, .NET, Java, and Delphi.[14] HP QuickTest Professional and the HP QuickTest Professional add-ins are packaged together in HP Functional Testing software.[15]
User interface
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing 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, HP Unified Functional Testing 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.[16]
Expert view
In Expert View, HP Unified Functional Testing 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.[17]
Languages
HP Unified Functional Testing 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.[18]
Some Windows script (WScript,WSH,WMI) & VB.Net code can be used in a script in the expert view.
Drawbacks
HP Unified Functional Testing 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.[19]
HP Unified Functional Testing cannot test with all browser types and versions. In particular it does not support Opera.[20] [21]
The Test Execution engine is combined with the GUI Test Code development IDE, so there is no way to run the tests independent of HP Unified Functional Testing, even though remote execution is still possible with HP Unified Functional Testing running on a different machine.[22][23]
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.)[24]
Supported Technologies
The supported technologies, depending on the version, are available for Web, Java (Core and Advanced), .Net, WPF, SAP, Oracle, Siebel, PeopleSoft, Delphi, Power Builder, Stingray 1, Terminal Emulator, Flex, Web Services, Windows Mobile, VisualAge Smalltalk, Silverlight and mainframe terminal emulators.[25]
QTP/UFT browser support matrix
QTP/UFT vs IE support matrix
Lua error in package.lua at line 80: module 'strict' not found.
| Versions | QTP v10 | QTP v11 | UFT v11.5 | UFT v12.02 | UFT v12.50 | UFT v12.51 |
|---|---|---|---|---|---|---|
| IE v6 SP1 | Yes | Yes | Yes | N/A | No | N/A |
| IE v7.00 | Yes | Yes | Yes | N/A | No | N/A |
| IE v8.00 | Yes with support of QTP_00626 | Yes | Yes | Yes | Yes | Yes |
| IE v9.00 | No | Yes with support of QTPWEB_00078 | Yes | Yes | Yes | Yes |
| IE v10.00 | No | No | Yes with support of UFT_00044 | Yes | Yes | Yes |
| IE v11.00 | No | No | No | Yes | Yes | Yes |
| IE v11.0 EPM | No | No | No | Yes (Other than ActiveX, Silverlight, Flex) | Yes (Other than ActiveX, Silverlight, Flex) | Yes (Other than ActiveX, Silverlight, Flex) |
Versions
- 5.5: First release: Released in 2001
- 6.0: Released in 2002
- 6.5: Released in 2003
- 7.0: Never released
- 8.0: Released in 2004
- 8.2: Released in 2005
- 9.0: Released in 2007
- 9.1: Released in 2007
- 9.2: Released in 2007
- 9.5: Released in 2008
- 10.0: Released in 2009
- 11.0: Released in 2010
- 11.5: Released in 2012 [renamed Unified Functional Testing][26]
- 11.52: Released in June 2013
- 11.53: Released in November 2013
- 12.0: Released March 2014
- 12.01: Released July 2014
- 12.02: Released March 2015
- 12.50: Released July 2015
License models
HP Unified Functional Testing is available through single-seat licenses, as well as floating or concurrent licenses.[27] A trial version of the software is also available.[28]
HP Unified Functional Testing Integration
HP Unified Functional Testing and HP Quality Center work together for additional testing capabilities. Users can use HP Quality Center with HP Unified Functional Testing assets, such as tests, shared object repositories, libraries, recovery scenarios and external data tables.[29]
HP Application Lifecycle Management Integration
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.[30] The software was tailored to work with a number of HP testing tools including HP Unified Functional Testing to test for functional defects in the code.[31]
See also
References
- ↑ http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features/
- ↑ HP QuickTest Professional software data sheet
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing
- ↑ http://www.computerworld.com/s/article/9233308/HP_simplifies_automated_software_testing_suite
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ "QuickTest Professional User’s Guide.”
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ "HP Functional Testing software System Requirements", 'HP', accessed May 2, 2011.
- ↑ "HP QuickTest Professional 11.00 Product Availability Matrix", 'HP', Oct 1 2010, accessed May 2, 2011.
- ↑ http://forums.mozillazine.org/viewtopic.php?f=7&t=277002
- ↑ http://social.msdn.microsoft.com/Forums/vstudio/en-US/c55675ba-e3ab-4296-8010-d14fa4fd74ca/migrating-from-qtp-to-microsoft-test-managermtm
- ↑ http://www.learnqtp.com/forums/Thread-Run-QTP-script-on-system-without-QTP-IDE
- ↑ Hammant, Paul. "I think it is time for QTP to die" accessed May 2, 2011.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ http://www.joecolantonio.com/2011/07/11/uft-hp%E2%80%99s-unified-functional-testing/
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ HP QuickTest Professional software official web page
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ http://www.rubric.co.za/tool-support/hp
- ↑ http://www.networkworld.com/news/2010/113010-hp-fuses-dev-management-and.html
