UFT One: Difference between revisions

Browse history interactively ← Previous editContent deleted Content addedVisual WikitextInline

Revision as of 12:52, 12 October 2009 edit117.241.124.98 (talk) →External links ← Previous edit		Latest revision as of 05:25, 15 July 2024 edit undoLiuyuns (talk \| contribs)7 editsNo edit summary
(566 intermediate revisions by more than 100 users not shown)
Line 1:		Line 1:
			{{Short description\|Software testing automation tool}}
	{{Primarysources\|date=August 2007}}
	{{~~Nofootnotes\|article~~\|date=~~August~~ ~~2008~~}}		{{Use mdy dates\|date=January 2017}}
	{{~~Advert~~\|date=~~August~~ ~~2008~~}}		{{More citations needed\|date=December 2015}}
			{{Manual\|date=March 2023}}
	{{ infobox software
			{{infobox software
	\| name = HP QuickTest Professional
			\| name = OpenText UFT One
	\| developer = ]/]
			\| logo = UFT LOGO.png
	\| latest release version = 10.0
			\| logo_alt = UFT Icon
	\| latest release date =
			\| logo_size = 32px
	\| operating system = ]
			\| screenshot = File:UFT ONE 24.2.png
	\| genre = ]
			\| caption = Start Page
	\| license = ]
			\| developer = ]
	\| website =
			\| latest release version = 24.2
	\| status = Active
			\| latest release date = {{Start date and age\|2024\|04\|17}}
			\| operating system = ]
			\| genre = ]
			\| license = ]
			\| website = {{URL\|https://www.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.
	'''Quick Test Professional''' (QTP) is an automated functional Graphical User Interface (GUI) testing tool created by the ] subsidiary ] that allows the automation of user actions on a web or client based and desktop computer application. It is primarily used for ] ] ]. QTP uses a scripting language built on top of ] to specify the test procedure, and to manipulate the objects and controls of the application under test.

			It was formerly known as '''Micro Focus Unified Functional Testing''' and '''QuickTest Professional''' ('''QTP''').
	As part of a functional test suite, it works together with ] and ] and supports enterprise Quality Assurance.

			UFT One supports keyword and scripting interfaces and features a graphical user interface.<ref name="automatedtestinginstitute1">{{cite web\|url=http://www.automatedtestinginstitute.com/home/index.php?view=article&id=%201215&option=com_content&Itemid=1000 \|title=HP Release QTP 10.0 \|website=Automated Testing Institute \|date=March 7, 2009 \|access-date=January 27, 2011}}</ref> It uses the Visual Basic Scripting Edition (]) scripting language to specify a test procedure, and to manipulate the objects and controls of the application under test.<ref name="automatedtestinginstitute1"/> 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.<ref>{{cite web\|url=http://www.computerworld.com/s/article/9233308/HP_simplifies_automated_software_testing_suite\|title=HP simplifies automated software testing suite\|first=Joab\|last=Jackson\|date=November 6, 2012 \|access-date=August 10, 2018}}</ref>
	==Overview==
	QTP is UI automation software designed for testing Web-based and Windows based applications running on Microsoft Windows. Like other test automation tools, it works by identifying the objects in the application UI or a web page and performing the desired operations on them (like mouse clicks or keyboard events); it can also be used to capture object properties like name or handler ID etc. To perform these actions, QTP uses a scripting language built on top of VBScript to specify the test procedure, and to manipulate the objects and controls of the application under test. To perform sophisticated actions, users may need to manipulate the underlying VBScript.

			UFT was originally written by ] and called QuickTest Professional.<ref>{{cite web\|url=http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation \|title=Mercury QuickTest Professional (QTP) Evaluation \|website=Devbistro.com \|date=November 8, 2006 \|access-date=January 27, 2011}}</ref> Mercury Interactive was subsequently acquired by ] (HP) in 2006.<ref>{{cite web\|url=http://www.hp.com/hpinfo/newsroom/press/2006/061107xa.html?jumpid=reg_R1002_USEN \|title=HP Press Release: HP Closes Landmark Mercury Acquisition; Companies Unite to Lead in Business Technology Optimization Software \|website=HP \|access-date=January 27, 2011}}</ref> UFT 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref>{{cite web\|url=http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing\|title=HP-UFT 11.50 (Unified Functional Testing)\|website=selftechy.com\|access-date=August 10, 2018}}</ref> which was available from the ] until 2016, when the division was ultimately sold to ].<ref>QA Financial, , September 23, 2016.</ref>
	Though QTP is usually used for "UI Based" ] Automation, it can automate some "Non-UI" based Test Cases. (e.g. API (Certification testing), Database Testing, etc.)


			Micro Focus was acquired by ] in 2023.

			==Description==
			OpenText UFT One is automated testing software designed for testing various software applications and environments. It performs functional and ] through a user interface such as a native GUI or web interface.<ref>{{cite web \|url=http://www.testingfaqs.org/t-gui.html \|title=Software Testing FAQ: GUI Test Drivers \|website=Testingfaqs.org \|access-date=January 27, 2011 \|url-status=dead \|archive-url=https://web.archive.org/web/20101221192636/http://testingfaqs.org/t-gui.html \|archive-date=December 21, 2010}}</ref> 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 ].<ref>{{cite web\|url=http://www.slideshare.net/kuldeepse/qtp-with-descriptive-programming-293056 \|title=QTP with Descriptive programming \|date=March 4, 2008 \|website=SlideShare \|access-date=January 27, 2011}}</ref>

			Although UFT is usually used for "UI based" ] 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\|date=March 2023}}

	===~~License~~ ~~models~~===		===Exception handling===
			OpenText UFT One manages ] using recovery scenarios; the goal is to continue running tests if an unexpected failure occurs.<ref>{{cite web\|url=http://www.qtpautomation.com/ \|title=Mastering QuickTest Professional (QTP) \|website=Qtpautomation.com \|date=March 16, 2009 \|access-date=January 27, 2011}}</ref> 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.
	QTP comes with a 14-day demo license, and supports a node-locked seat license, as well as ] or concurrent licenses.

	===~~Record~~ ~~and playback~~===		===Data-driven testing===
			OpenText UFT One supports ]. For example, data can be output to a data table for reuse elsewhere. Data-driven testing is implemented as a ] 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.<ref>{{cite web\|url=http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html \|title=Using Global and Action Data Sheets in QTP ~ Guide to QuickTest Professional 10 \|website=Qtp10.com \|date=July 5, 2009 \|access-date=January 27, 2011}}</ref>
	Initial development of automated tests with QTP is usually done by record-and-playback. A user's actions are recorded and transposed into comprehensible actions using VBScript. Once recorded, the scripts are editable in either ] or ].

	To execute, users select the playback button, which re-executes the commands against the application under test. In real world usage, simply recording and playing-back actions is generally not valuable, as it simply repeats a test already executed and may no longer be valid (because the record now exists in the system, for example).

			===Automating custom and complex UI objects===
	This record/playback behavior is not unique to QTP, but is shared by comparable automated functional testing tools, such as IBM Rational Functional Tester, MicroFocus ], and Borland ]. There are a few other tools which supports "capture & replay" options (with a difference of a supported technologies) like free ].
			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.<ref></ref>

	===~~Verification~~===		===Extensibility===
			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 ].<ref name="scribd1">{{cite web\|url=https://www.scribd.com/doc/26190751/QTP-10-Tutorial \|title=QTP 10 Tutorial \|publisher=Scribd.com \|date=July 8, 2010 \|access-date=January 27, 2011}}</ref> HP QuickTest Professional and the HP QuickTest Professional add-ins are packaged together in HP Functional Testing software.<ref>{{cite web\|author=Software Quality Engineering IT \|url=http://www.stickyminds.com/sitewide.asp?ObjectId=3323&Function=edetail&ObjectType=TOOL \|title=Tool info : HP Functional Testing software \|website=StickyMinds \|date=August 4, 2010 \|access-date=January 27, 2011}}</ref>
	Checkpoints are a feature used for verifying that the application under test functions as expected. One can add a checkpoint to check if a particular object, text or a bitmap is present in the automation run. Checkpoints are used to verify that during the course of test execution, the actual application behavior or state is consistent with the expected application behavior or state.

			==User interface==
	There are 10 types of checkpoints available in QTP, enabling users to verify various aspects of an application under test, such as: the properties of an object, data within a table, records within a database, a bitmap image, or the text on an application screen. Users can also create user-defined checkpoints.
			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 ] (IDE) for the test, and UFT includes many standard IDE features, such as ]s to pause a test at predetermined places.

	===~~Exception~~ ~~handling~~===		===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.
	Recovery is the name for ] in QTP, with the goal of enabling the tests to continue to run if an unexpected failure occurs. For instance if an application crash occurs and a message dialog appears, QTP can be instructed to attempt to restart the application and continue with the rest of the test cases from there. Because QTP hooks into the memory space of the applications being tested, some exceptions may cause QTP to terminate, and may be unrecoverable.

			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.<ref>{{cite web\|url=http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html \|title=Working with Keyword View in HP QTP – QTP Tutorial 6 ~ Guide to QuickTest Professional 10 \|website=Qtp10.com \|date=July 4, 2009 \|access-date=January 27, 2011}}</ref>
	===Data-driven testing===
	QTP has features to enable users to perform ]. For example, data can be output to a data table for reuse elsewhere. Data-driven testing is implemented as a ] workbook that can be accessed from within QTP. There are two types of Data Tables available in QTP: the Global data sheet and the local data sheets. The test steps read data from these data tables in order to (for example) drive variable data into the application under test, and verify the expected result.

			===Expert view===
	===Automating custom and complex UI objects===
			]
	Customized user interface objects and other complex objects may not be recognized properly by QTP. QTP offers a Virtual Object concept to enable users to add some degree of support for these objects. Assuming that the required information can be extracted from the object, this allows the users to successfully record and playback against that object. In practice, this is not always possible.
			In Expert View, UFT lets users display and edit a test's source code using ]. 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.<ref>{{Cite web \|url=http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf \|title=Mercury Interactive QuickTest Professional \|access-date=April 6, 2010 \|archive-url=https://web.archive.org/web/20090419201544/http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf \|archive-date=April 19, 2009 \|url-status=dead}}</ref>

	===~~Add-in Extensibility~~===		===Languages===
			OpenText UFT One uses ] as its scripting language. VBScript supports classes but not polymorphism and inheritance. Compared with ] (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.<ref>{{cite web\|url=http://www.htmlgoodies.com/beyond/asp/vbs-ref/article.php/3458611 \|title=Key Differences Between VB and VB Script \|website=HTMLGoodies \|date=January 23, 2011 \|access-date=January 27, 2011}}</ref>
	QuickTest add-in extensibility, available for some environments, enables you to extend the relevant QuickTest add-in to support third-party and custom controls that are not supported out-of-the-box.
	QuickTest add-in extensibility is currently supported for the Web, .NET, Java, and Delphi add-ins

			Some Windows script (WScript, WSH, WMI) and VB.Net code can be used in a script in the expert view.{{Citation needed\|date=March 2023}}
	===Results===
	QTP generates the result file for the test cases at the end of test in the form of an XML tree. The result file provides detail regarding PASS and FAILS counts, error messages, and may provide supporting information that allows users to determine the underlying cause of a failure. Frequently, however, users may need to re-execute the test case and observe the failure directly

			===Drawbacks===
	===Quality Center Integration===
			{{Criticism section\|date=March 2023}}
	Using QuickTest Professional together with Quality Center provides you an intuitive and efficient system for managing your tests and their resources (actions, function libraries, object repositories, recovery scenarios, data table files, and environments variables). You can manage asset dependencies and versions, schedule and run tests, collect, analyze, and share results report defects, and link your tests and defects to project requirements.
			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.<ref>{{Dead link\|date=April 2020 \|bot=InternetArchiveBot \|fix-attempted=yes}}. ''HP''. Retrieved May 2, 2011.</ref>

			OpenText UFT One cannot test with all browser types and versions. In particular it does not support Opera.<ref>. ''HP''. October 1, 2010. Retrieved May 2, 2011.</ref><ref>{{cite web\|url=http://forums.mozillazine.org/viewtopic.php?f=7&t=277002\|title=Firefox & VBScript \|website=mozillaZine Forums \|access-date=August 10, 2018}}</ref>
	==User interface==
	QuickTest provides two main views of a script: Keyword View and Expert View. They are selected from tabs at the bottom of the QuickTest Professional window.

	===Keyword view===
	Keyword View is QTP's default test procedure interface. It displays the automation steps of a test procedure as a descriptive tree of actions and functions. The tree contains columns listing the action or function name, parameters, and comments. This mode is useful for the beginners. This view allows the user to select the objects either from the application or from the Object Repository and the user can select the methods to be performed on those objects. The script is automatically generated. Users can also set checkpoints from the keyword view. Users without technical knowledge may be able to understand the Keyword View, but more experienced users and users needing to perform more complicated actions may need to switch to Expert View.

			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.<ref>{{Cite web\|url=http://social.msdn.microsoft.com/Forums/vstudio/en-US/c55675ba-e3ab-4296-8010-d14fa4fd74ca/migrating-from-qtp-to-microsoft-test-managermtm\|title=Migrating from QTP to Microsoft Test Manager(MTM)}}</ref><ref>{{cite web\|url=http://www.learnqtp.com/forums/Thread-Run-QTP-script-on-system-without-QTP-IDE\|title=Run QTP script on system without QTP IDE\|website=www.learnqtp.com\|access-date=August 10, 2018}}</ref>
	===Expert view===
	In Expert View, QTP allows display and editing of the test's source code using VBScript. All test actions can be edited here except for the root Global action. Expert View acts as an ] for the test. It includes many standard IDE features, such as breakpoints.

			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 ] 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).<ref>Hammant, Paul. . ''Paul Hammant's blog.'' Retrieved May 2, 2011.</ref>
	===Languages===
	QTP 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 has added some of these features to QTP, such as a debugger, but QTP's functionality is more limited in these areas compared with testing tools that integrate a full-featured IDE, such as those provided with VBA, Java, or VB.NET.

			==Integration==
	===Drawbacks===
			OpenText UFT One and Quality Center work together for additional testing capabilities. Users can use ] with UFT assets, such as tests, shared object repositories, libraries, recovery scenarios and external data tables.<ref>{{cite web\|url=http://h30423.www3.hp.com/?rf=sitemap&fr_story=399876c51bce0e1612eb0f1a3cd2c27ce70a26c3&jumpid=reg_R1002_USEN \|title=HP Quality Center 10.00 integration \| HP Enterprise TV: Online Videos and Podcasts \|website=H30423.www3.hp.com \|access-date=January 27, 2011}}</ref>
	QTP is not supported by non-Windows based applications. Neither can it be used by a plug-in in other environments. It fetches objects like ActiveX from the Windows environment which is not possible in any other OS. It also cannot be used via Remote Desktop Connection due to licensing issues.{{fact\|date=June 2009}}.

			] (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.<ref>{{Cite web \|url=http://www.rubric.co.za/tool-support/hp \|title=HP – HP Software ALM – Application Lifecycle Management \|website=Rubric \|access-date=December 11, 2013 \|archive-url=https://web.archive.org/web/20131214162347/http://www.rubric.co.za/tool-support/hp \|archive-date=December 14, 2013 \|url-status=dead}}</ref> The software was tailored to work with a number of testing tools, including UFT, to test for functional defects in the code.<ref>{{Cite web \|url=http://www.networkworld.com/news/2010/113010-hp-fuses-dev-management-and.html \|title=HP fuses dev management and testing tools \|access-date=December 11, 2013 \|archive-url=https://web.archive.org/web/20131214010956/http://www.networkworld.com/news/2010/113010-hp-fuses-dev-management-and.html \|archive-date=December 14, 2013 \|url-status=dead}}</ref>
	==Supported Technologies==
	* Web
	* Java
	* .Net
	* WPF
	* SAP
	* Oracle
	* Siebel
	* PeopleSoft
	* Delphi
	* Power Builder
	* Stingray
	* Terminal Emulator

	Full list of supported environemnts can be found

	==See also==		==See also==

	{{Portal\|Software Testing}}
	*]		*]
	*]
	*]		*]

	*]
			==References==
			{{reflist\|2}}

	==External links==		==External links==
			*
			*

			{{OpenText}}
	*
	*
	*
	*
	*
	*
	*
	*
	*
	]
	]

			]
	]
			]
			]

