Uft Tutorial 6 Homework

HPE 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] HPE Unified Functional Testing can be used for enterprise quality assurance.[3]

HPE 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]

HPE 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 was available from the HP Software Division until 2016, when whole division was sold to Micro Focus.[8] The integrated HPE 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.[9]

Description[edit]

HPE 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.[10] 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.[11]

Although HPE 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[edit]

HPE Unified Functional Testing manages exception handling using recovery scenarios; the goal is to continue running tests if an unexpected failure occurs.[12] Because HPE Unified Functional Testing 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]

HPE 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 HPE Unified Functional Testing. HPE 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.[13]

Automating custom and complex UI objects[edit]

HPE Unified Functional Testing may not recognize customized user interface objects and other complex objects. Users can define these types of objects as virtual objects. HPE Unified Functional Testing does not support virtual objects for analog recording or recording in low-level mode.[14]

Extensibility[edit]

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

User interface[edit]

HPE Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HPE Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HPE Unified Functional Testing 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, HPE 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.[17]

Expert view[edit]

In Expert View, HPE 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.[18]

Languages[edit]

HPE 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.[19]

Some Windows script (WScript,WSH,WMI) & VB.Net code can be used in a script in the expert view.

Drawbacks[edit]

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

HPE Unified Functional Testing cannot test with all browser types and versions. In particular it does not support Opera.[21][22]

The Test Execution engine is combined with the GUI Test Code development IDE, so there is no way to run the tests independent of HPE Unified Functional Testing, even though remote execution is still possible with HPE Unified Functional Testing running on a different machine.[23][24]

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

Supported Technologies[edit]

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

QTP/UFT browser support matrix[edit]

QTP/UFT vs IE support matrix[edit]

VersionsQTP v10QTP v11UFT v11.5UFT v12.02UFT v12.50UFT v12.51
IE v6 SP1YesYesYesN/ANoN/A
IE v7.00YesYesYesN/ANoN/A
IE v8.00Yes with support of QTP_00626YesYesYesYesYes
IE v9.00NoYes with support of QTPWEB_00078YesYesYesYes
IE v10.00NoNoYes with support of UFT_00044YesYesYes
IE v11.00NoNoNoYesYesYes
IE v11.0 EPMNoNoNoYes (Other than ActiveX, Silverlight, Flex)Yes (Other than ActiveX, Silverlight, Flex)Yes (Other than ActiveX, Silverlight, Flex)

Versions[edit]

  • 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][27]
  • 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 December 2014
  • 12.50: Released July 2015
  • 12.54: Released October 2016
  • 13.00: Never released
  • 14.00: Released January 27, 2017

License models[edit]

HPE Unified Functional Testing is available through single-seat licenses, as well as floating or concurrent licenses.[28] A trial version of the software is also available.[29]

HPE Unified Functional Testing Integration[edit]

HPE Unified Functional Testing and HP Quality Center work together for additional testing capabilities. Users can use HP Quality Center with HPE Unified Functional Testing assets, such as tests, shared object repositories, libraries, recovery scenarios and external data tables.[30]

HP Application Lifecycle Management Integration[edit]

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.[31] The software was tailored to work with a number of HP testing tools including HPE Unified Functional Testing to test for functional defects in the code.[32]

See also[edit]

References[edit]

  1. ^http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features/
  2. ^HP QuickTest Professional software data sheet
  3. ^"A complete guide to working on Quality Center with QTP". Learn QTP. Retrieved January 27, 2011. 
  4. ^ ab"HP Release QTP 10.0". Automatedtestinginstitute.com. March 7, 2009. Retrieved January 27, 2011. 
  5. ^"Mercury QuickTest Professional (QTP) Evaluation". Devbistro.com. November 8, 2006. Retrieved January 27, 2011. 
  6. ^"HP Press Release: HP Closes Landmark Mercury Acquisition; Companies Unite to Lead in Business Technology Optimization Software". Hp.com. Retrieved January 27, 2011. 
  7. ^http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing
  8. ^QA Financial, How the $8.8 billion HPE — Micro Focus merger will shake up testing, September 23, 2016
  9. ^http://www.computerworld.com/s/article/9233308/HP_simplifies_automated_software_testing_suite
  10. ^"Software Testing FAQ: GUI Test Drivers". Testingfaqs.org. Archived from the original on December 21, 2010. Retrieved January 27, 2011. 
  11. ^"QTP with Descriptive programming". Slideshare.net. Retrieved January 27, 2011. 
  12. ^"Mastering QuickTest Professional (QTP)". Qtpautomation.com. March 16, 2009. Retrieved January 27, 2011. 
  13. ^"Using Global and Action Data Sheets in QTP ~ Guide to QuickTest Professional 10". Qtp10.com. July 5, 2009. Retrieved January 27, 2011. 
  14. ^"QuickTest Professional User’s Guide.”
  15. ^"QTP 10 Tutorial". Scribd.com. July 8, 2010. Retrieved January 27, 2011. 
  16. ^Software Quality Engineering IT (August 4, 2010). "Tool info : HP Functional Testing software". Stickyminds.com. Retrieved January 27, 2011. 
  17. ^"Working with Keyword View in HP QTP - QTP Tutorial 6 ~ Guide to QuickTest Professional 10". Qtp10.com. July 4, 2009. Retrieved January 27, 2011. 
  18. ^http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf
  19. ^"Key Differences Between VB and VB Script". www.htmlgoodies.com. January 23, 2011. Retrieved January 27, 2011. 
  20. ^"HP Functional Testing software System Requirements", 'HP', accessed May 2, 2011.
  21. ^"HP QuickTest Professional 11.00 Product Availability Matrix", 'HP', October 1, 2010, accessed May 2, 2011.
  22. ^http://forums.mozillazine.org/viewtopic.php?f=7&t=277002
  23. ^http://social.msdn.microsoft.com/Forums/vstudio/en-US/c55675ba-e3ab-4296-8010-d14fa4fd74ca/migrating-from-qtp-to-microsoft-test-managermtm
  24. ^http://www.learnqtp.com/forums/Thread-Run-QTP-script-on-system-without-QTP-IDE
  25. ^Hammant, Paul. "I think it is time for QTP to die" accessed May 2, 2011.
  26. ^"Functional Testing software System Requirements - HP - BTO Software". HP. Retrieved January 27, 2011. 
  27. ^http://www.joecolantonio.com/2011/07/11/uft-hp%E2%80%99s-unified-functional-testing/
  28. ^"Download QTP 10.0 Evaluation ~ Guide to QuickTest Professional 10". Qtp10.com. April 17, 2009. Retrieved January 27, 2011. 
  29. ^HP QuickTest Professional software official web page
  30. ^"HP Quality Center 10.00 integration | HP Enterprise TV: Online Videos and Podcasts". H30423.www3.hp.com. Retrieved January 27, 2011. 
  31. ^http://www.rubric.co.za/tool-support/hp
  32. ^http://www.networkworld.com/news/2010/113010-hp-fuses-dev-management-and.html

External links[edit]

VBScript code in Expert View

The Keyword View provides an easy way to create, view, and modify tests in a graphical easy-to-use format.

About Working with the Keyword View in HP’s QTP:
The Keyword View enables you to create and view the steps of your test in a modular, table format. Each step is a row in the Keyword View that is comprised of individual, modifiable parts. You create and modify steps by selecting items and operations in the Keyword View and entering information as required. Each step is automatically documented as you complete it, enabling you to view a description of your test in understandable sentences. You can also use these descriptions as instructions for manual testing, if required.

You can use the Keyword View to add new steps to your test and to view and modify existing steps. When you add or modify a step, you select the test object or other step type you want for your step, select the method operation you want to perform, and define any necessary values for the selected operation or statement. Working in the Keyword View does not require any programming knowledge. The programming required to actually perform each test step is done automatically behind the scenes by QTP.

The Keyword View

The Keyword View enables you to create and view the steps of your test in a keyword-driven, modular, table format. The Keyword View is comprised of a table-like view, in which each step is a separate row in the table, and each column represents the different parts of the steps. The columns displayed vary according to your selection.

Actions are the highest level of the test hierarchy. They contain all the steps that are part of that action, and can include calls to other reusable actions. In the Keyword View, you can use the Action toolbar to view either the flow of all the top-level action calls in the test, or the content of a specific action. You can also display an action by double-clicking it in the Test Flow pane.

You can insert a new action, a call to an action, or a copy of an action, to your test.

Tip: You can copy and paste or drag and drop actions to move them to a different location within a test.

Each action is comprised of steps. Each step is inserted as a row in the Keyword View. For example, the Keyword View could contain the following rows:

These rows show the following three steps that are all performed on the Welcome: Mercury Tours page of the Mercury Tours sample Web site:

  • tutorial is entered in the userName edit box.
  • An encrypted string is entered in the password edit box.
  • The Sign-In image is clicked.
  • The Documentation column translates each of the steps into understandable sentences.

For every step in the Keyword View, QTP displays a corresponding line of script in the Expert View. If you select a specific row in the Keyword View and switch to the Expert View, the cursor is located in the corresponding line of the script.

You can use the Keyword View to add steps at any point in your test. After you add steps, you can modify or delete them using standard editing commands and drag-and-drop functionality. You can print the contents of the Keyword View to your Windows default printer (and even preview the contents prior to printing).

In the Keyword View, you can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist you in debugging your test.

The Keyword View can contain any of the following columns: Item, Operation, Value, Assignment, Comment, and Documentation. A brief description of each column is provided below.

Columns Description:

Item Column:

The item on which you want to perform the step (test object, utility object, function call, or statement). This column displays a hierarchical icon-based tree. The highest level of the tree are actions, and all steps are contained within the relevant branch of the tree. Steps performed within the same parent object are displayed under that same object. Function calls, utility objects, and statements are placed in the tree hierarchy at the same level as the item above them (as a sibling).

You can collapse or expand an item in the item tree to change the level of detail that the tree displays.

  • To collapse an item and its sub-items, click the arrow ( ) to the left of the item's icon, press the minus key (-) on your keyboard number pad, press the left arrow key on your keyboard, or right-click the item and select Collapse Sub Tree. The item tree hides all its sub-items and the collapse arrow changes to expand.
  • To collapse all the items in the tree, select View > Collapse All.
  • To expand an item one level or to its previously expanded state, select it and click the arrow (down arrow) to the left of the item icon, press the plus key (+) on your keyboard number pad, press the right arrow key on your keyboard, or right-click the item and select Expand Sub Tree. The tree displays the details for the item and all its first-level sub-items and the expand arrows change to collapse.
  • To expand an item and all its sub-items, select the item and press the asterisk (*) key on your keyboard number pad. The tree displays the details for the item and all its sub-items and the expand arrows change to collapse.
  • To expand all the items in the tree, select View > Expand All.

Note: When you use the +, -, and * keys to expand and collapse the Item tree, make sure that the entire row is selected (by clicking to the left of the item's icon) and that a specific column is not selected, before pressing the required key. Otherwise, the keys will not work.

    Operation Column:

    The operation to be performed on the item. This column contains a list of all available operations (methods, functions, or properties) that can be performed on the item selected in the Item column, for example, Click and Select. The default operation for the item selected in the Item column is displayed by default.

Value Column:

The argument values for the selected operation, or the content of the statement. The Value cell is partitioned according to the number of arguments of the selected operation.

If an argument has a predefined list of values, QTP provides a drop-down list of possible values. If a list of values is provided, you cannot manually type a value in this box.

Assignment Column:

The assignment of a value to or from a variable. For example, Store in cCols would store the return value of the current step in a variable called cCols, which you could then use later in the test.

You can select either Store in or Get from, depending on whether you want to retrieve the value from a variable or store the value in a variable. A Store in X value in the Assignment column is equivalent to an X = <step> line in the Expert View. A Get From X value in the Assignment column is equivalent to a <step> = X line in the Expert View.

Comment Column:

A free text edit box for any information you want to add regarding the step. These are also displayed as inline comments in the Expert View.

Note: You can also enter a comment on a new line below the currently selected step by choosing Insert > Comment.

Note: If you do not see one or more of the columns in the Keyword View, you can use the Keyword View Options dialog box to display them.

Tips for Working with the Keyword View:

  • You can use the left and right arrow keys to move the focus one cell to the left or right, with the following exceptions:
    • In the Item column, the left and right arrow keys collapse or expand the item (if possible). If not possible, the arrow keys behave as in any other column.
    • When a cell is in edit mode, for example, when modifying a value or comment, the left and right arrow keys move within the edited cell.
  • When a Value cell is selected, press Ctrl+F11 to open the Value Configuration Options dialog box.
  • When the entire step is selected (by clicking to its left), use the + key (expands a specific branch), - key(collapses a specific branch), and * key (expands all branches) to expand and collapse the Item tree.
  • When a row is selected (not a specific cell), you can type a letter to jump to the next row that starts with that letter.
Download Step by Step Tutorial to work in Keyword View:

1. Adding a Standard Steps to QTP Test Scripts in Keyword View
2. Adding a Programming Steps to QTP Test Scripts in Keyword View

Go Back to –>QTP Tutorial Learn QTP – Design QTP Scripts

0 thoughts on “Uft Tutorial 6 Homework”

    -->

Leave a Comment

Your email address will not be published. Required fields are marked *