Latest revision as of 05:25, 15 July 2024

Software testing automation tool

This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "UFT One" – news · newspapers · books · scholar · JSTOR (December 2015) (Learn how and when to remove this message)

This article is written like a manual or guide. Please help rewrite this article and remove advice or instruction. (March 2023)

OpenText UFT One

Start Page
Developer(s)	OpenText

Stable release	24.2 / April 17, 2024; 8 months ago (2024-04-17)

Operating system	Microsoft Windows
Type	Test automation tools
License	Proprietary
Website	www.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. 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. 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.

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

Micro Focus was acquired by OpenText in 2023.

Description

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. 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.

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.

Exception handling

OpenText UFT One manages exception handling using recovery scenarios; the goal is to continue running tests if an unexpected failure occurs. 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

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.

Automating custom and complex UI objects

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.

Extensibility

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. HP QuickTest Professional and the HP QuickTest Professional add-ins are packaged together in HP Functional Testing software.

User interface

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

This article's "criticism" or "controversy" section may compromise the article's neutrality. Please help rewrite or integrate negative information to other sections through discussion on the talk page. (March 2023)

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

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.

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. The software was tailored to work with a number of testing tools, including UFT, to test for functional defects in the code.

References

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

External links

v t e OpenText
Founders	Tim Bray Gaston Gonnet Frank Tompa
Products	ArcSight Documentum GroupWise IDOL LoadRunner NetIQ eDirectory opentext.ai OpenText ALM OpenText Business Network OpenText Content Suite OpenText Data Protector OpenText Quality Center OpenText SiteScope OpenText Together Open Enterprise Server Silk Central Silk Performer Silk Test StarTeam UFT One Vertica Visibroker ZENworks
Acquisitions	Autonomy Corporation Carbonite, Inc. Webroot Cordys Covisint Guidance Software GXS Inc. Harbinger Corporation Hummingbird Ltd. Micro Focus The Attachmate Group Attachmate Borland Fortify Software HP IT Management Software Mercury Interactive NetIQ Novell Unix System Laboratories Peregrine Systems PlateSpin Opsware Serena Software Vignette Corporation

Categories: