Ghid de Testare
Ghid de Testare
User Guide
Legal Notices
Warranty
The only warranties for HP products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable
for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Copyright Notice
© Copyright 1992 - 2015 Hewlett-Packard Development Company, L.P.
Trademark Notices
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Google™ and Google Maps™ are trademarks of Google Inc
Intel® and Pentium® are trademarks of Intel Corporation in the U.S. and other countries.
Microsoft®, Windows®, Windows® XP, and Windows Vista ® are U.S. registered trademarks of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Documentation Updates
The title page of this document contains the following identifying information:
l Software Version number, which indicates the software version.
l Document Release Date, which changes each time the document is updated.
l Software Release Date, which indicates the release date of this version of the software.
To check for recent updates or to verify that you are using the most recent edition of a document, go to:
https://softwaresupport.hp.com.
This site requires that you register for an HP Passport and sign in. To register for an HP Passport ID, go to
https://softwaresupport.hp.com and click Register.
Support
Visit the HP Software Support Online web site at: https://softwaresupport.hp.com
This web site provides contact information and details about the products, services, and support that HP Software
offers.
HP Software online support provides customer self-solve capabilities. It provides a fast and efficient way to access
interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by
using the support web site to:
l Search for knowledge documents of interest
l Submit and track support cases and enhancement requests
l Download software patches
l Manage support contracts
l Look up HP support contacts
l Review information about available services
l Enter into discussions with other software customers
l Research and register for software training
Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support
contract. To register for an HP Passport ID, go to: https://softwaresupport.hp.com and click Register.
To find more information about access levels, go to: https://softwaresupport.hp.com/web/softwaresupport/access-
levels.
Contents
Welcome to the Run Results Viewer User Guide 6
Additional Online Resources 6
It is recommended to have some prior knowledge of UFT and its testing capabilities so you can fully
evaluate the test results.
Resource Description
HP Software The HP Software Support Web site (www.hp.com/go/hpsoftwaresupport). To access, choose Help > HP
Support Online Software Support.
Note: Most of the support areas require that you register as an HP Passport user and sign in. Many
also require a support contract. To register for an HP Passport user ID, go to:
http://h20229.www2.hp.com/passport-registration.html
What's New The UFT What's New Help, describing the new features and enhancements in this version of UFT.
Product Movies The UFT HPLN (HP Live Networks) page (https://hpln.hp.com/page/uft-120-videos) with a list of all
product movies.
Resource Description
HP Software The HP Software Web site (www.hp.com/go/software). This site provides you with the most up-to-date
Web site information on HP Software products. This includes new software releases, seminars and trade shows,
customer support, and more.
• Concepts 10
• Run Results Viewer Overview 10
• Run Results XML File 11
• Run Results File Location 13
• Custom Fields (UFT API Testing Only) 14
• Tasks 16
• How to Install the Run Results Viewer as a Standalone Application 16
• How to Open Run Results 16
• How to Navigate the Run Results Tree 17
• How to Customize the Run Results Viewer 19
• How to Jump to a Step in a GUI Test (UFT GUI Tests Only) 20
• How to Manually Submit Defects to ALM 20
• How to Automatically Submit Defects to an ALM Project (UFT GUI Tests Only) 22
• How to Export Run Results 23
• How to Play a Screen Recorder Movie in the HP Micro Player (UFT GUI Testing Only) 24
• How to Delete Run Results 25
• Reference 26
• Run Results Viewer User Interface 26
• Run Results Viewer Commands 29
• Run Results Viewer Panes 32
• Run Results Tree Pane and Search Box 32
• Result Details Pane (Run Results Viewer) 37
• Captured Data Pane (Run Results Viewer) 40
• Captured Data Pane Contents for UFT API Steps 42
• Test Flow Pane (Run Results Viewer) (UFT API Tests Only) 47
• Data Pane (Run Results Viewer) 49
• Log Tracking Pane (Run Results Viewer) (UFT GUI Tests Only) 50
• Screen Recorder Pane (Run Results Viewer) (UFT GUI Testing Only) 52
• System Monitor Pane (Run Results Viewer) (UFT GUI Testing Only) 54
In addition, you can view the run results in HTML format directly in your browser or in UFT. To select the
format in which you want to view the run results, open the Run Sessions pane in the Options dialog box
(Tools > Options > General tab > Run Sessions node).
By default, the Run Results Viewer opens automatically at the end of a run session. If you want to
change this behavior, in UFT, clear the View results when run session ends check box in the Run
Sessions pane of the Options dialog box.
The Run Results Viewer contains a description of the steps performed during the run session.
l For a GUI component, or for a GUI test that does not contain Data Pane parameters, the Run Results
Viewer shows a single test iteration.
l For tests, if the test contains Data Pane parameters, and the test settings are configured to run
multiple iterations, the Run Results Viewer displays details for each iteration of the test run. The
results are grouped by the actions in the test.
l For an API test, the individual steps and checkpoints included in the test. If a test is set to run
multiple iterations, each iteration is displayed.
You set the test to run for one or all iterations in the Run pane of the Settings dialog box. For details,
see the section describing the Run pane in the HP Unified Functional Testing User Guide.
Note: To view the partial results in the Run Results Viewer, you need to open the results file from
another computer.
You can also install the Run Results Viewer as a standalone application. This enables you to share the
results of your tests with business analysts and developers who do not have UFT installed on their
computers. For details, see "How to Install the Run Results Viewer as a Standalone Application".
Each node in the run results tree is an element in the results.xml file. In addition, there are different
elements that represent different types of information displayed in the run results. You can take run
result information from the .xml file and use XSL to display the information you require in a customized
format (either when printing from within the Run Results Viewer, when displaying run results in your
own customized results viewer, or when exporting the run results to an .html file).
The diagram below for a GUI test, shows the correlation between some of the elements in the .xml file
and the items they represent in the run results. These elements are similar for both tests and business
components.
XSL provides you with the tools to describe exactly which run result information to display and exactly
where and how to display, print or export it. You can also modify the .css file referenced by the .xsl
file, to change the appearance of the report (for example, fonts, colors, and so forth).
For example, in the results.xml file, one element tag contains the name of an action or a component,
and another element tag contains information on the time at which the run session is performed. Using
XSL, you could tell your customized Run Results Viewer that the action or component name should be
displayed in a specific place on the page and in a bold green font, and that the time information should
not be displayed at all.
You may find it easier to modify the existing .xsl and .css files provided with the Run Results Viewer
application, instead of creating your own customized files from scratch. The files are located in the
HP\Run Results Viewer\dat folder, and are named as follows:
l PShort.xsl. Specifies the content of the run results report printed, or exported to an HTML file,
when you select the Short option in the Print or Export to HTML File dialog boxes.
l PDetails.xsl. Specifies the content of the run results report printed, or exported to an HTML file,
when you select the Detailed option in the Print or Export to HTML File dialog boxes.
l PStringTable.xsl. Specifies the string constants to be used in the exported document. For
example, Iteration # may be used for the iteration number prefix. If you select the User-defined
XSL option in the Print or Export to HTML File dialog boxes, the .xsl file you specify must contain an
"include" call to this file. You can localize the strings, if needed.
l PResults.css. Specifies the appearance of the run results print preview. This file is referenced by
the above .xsl files.
l Results.css. Specifies the styles, fonts, and colors of the various elements displayed in the run
results.
For more details on printing run results using a customized .xsl file, see "Print Dialog Box (Run Results
Viewer)" on page 62.
For more details on exporting the run results to a file using a customized .xsl file, see "Export Run
Results Dialog Box (Run Results Viewer)" on page 57.
UFT only: For details on the structure of the XML schema, and a description of the elements and
attributes you can use to customize the run results reports, see the HP Run Results Schema Reference
(Help > HP UFT GUI Testing Automation and Schema References Help > HP Run Results Schema
Reference).
GUI Tests
Tests saved in the file system. By default, the results of a GUI test saved in the file system are stored
in the test folder. When you run your test, you can specify a different location to store the results, using
the Results Location tab of the Run dialog box. Specifying your own location for the results file can
make it easier for you to locate the results file in the file system.
Tests saved in ALM. Run results are stored in the test folder in ALM. You cannot change the location of
the run session results.
For details, see the section describing the Run dialog box in the HP Unified Functional Testing User Guide.
GUI Components
By default, the results of a component run are stored in an ALM cache folder on your computer.
When you run your test, you can specify a different location to store the results, using the Results
Location tab of the Run dialog box. Specifying your own location for the results file can make it easier
for you to locate the results file in the file system.
For details, see section describing the Run dialog box in the HP Unified Functional Testing User Guide.
API Tests
Tests saved in the file system. By default, the results of API tests that are saved in the file system, are
stored in the test folder. When you run your test, you can specify a different location to store the
results, using the Results Location tab of the Run dialog box. Specifying your own location for the
results file can make it easier for you to locate the results file in the file system.
Tests saved in ALM. Run results are stored in your ALM project. You cannot change the location of the
run session results.
You add the Report function to the step's events. For details, see the section on Custom Code and
Events in the HP Unified Functional Testing User Guide.
The following example prints APR-12-2010_CYCLE_1 in the Value column for TestID.
args.Activity.Report("TestID","APR-12-2010_CYCLE_1");
The report displays the keyword and its value at the Activity level of the results. For details, see
"Captured Data Pane (Run Results Viewer) " on page 40.
You can add the Run Results Viewer to the Start screen by navigating to its location on the file system
or the Desktop screen and pinning it to the Start screen.
In addition, you can add other related files, including .exe files and documentation the Start screen by
pinning these items.
Note: By default, the Start and Apps screens on Windows 8.x or higher are set to open Internet
Explorer in Metro Mode. However, if User Account Control is turned off on your computer, Windows
8 will not open Internet Explorer in Metro mode. Therefore, if you try to open an HTML shortcut
from the Start or Apps screen, such as the UFT Help or Readme file, an error will be displayed.
To solve this, you can change the default behavior of Internet Explorer so that it never opens in
Metro mode. In the Internet Properties dialog box > Programs tab, select Always in Internet
Explorer on the desktop for the Choose how you open links option. For more details, see
http://support.microsoft.com/kb/2736601 and
http://blogs.msdn.com/b/ie/archive/2012/03/26/launch-options-for-internet-explorer-10-on-
windows-8.aspx.
Note: For details on accessing UFT and UFT tools and files in Windows 8 and Windows Server
2012, see "Accessing the UFT in Windows 8.X or Higher Operating Systems" on the previous
page.
l In UFT, select View > Last Run Results or click the Results button .
l From the Start menu, select Start > All Programs >HP Software > HP Run Results Viewer > Run
Results Viewer.
l Run a test or component. By default, the results are displayed in the Run Results Viewer at the end of
the run session. (In UFT, you can change the default setting in the Run Sessions pane of the Options
dialog box. For details, see the HP Unified Functional Testing User Guide.)
Note: This section describes how to open tests and components run in UFT. For other types of
tests, see your testing product's documentation.
If the Run Results Viewer opened automatically, click the Open button or select File > Open .
Browse to the relevant results. For details, see "Open Run Results Dialog Box" on page 61.
When you open run results in the Run Results Viewer for the first time, the tree expands one level at a
time. If the child branches under a parent branch were previously expanded, that state is maintained
when you expand or collapse the parent branch.
l "Find specific steps within the Run Results: " on the next page
l "Filter the tree to display only nodes that match certain criteria: " on the next page
Move between previously selected nodes within the run results tree:
Click the Go to Previous Node or Go to Next Node buttons .
You can search for text, status, and/or types of nodes. For details, see "Run Results Tree Pane and
Search Box" on page 32.
Filter the tree to display only nodes that match certain criteria:
Use the Filter dialog box (View > Filters). For details, see "Filter Dialog Box (Run Results Viewer) " on
page 60.
Docked panes are fixed in a set position relative to the rest of the application. For example, when you
move a pane to a position indicated by a marker, the pane is docked in that position.
Floating panes are displayed on top of all other windows. They can be dragged to any position on your
screen, even outside of the Run Results Viewer.
Note: This feature is disabled for a variety of settings. For details, see "Guidelines for using the
Jump to Step in Test command" below, below.
1. Make sure that UFT is open to the test whose results are displayed in the Run Results Viewer.
2. Select a node in the run results tree.
3. Perform one of the following:
a. Click the Jump to Step in Test button from the Run Results toolbar.
b. Right-click and select Jump to Step in Test from the context menu.
c. Select View >Jump to Step in Test.
4. The UFT window is activated and the step is highlighted.
l "Prerequisites" below
l "Connect to an ALM project" below
l "Open the New Defect dialog box" below
l "Modify the defect information if needed and submit it" below
l "Results" below
1. Prerequisites
Ensure that the ALM client is installed on your computer. (Enter the ALM Server URL in a browser
and ensure that the Login screen is displayed.)
Select Tools > ALM Connection or click the ALM Connection button and connect to an ALM
project. For details, see "HP ALM Connection Dialog Box (Run Results Viewer)" on page 65.
Note: If you do not connect to an ALM project before proceeding to the next step, you are
prompted to connect before continuing.
Select Tools > Add Defect or click the Add Defect button to open the New Defect dialog box in
the specified ALM project. The New Defect dialog box opens.
Tip: You can attach movies (.fbr files) to defects in ALM. If you have the Unified Functional
Testing Add-in for ALM installed, you can view the movies from ALM.
5. Results
The defect is added to the ALM project's defect database.
l "Prerequisites" below
l "Modify the Run settings in the Options dialog box" below
l "Results" on the next page
1. Prerequisites
l In UFT, make sure you are connected to the relevant ALM project prior to the run session (ALM >
ALM Connection).
l The run results must be stored in this ALM project.
c. Select the Submit a defect to ALM for each failed step check box.
3. Results
A sample of the information that is submitted to ALM for each defect is shown below:
Click Export. The Save As dialog box opens. Specify the file name and path, and select the required
file type.
Note: Only the system monitor data is exported, not the graph.
4. Results
When you click Save, the file is exported in the specified format to the designated location.
Note: You can view .fbr files in the HP Micro Recorder (as described in "Viewing Screen
Recorder Movie Files in the HP Micro Player" on page 54). You can also attach .fbr files to
defects in ALM. If you have the Unified Functional Testing Add-in for ALM installed, you can
view the movies from ALM.
Note: For details on accessing UFT and UFT tools and files in Windows 8 and Windows Server
2012, see "Accessing the UFT in Windows 8.X or Higher Operating Systems" on page 15.
2. Use the controls at the top of the window to access a particular location in the movie or to modify
the volume settings.
Prerequisites
To delete run results from an ALM project, you must first:
l Make sure that you have Delete Run permissions for this ALM project.
l Connect to the ALM project. For details see, "HP ALM Connection Dialog Box (Run Results Viewer)" on
page 65.
For details, see "Run Results Deletion Tool (UFT Only)" on page 68.
Results
The selected run results are deleted from the file system and/or the ALM project.
GUI Test. The following example shows the Executive Summary results of a test. Notice that the results
for a test are organized by the test's actions.
In the Statistics area, you can see how many iterations passed, contained warnings, or failed, and, when
previous runs exist, you can compare the current results with the previous results. You can also access
the previous run results by clicking the Open button.
Note: In this example, the component failed due to a run error in a test object. If the run error had
not occurred, the Result would indicate Done.
UFT API Test. The following example shows an Executive Summary for an API test run:
l Select HP Software > HP Run Results Viewer > Run Results Viewer from the Start Menu.
By default, the left pane (dockable) contains the run results tree. The right side of the window contains
two rows of additional dockable panes. These user interface elements are described below (unlabeled
elements are shown in angle brackets):
UI Elements Description
<Run Results Viewer menu See "Run Results Viewer Commands" on the next page.
bar and toolbar>
Executive Summary Page l A high-level results overview report (general information, pass/fail status, statistics, link to
previous run results (if any), notes, and so on) displayed in the Result Details pane when
the topmost node is selected. For details, see "Executive Summary Page" on page 38.
l ALM information for your test (if the test or component was run from ALM, or if a test that
is stored in ALM is run from UFT and you choose to store the results in ALM).
UI Elements Description
"Run Results Tree Pane l A graphical representation of the results in an expandable tree
and Search Box" on l A search box
page 32
l Displays the test or component steps, specifying exactly where application failures
occurred
"Result Details Pane (Run Detailed explanations of each step and checkpoint pass or failure, at each stage of the test or
Results Viewer) " on component.
page 37
"Captured Data Pane (Run l A still image of the state of your application at a particular step
Results Viewer) " on l For UFT, additional information, such as a bitmap checkpoint image.
page 40
For details, see "Captured Data Pane (Run Results Viewer) " on page 40.
"Screen Recorder Pane A movie clip of the state of your application at a particular step or of the entire test or
(Run Results Viewer) (UFT component
GUI Testing Only)" on
page 52
"System Monitor Pane Any system counters that were monitored for your test or component
(Run Results Viewer) (UFT
GUI Testing Only)" on
page 54
"Log Tracking Pane (Run Any log messages that were received for your test or component
Results Viewer) (UFT GUI
Tests Only)" on page 50
l A description of any highlighted menu command (Available only if the menu command is
enabled)
l The status of the currently selected command
l Connection information (when connected to an ALM project)
l A filter indication icon (when the results are filtered)
File > Open CTRL+O Opens the Open Run Results dialog box, enabling you to open saved run results from
the file system or from ALM.
File > Print CTRL+P Opens the Print dialog box, enabling you to print the results of the run session.
For details, see "Print Dialog Box (Run Results Viewer)" on page 62.
-- File > Print CTRL+F2 Opens the Print Preview dialog box, enabling you to preview the results of the run
Preview session prior to printing.
For details, see "Print Preview Dialog Box (Run Results Viewer)" on page 64.
-- File > Export -- Opens the Export Run Results dialog box, enabling you to save various parts of the
To File results as external files.
For details, see "Export Run Results Dialog Box (Run Results Viewer)" on
page 57.
-- File > Remove -- (UFT GUI testing only) Enables you to remove a stored movie from the results of a test
Movie from or component. This reduces the size of the run results file.
Results
-- View > Run -- Shows or hides the Run Results Viewer toolbar.
Results
Viewer
Toolbar
-- View > Status -- Shows or hides the status bar, which indicates:
Bar l A hint about the currently selected command
l The status of the Run Results Viewer
l The ALM server name and project to which the Run Results Viewer is connected
l Whether the results are currently filtered (displays a Filter icon when a filter is
applied)
-- View > Result -- Opens the Results Details pane if it is closed or brings it into focus. For details, see
Details "Result Details Pane (Run Results Viewer) " on page 37.
-- View > Screen -- (UFT GUI testing only) Opens the Screen Recorder pane if it is closed or brings it into
Recorder focus. For details, see "Screen Recorder Pane (Run Results Viewer) (UFT GUI
Testing Only)" on page 52.
-- View > -- (UFT GUI testing only) Opens the System Monitor pane if it is closed or brings it into
System focus. For details, see "System Monitor Pane (Run Results Viewer) (UFT GUI
Monitor Testing Only)" on page 54.
-- View > -- Opens the Captured Data pane if it is closed or brings it into focus. For details, see
Captured "Captured Data Pane (Run Results Viewer) " on page 40.
Data
-- View > Data -- Opens the Data pane if it is closed or brings it into focus. For details, see "Data Pane
(Run Results Viewer) " on page 49.
-- View > Log -- (UFT GUI testing only) Opens the Log Tracking pane if it is closed or brings it into focus.
Tracking For details, see "Log Tracking Pane (Run Results Viewer) (UFT GUI Tests Only)"
on page 50.
-- View > -- Restores the default layout of the Run Results Viewer.
Restore
Layout
View > Filters CTRL+T Opens the Filters dialog box, enabling you to filter the information displayed. For more
details, see "Filter Dialog Box (Run Results Viewer) " on page 60.
View > -- Collapses all of the branches in the run results tree.
Collapse All Also available as a context menu option to collapse all of the nodes under the selected
node.
View > -- Collapses all of the branches in the run results tree.
Collapse All Also available as a context menu option to collapse all of the nodes under the selected
node.
View > Go to -- Moves the cursor to the previously selected node in the tree.
Previous Node
View > Go to -- Moves the cursor to the node you selected in the tree prior to clicking the Go to
Next Node Previous Node button.
View > Jump CTRL+J (UFT GUI tests only) Activates the UFT window and highlights the step in the test
to Step in corresponding to the selected node in the Run Results tree.
Test For details, see "How to Jump to a Step in a GUI Test (UFT GUI Tests Only)" on
page 20.
Tools > Add -- Enables you to add a defect to your ALM project. If you are not currently connected to
Defect ALM, opens the ALM Connection dialog box. For more details, see "How to Manually
Submit Defects to ALM" on page 20.
Tools > ALM -- Opens the HP ALM Connection dialog box, enabling you to connect to an ALM project.
Connection For more details, see "HP ALM Connection Dialog Box (Run Results Viewer)" on
page 65.
-- Help > About -- Displays version information about the HP Run Results Viewer.
Run Results
Viewer
The following example shows the run results tree for a GUI test. Similar results would be displayed for a
GUI component. For UFT API tests, the tree shows each of the individual test steps and checkpoints.
In the following example, eight instances of the searched for text, Welcome, were found.
To access Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
The Run Results Tree pane is displayed by default on the left side of the Run Results Viewer. It cannot be
hidden.
The Search box is located directly above the tree and can be expanded by clicking the Expand button.
Important l Click a node in the tree to view its details in the Result Details pane. Other panes also display information
information for the test or component or highlighted step, if available.
l You can collapse or expand a node in the run results tree to change the level of detail that the tree
displays.
l You can also use the "Filter Dialog Box (Run Results Viewer) " on page 60 commands to control
what is displayed in the run results tree.
UI Description
Elements
Note: If a test does not contain checkpoints, no icon is displayed. For components, this icon is displayed
only if the component step contains one of the following:
Indicates a step that failed. Failed steps cause all parent steps (up to the root action, test, or component) to fail as
well.
(UFT GUI tests only) Indicates an information step. This does not affect the pass/fail status of the step.
(Relevant only for UFT GUI tests)
UI Description
Elements
Indicates a warning, meaning that the step did not succeed, but it did not cause the action, test, or component to
fail.
Indicates a step that failed unexpectedly, such as when an object is not found for a checkpoint.
(UFT GUI tests and components only) Indicates that the Smart Identification mechanism successfully found the
object.
(UFT GUI tests and components only) Indicates that a recovery scenario was activated.
(UFT GUI tests and components only) Square brackets around a test object name indicate that the test object was
created dynamically during the run session. A dynamic test object is created either using programmatic
descriptions or by using an object returned by a ChildObjects method, and is not saved in the object
repository.
(UFT GUI tests and components only) Displays the Maintenance Mode Update Result , which is a table that
describes the Action taken by Maintenance Run Wizard on a failed step and its Details. Displayed only for tests or
components run in Maintenance Run Mode. For more details, see the section describing Maintenance Run Mode in
the HP Unified Functional Testing User Guide .
Search Box
The Search box user interface elements are described below:
UI Description
Elements
Text box in which you can optionally enter text for which to search.
If the specified text is found in one or more tree nodes, the text area indicates this, as shown below:
In this example, 1 of 6 indicates that there are six nodes displaying the text, Welcome, and the first
matching node is highlighted in the tree.
Search. Finds the next instance that matches the criteria you specified in the Search box. Click this button to jump
to each node that matches your search criteria.
Expand or Collapse. Shows or hides the lower part of the Search box.
Possible values:
l Passed. Searches for steps that passed and match your other selection criteria.
l Failed. Searches for steps that failed and match your other selection criteria.
UI Description
Elements
l Done. Searches for steps with the status Done (steps that were performed successfully but did not receive a
pass, fail, or warning status) that match your other selection criteria.
l Warning. Searches for steps with the status Warning (steps that did not pass, but did not cause the test to
fail) that match your other selection criteria.
Note: If the tree does not contain any steps that match a particular status, that option is grayed out in the
Search box.
Node The type of node to search for (together with your other search criteria). (Optional)
type Possible values:
l Iteration. Searches for Iteration nodes that match your other selection criteria.
l Action. Searches for action nodes that match your other selection criteria.
l Step. Searches for steps that match your other selection criteria.
l Reporter. Searches for Reporter steps that match your other selection criteria.
Note: This is not relevant for Reporter.ReportNote steps, which are displayed in the Executive
Summary page and not in the run results tree.
l Checkpoint/Output Value. Searches for checkpoint and output value steps that match your other selection
criteria.
Note: If the tree does not contain a particular node type, that option is grayed out in the Search box.
l Up
l Down
The Executive Summary is displayed when the topmost node in the run results tree is selected.
Result details are displayed when any node (other than the topmost node) is selected in the run results
tree.
l To open the Result Details for a step, select the relevant node in the tree.
2. Select the Result Details tab. (This assumes that the default layout is displayed.)
Tip: If the Result Details pane is hidden, select View > Result Details to show it.
Important By default, when the Run Results Viewer opens after a run session, an Executive Summary is displayed in the
information Result Details pane. This summary displays run session information about the test or component. It also
includes run Statistics and Notes (if any were included).
For any other node, the details in the Result Details pane are specific for the step selected in the run results tree.
For example, the details may include input or output parameters, or may indicate that the session ran in Update
Run Mode.
User interface elements are described below (unlabeled elements are shown in angle brackets):
Executive Includes:
UI Description
Elements
Summary l the test or component name and result details, and configuration details, if any
l time-related information for the run
l the product from which the test or component was run
l ALM server and project, if UFT was connected to an ALM project during the run
Note: If a test or component that is stored in ALM is run from UFT, but you choose to store the results
in a temporary location, the Test set and Test instance fields are not displayed in the results.
Statistics Provides graphical, status-related statistics for the current run and the previous run (if any). If the test or
component was run previously, you can click Open to open the previous run results in a new Run Results
Viewer window.
Notes Displays notes related to the run session, if any were added to the results using the
Reporter.ReportNote Utility statement. For details, see the Utility Objects section of the HP UFT
Object Model Reference for GUI Testing.
Parameters Displays any test or component input and/or output parameters. For details, see "Parameterized Values in
the Run Results " on page 90.
Note: A test, component, iteration, or action containing a step marked Warning may still be labeled Passed
or Done.
<step Details about the step, such as the object on which the step was performed, the timestamp, the step results, and
details> so on. The information in this area changes according to the type of step.
UI Description
Elements
The following image shows an example of the Captured Data pane with a still image of an application
taken during a GUI testing run session.
The following image shows the Captured Data pane with the Web Service Call properties for a test step.
To access Select View > Captured Data or click the Captured Data tab.
Important l Screen captures for UFT GUI steps. By default, UFT saves a still image of your application for failed
information steps. When you select a failed step in the run results tree and select the Captured Data pane, the pane
displays a screen capture of your application corresponding to the highlighted step in the run results tree. If
the highlighted step does not contain an error, no screen capture is displayed.
In UFT, you instruct UFT to include still images of your application in the run results by setting the Save still
image captures to results option in the Screen Capture pane (Tools > Options > GUI Testing tab of the
Options dialog box. For details, see the section describing the Screen Capture pane in the HP Unified
l In UFT API Testing. You can programmatically add items to the report. For details, see "Custom
Fields (UFT API Testing Only)" on page 14.
l Captured Data pane for file content checkpoint steps. The captured data pane displays a side-by-
side comparison of the expected and actual lines from the file. For details, see "File Content Checkpoint
Results (UFT GUI Tests Only) " on page 80.
l Start, End. General information about the Start and End activities.
l Test Flow/Loop. Information about the loop to which the test steps belong, such as Test Flow.
l <Step Name>. Captured data from the selected step.
l For service type activities, this level shows the Request and Response data for the operation or
method.
l For the Report Message activity, this level displays the custom message defined in the activity's
properties.
l Checkpoints. Data about the checkpoints such as the Expected and Actual values, the method of
evaluation (Equals, Does Not Equal, and so on) and status.
The following example shows the Request and Response captured data for the GetFlights operation
from the sample Web Service.
For built-in activities, the Step Properties table shows the values used during the test run.
For service requests, you can observe the actual values in the Request/Response table.
Array Checkpoints
When you select the Checkpoints node in the left pane, the Captured Data pane provides a list of the
checkpoints, their expected values, and actual results. In the case of a checkpoint in the form of an
array, the Captured Data pane provides a link to a checkpoint report.
The checkpoint report opens in a separate browser window and provides details about the checkpoints
in each of the array elements. You can expand each checkpoint to see what its expected and actual
values were.
To view this table properly, you should enable active content in your browser in the following way:
In the upper part of the Captured Data pane, click the link Report File link to open the complete
comparison report in an external browser.
Converted Strings
The XML to String and JSON to String steps provide their results in the Captured Data pane. The Step
Properties table shows the resulting strings for the OutputString entry.
Custom Messages
The Captured Data pane also shows custom messages that you sent to the output using the Report
function in an event handler.
For details, see the Coding Events section in the HP Unified Functional Testing User Guide.
this.ConcatenateStringsActivity5.Report("Test Cycle","CYCLE_JULY_2012_B");
Test Flow Pane (Run Results Viewer) (UFT API Tests Only)
This pane contains a snapshot of the canvas containing the test's steps . The snapshot shows the order
of the steps and the connections between them. You can scroll down, zoom in, and set the displayed
details level, as you would in the test's canvas.
If you select a node in the Run Results tree that represents a step in the Test Flow, it is highlighted in
this pane.
In the following example, the Test Flow pane contains shows how two steps are connected, and the
test's internal loops.
To access Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
Important information The Test Flow pane is not shown by default when the Run Results Viewer opens.
User interface elements are described below (unlabeled elements are shown in angle brackets):
UI Elements Description
Zoom Level scroller Enables you to control the magnification of the steps in the canvas.
Restore Default Zoom. Restores the canvas display to the default view.
Details Level Enables you to select the detail level of the display:
l None
l Links only
l Links and linked parameters
l Links and all parameters
If you select a node in the run results tree that represents a step using data table values, the relevant
row is highlighted in this pane.
In the following example, the data table contains parameterized flight departure and arrival values.
To access Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
Important l This pane may display one data sheet or several data sheets divided by tabs. For example, a UFT GUI test
information may use data table parameters from the global sheet and individual action sheets.
Note: Sheets that contain no data are not displayed in the results.
l Use the context menu items to copy or export the data in the run results.
See also For details on the run-time data table, see the section describing the Data pane in the HP Unified Functional
Testing User Guide .
User interface elements are described below (unlabeled elements are shown in angle brackets):
UI Description
Elements
<Row> Represents the set of values that UFT submitted for the parameterized arguments during a single iteration of the
action (UFT GUI tests only), test, or configuration.
<Column> Represents the list of values for a single parameterized argument. The column header is the parameter name.
Log Tracking Pane (Run Results Viewer) (UFT GUI Tests Only)
This pane displays a complete list of log messages that UFT received from your application during the
run session.
In addition to viewing the log messages, when you select a message, you can see its details in the
"Result Details Pane (Run Results Viewer) " on page 37 pane.
Tip: You can "Print Dialog Box (Run Results Viewer)" on page 62 or "Export Run Results Dialog Box
(Run Results Viewer)" on page 57 the log tracking details to a file to show to a developer, or you can
provide the developer with the standalone Run Results Viewer installation so that the developer
can view and analyze the results directly on his or her own computer. For details, see "How to Install
the Run Results Viewer as a Standalone Application" on page 16.
To access Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
Important l Japanese characters - known Log4Net issue. If a log message contains Japanese characters, these
information characters are displayed as question marks (?) in the Message column of the Run Results Viewer's Log
Tracking pane. This is due to a known bug in log4net.Layout.XmlLayoutSchemaLog4j - version 1.2.10. For
details, see https://issues.apache.org/jira/browse/LOG4NET-229.
l Showing and hiding columns. You can show or hide columns in the Log Tracking pane by right-clicking
any column header and selecting or clearing a menu option.
l Reordering columns. You can reorder the columns in the pane by dragging and dropping a column header
to a different location.
See also l "Find Dialog Box (Log Tracking Pane - Run Results Viewer) (UFT GUI Testing Only)" on page 58
l The Log Tracking section in the HP Unified Functional Testing User Guide
UI Description
Elements
Find Opens the "Find Dialog Box (Log Tracking Pane - Run Results Viewer) (UFT GUI Testing Only)" on
page 58 dialog box, enabling you to search the log messages by message, level, and character case.
Level The severity level for the log message. Possible level values:
l TRACE
l DEBUG
l INFO
l WARN
l ERROR
UI Description
Elements
l FATAL
To access Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
Select View > Screen Recorder or click the Screen Recorder tab.
Important l Use of multiple monitors: The Screen Recorder records a movie of the operations performed on your
information primary monitor. Therefore, if you are working with multiple monitors, make sure that your application is
fully visible on your primary monitor when recording or running a test or component.
l Prevent UFT from obscuring your application. The Screen Recorder saves a movie of your entire
desktop. You can prevent the UFT window from partially obscuring your application while capturing the
movie by minimizing UFT during the run session. For details, see the section describing the screen recorder in
the HP Unified Functional Testing User Guide .
l View full screen. You can double-click the Screen Recorder pane to display the Screen Recorder in full-
screen mode and hide the run results tree. Double-clicking again restores the Screen Recorder to its
previous size and displays the run results tree. When the Screen Recorder is expanded, the playback controls
at the top of the Screen Recorder automatically hide after approximately three seconds with no mouse
activity, or when you click anywhere on the Screen Recorder. They reappear when you move the mouse
again.
UI Description
Elements
Play/Pause. Click to play or pause the movie. When you click Pause, the relevant tree node is highlighted.
Slider. Drag the bar to view a particular frame in the movie. When you click the bar, the relevant node is
highlighted in the tree. When you play the movie, the slider automatically moves to the position of the currently
displayed frame.
Volume Control. Drag the bar to the right or left to control the movie sound.
You can also attach .fbr files to defects in ALM. If you have the Unified Functional Testing Add-in for ALM
installed, you can view the movies from ALM.
To access Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
Select View > System Monitor or click the System Monitor tab.
Important You can export the data from the System Monitor tab to the following file types: text (.csv or .txt ),
information Excel (.xls ), .xml , or .html . (Graphs are not exported.)
For details, see "Export Run Results Dialog Box (Run Results Viewer)" on page 57.
See also l For details on enabling local system monitoring, the HP Unified Functional Testing User Guide .
UI Description
Elements
Zoom In. Click this button and click anywhere on the graph to zoom in. You can also click and drag over an area
of the graph to zoom in on that area.
Zoom Out. Click this button and click anywhere on the graph to zoom out.
View Full Graph. Click this button to zoom out and view the entire graph. This button is disabled when the
graph is not zoomed in.
Move. Click this button and then click and drag on the graph to scroll right and left. This button is disabled
when the graph is not zoomed in.
Arrow. Click this button and double-click anywhere on the graph to select that point as the current step. The
Current Step indicator moves to the new location and the step is highlighted in the Run Results tree. You can
also hover over any point on a Counter Line in the graph to see the value for the Counter Line at that point.
Application The name of the application for which system counters were monitored.
Name
Currently The list of counters currently displayed in the line graph. The System Monitor tab displays a maximum of two
Displayed counters at one time. To change the counters being displayed, clear the check box for one or both of the
Counters currently selected counters, and select the check box for the desired counters.
Maximum The maximum value the counter achieved during the run session.
Counter
Value
Current The point in the graph representing the step that is currently highlighted in the Run Results tree.
Step
Counter A visual representation of the limit for that counter, if set, as defined in the Local System Monitor pane of the
Limit Line Test Settings dialog box or the Additional Settings pane in the Application Area (in UFT).
UI Description
Elements
If set, a counter that exceeds this limit causes the step to fail. Only the first step that exceeds the counter limit
fails. Subsequent steps that exceed the counter limit are not affected.
Counter The numeric value of the limit for that counter, if set, as defined in the Local System Monitor pane of the Test
Limit Value Settings dialog box or the Additional Settings pane in the Application Area (in UFT).
If set, a counter that exceeds this limit causes the step to fail. Only the first step that exceeds the counter limit
fails. Subsequent steps that exceed the counter limit are not affected.
Time Scale The scale of time in seconds, for the run session.
l "Export Run Results Dialog Box (Run Results Viewer)" on the next page
l "Find Dialog Box (Log Tracking Pane - Run Results Viewer) (UFT GUI Testing Only)" on page 58
l "Filter Dialog Box (Run Results Viewer) " on page 60
l "Open Run Results Dialog Box" on page 61
l "Print Dialog Box (Run Results Viewer)" on page 62
l "Print Preview Dialog Box (Run Results Viewer)" on page 64
l "HP ALM Connection Dialog Box (Run Results Viewer)" on page 65
To access Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
Important l The export time varies according to the size of the results file and the file type you
information select. When selecting the file type, consider the length of time it will take to generate different
document types, especially for a report with many images. .Html files generate the fastest,
followed by .pdf and .doc When exporting a report with 100 or more images to a .doc file, a
dialog box is displayed reminding you that it may take a long time to generate the file. The dialog box
gives you the option to continue exporting with images, continue exporting without images, or to
export to .pdf .
l Screen capture images are not exported for steps on Web-based applications. When you
export run results containing steps on a Web application, any screen capture images for those steps
are not exported to the file. This is because for Web-based applications, the Run Results Viewer
displays the .html corresponding to the relevant Web page (with downloaded images) rather than a
captured image and thus no image is saved with the report.
l Exporting to a .doc file. Requires that a supported version of Microsoft Word be installed on the
Run Results Viewer computer. For details, see the Product Availability Matrix, available from the HP
Support Matrix page (requires an HP passport).
UI Description
Elements
Report The type of report you want to export, for example, Step Details or System Monitor .
type
l User-defined XSL. Enables you to browse to and select a customized .xsl file. You can create a
customized .xsl file that specifies the information to be included in the exported report, and the way it should
appear.
If you decide to modify one of the existing .xsl files provided with the Run Results Viewer, and you copy that
file to a different folder, make sure to copy over all of the .xsl files that are listed in that .xsl file's "include"
calls, as well as the .css files. For details, see "Run Results XML File" on page 11.
Find Dialog Box (Log Tracking Pane - Run Results Viewer) (UFT
GUI Testing Only)
This dialog box enables you to search for a log message by message text, level, and case (upper-
case/lower-case characters).
To access 1. Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
2. Display the Log Tracking pane, as described in "Log Tracking Pane (Run Results Viewer) (UFT
Important l This dialog box is relevant only for the Log Tracking pane. To perform a search in the run results tree,
information use the "Search Box" on page 35.
UI Description
Elements
Find Enter the text to find. This can be message text or a severity level.
Message Searches the Message column for the text specified in the Find box.
Level Searches the Level column for the text specified in the Find box. Possible level values:
l TRACE
l DEBUG
l INFO
l WARN
l ERROR
l FATAL
Match Displays only those occurrences that match the capitalization (upper-case and lower-case characters) you
case specified for the text in the Find box.
Next Jumps to the next instance that matches the selected criteria.
Previous Jumps to the previous instance that matches the selected criteria.
To access 1. Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
Important l When you apply a filter, a filter icon is displayed on the status bar, and (Filtered) is appended to the Search
information box title bar. These visual changes indicate that the run results tree is currently displaying only those nodes
that match your filter criteria.
l (UFT GUI tests only) You can use Reporter.Filter statements in the Editor to disable or enable the
saving of selected steps, or to save only steps with Failed or Warning status. For more details on saving
run session information, see the HP Unified Functional Testing User Guide or the HP UFT Object Model
Reference for GUI Testing. The Reporter.Filter statement differs from the Filters dialog box
described above. The Reporter.Filter statement determines which steps are saved in the Run
Results, while the Filter dialog box determines which steps are displayed at any time.
UI Elements Description
Filter what A text box in which you enter the text by which you want to filter. (Optional)
UI Elements Description
Possible values:
l Passed. Displays the run results for the steps that passed and match your filter criteria.
l Failed. Displays the run results for the steps that failed and match your filter criteria.
l Done. Displays the run results for the steps with the status Done (steps that were performed
successfully but did not receive a pass, fail, or warning status) that match your filter criteria.
l Warning. Displays the run results for the steps with the status Warning (steps that did not pass, but
did not cause the test to fail) that match your filter criteria.
Node type Displays all results that match your selection criteria based on: (Optional)
l Iteration. Displays the run results in the run results tree for the iterations specified in the Iterations
area.
l Action. Displays the run results for all actions in the run results tree that match your other selection
criteria. (Not relevant for components.)
l Step. Displays the run results for all steps in the run results tree that match your other selection
criteria.
l Reporter. Displays the run results for all Reporter steps in the run results tree that match your other
selection criteria.
Note: This is not relevant for Reporter.ReportNote steps, which are displayed in the Notes
area of the Executive Summary page and not in the run results tree.
l Checkpoint/Output Value. Displays the run results for all checkpoint and output value steps in the
run results tree that match your other selection criteria.
To access 1. Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
Important l To view results stored in ALM, you must first connect to your ALM project. For details, see "HP ALM
information for Connection Dialog Box (Run Results Viewer)" on page 65.
UFT tests l By default, results files for UFT tests are stored together with the test, for example:
C:\%HOMEPATH%\My Documents\Unified Functional Testing\<Test
name>\<ResultName>
l To view result files for QuickTest Professional version 6.5 and earlier, use the Test/Run Results
Viewer in an earlier version of QuickTest.
UI Description
Elements
Test The name of the test for which you want to view results. The test can be located in the file system or in an ALM
name project. If you select this option, you must also specify the Run name.
Results The actual .xml results file. The file must be located in the file system.
XML file
To access 1. Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
UI Description
Elements
Print l All. Prints the run results for the entire test or component.
range l Selection. Prints the run results information for the selected branch in the run results tree.
Print l Short. Prints a summary line (when available) for each item in the run results tree. This option is only available if
format you selected All in Print range.
l Detailed. Prints all available information for each item in the run results tree, or for the selected branch,
according to your selection in Print range. The printed report includes still images associated with the steps in
your run results. If a bitmap checkpoint step displays bitmaps, these are also included.
l User-defined XSL. Enables you to browse to and select a customized .xsl file. You can create a customized
.xsl file that specifies the information to be included in the printed report, and the way it should appear. For
more details, see "Run Results XML File" on page 11.
Note: The Print format options are available only for run results last modified with QuickTest version 8.0
and later.
Print Opens the standard Windows Print dialog box, enabling you to send the selected run results any installed printer.
To access 1. Open the Run Results Viewer, as described in "How to Open Run Results" on page 16.
2. Select File > Print Preview .
Important The Print Preview option is available only for run results last modified with QuickTest version 8.0
information and later.
UI Description
Elements
Print l All. Previews the run results for the entire test or component.
range l Selection. Previews run results information for the selected branch in the run results tree.
Print l Short. Previews a summary line (when available) for each item in the run results tree. This option is only
format available if you selected All in Print range.
l Detailed. Previews all available information for each item in the run results tree, or for the selected branch,
according to your selection in Print range. The preview includes still images associated with the steps in your
run results. If a bitmap checkpoint step displays bitmaps, these are also included.
l User-defined XSL. Enables you to browse to and select a customized .xsl file. You can create a customized
.xsl file that specifies the information to be included in the preview, and the way it should appear. For more
details, see "Run Results XML File" on page 11.
Preview Displays the run results on screen as they are displayed when printed.
UI Description
Elements
Tip: If some of the information is cut off in the preview, for example, if checkpoint names are too long to fit
in the display, click the Page Setup button in the Print Preview window and change the page
orientation from Portrait to Landscape.
Important l 1st time connection. The first time you connect to an ALM server, you must connect as a user with
information administrator privileges on the computer on which you are connecting.
l Connecting to different versions of Quality Center or ALM. You cannot connect to multiple versions
of Quality Center or ALM in the same Run Results Viewer session. Close and reopen Run Results Viewer to
l Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012 Users. The security
settings may prevent you from connecting to an ALM project:
This can occur when the UAC (User Account Control) option is set to ON, and you have never connected to an
ALM project.
To connect to ALM for the first time, you must disable the UAC option. After you successfully connect to
ALM, you can turn the UAC option on again. Thereafter, you should be able to connect to ALM, as needed.
l Connect. The connection process has two steps. First, you connect to a local or remote ALM server. This
server handles the connections between Run Results Viewer and the ALM project. You must provide a user
name and a password.
Next, you choose the project you want to access. The project stores tests and run session information for
the application you are testing.
l Disconnect. You can disconnect from an ALM project or from an ALM server.
l If you disconnect from an ALM server without first disconnecting from a project, the Run Results Viewer
connection to that project database is automatically disconnected.
l SSL Certificates. If you are attempting to connect to an ALM project with a https:// prefix, but your
computer does not have a valid SSL certificate, the connection will fail.
l ALM servers using external authentication. To use an ALM server using external authentication, you
must have your external certificate installed on both the computer running ALM and the computer running
Run Results Viewer. When you log in to the ALM server using external authentication, a dialog prompts you
to select your certificate from the list of available certificates.
l After running tests, from ALM, you can optionally automatically upload your run results to ALM if you are
running a test from ALM. This option is set in ALM as a site parameter for your project. For details, see the
HP Application Lifecycle Management Administrator Guide .
UI Elements Description
Server URL The URL address of the Web server where ALM is installed.
You can choose a server that is accessible via a Local Area Network (LAN) or a Wide Area
Network (WAN).
You can connect to any currently supported version of ALM. For a list of supported
versions, see the HP Unified Functional Testing Product Availability Matrix, available
from the HP Support Matrix page (requires an HP passport).
Note: If you are connecting to an ALM server using external authentication, you do
not need to enter a user name. If you do enter a user name, Run Results Viewer
ignores the entered name when connecting.
UI Elements Description
Note:
To enter a password in any CJK (Chinese, Japanese, Korean) language, copy/paste
the password into the edit box. (Windows does not support typed CJK characters in
password fields.)
If you are connecting to an ALM server using external authentication, you do not
need to enter a password. If you do enter a password, Run Results Viewer ignores
the entered password when connecting.
Disconnect, and at the top of the dialog box, the Disconnected icon changes
to a Connected icon .
Note: Only those projects for which you are a defined user are displayed.
Restore connection on startup Instructs Run Results Viewer to automatically reconnect to the ALM server every time you
open Run Results Viewer.
You can sort the run results by name, date, size, and so on, so that you can more easily identify the
results you want to delete.
To access In the Run Results Viewer, select Tools > Run Results Deletion Tool or select the Run Results
Important l To delete run results from an ALM project, connect the Run Results Viewer to an ALM project
information for before browsing or entering the path. Specify the ALM test path in the standard ALM format.
HP ALM users
Example: [QC-TEST];;Subject\<folder name>\<test name>;;
For details on connecting to ALM, see "HP ALM Connection Dialog Box (Run Results Viewer)"
on page 65.
l You can delete results from only one test at a time. Make sure that you have Delete Run
permission for this ALM project.
l For details on ALM project permissions, contact your ALM administrator or see the section on
permission settings in the ALM administrator guide.
UI Elements Description
Test or folder The path from which you want to delete run results. When working with the file system, you can specify a
test or a folder. When working with ALM, you cannot specify folders.
Browse Enables you to browse to and select the folder or specific run results that you want to delete. By default,
clicking the Browse button opens the Open Test dialog box. If you want to browse to a folder, click the
down arrow and select Folders to open the Open Folder dialog box.
Include run Adds all run results contained in subfolders of the specified folder to the Run Results area of this dialog box.
results found (Relevant only for folders in the file system. This option is not supported when working with tests in ALM.)
in subfolders
Run Results Lists the run results that are stored in the specified test or folder, together with descriptive information for
each. You can click a column's title to sort run results based on the entries in that column.
Delete Deletes the selected run results from the file system and/or the ALM project. You can select multiple run
results for deletion using standard Windows selection techniques.
<status bar> Displays information regarding the displayed run results, including the number of results selected, the total
number of results in the specified location and the size of the files.
l Local system monitor. After you run a test or component with the local system monitoring option
activated when the test or component is either very short, or the number of seconds entered for the
Enable local system monitoring every: __ seconds option is high (a high percentage relative to the
length of your entire test run), then when you select one of the last steps in the Run Results tree, the
Current Step indicator in the System Monitor pane may jump to a position outside (to the right) of
the graph.
Workaround: Add a Wait statement to the end of the test or reduce the number of seconds entered
in the Enable local system monitoring every: __ seconds option.
l Run session errors. Errors during the run session produce more than one error node in the run
results.
l Exporting run results. When UAC is set to ON and you select to export the Run Results to a system
folder, the exported file is stored under Virtual Storage rather than under the specified folder.
(Relevant for Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012)
l Viewing run results from ALM. If you installed the Run Results Viewer without installing UFT, then
after you run a BPT test from ALM, pressing Show Last Run Results might fail to display the results
in the Run Results Viewer if the Visual C++ 2005 redistributable is installed on your computer.
Workaround: Install the Unified Functional Testing Add-in for ALM from the ALM Add-ins page.
• Concepts 72
• Smart Identification in the Run Results (UFT GUI Testing Only) 72
• Smart Identification - No Object Matches the Learned Description (UFT GUI Testing Only) 72
• Smart Identification - Multiple Objects Match the Learned Description (UFT GUI Testing Only) 73
• Checkpoint and Output Value Results (UFT GUI Testing Only) 75
• Accessibility Checkpoint Results (UFT GUI Tests Only) 75
• Bitmap Checkpoint Results (UFT GUI Tests Only) 79
• File Content Checkpoint Results (UFT GUI Tests Only) 80
• Standard Checkpoint Results (UFT GUI Tests Only) 82
• Table and Database Checkpoint Results (UFT GUI Tests Only) 83
• Text and Text Area Checkpoint Results (UFT GUI Tests Only) 85
• XML Checkpoint Results (UFT GUI Tests Only) 85
• Output Value Results (UFT GUI Tests Only) 86
• File Content Output Value Results (UFT GUI Tests Only) 88
• XML Output Value Results (UFT GUI Tests Only) 88
• Parameterized Values in the Run Results 90
• GUI Tests Containing Calls to UFT API /Service Test Tests (UFT GUI Tests Only) 93
• Reference 94
• Color Settings Dialog Box (Captured Data Pane - Run Results Viewer) (UFT GUI Tests Only) 94
• Filter Dialog Box (Captured Data Pane - Run Results Viewer) (UFT GUI Tests Only) 95
• XML Checkpoint Results Window (UFT GUI Tests Only) 95
• Element Value Dialog Box (Run Results Viewer) (UFT GUI Tests Only) 102
• XML Output Value Results Window (UFT GUI Tests Only) 103
l "Smart Identification - No Object Matches the Learned Description (UFT GUI Testing Only)" below
l "Smart Identification - Multiple Objects Match the Learned Description (UFT GUI Testing Only)" on the
next page
A description An indication that the object (for example, the userName WebEdit object) was not found.
mismatch icon for
the missing object.
For example:
A Smart An indication that the Smart Identification mechanism successfully found the object, and information
Identification icon for on the properties used to find the object. You can use this information to modify the learned test object
the missing object. description, so that UFT can find the object using the description in future run sessions.
For example:
The actual step Normal result details for the performed step.
performed. For
example:
For details on the Smart Identification mechanism, see the section describing Smart Identification in the
HP Unified Functional Testing User Guide.
The image below shows the results for a test or component in which Smart Identification was used to
identify the userName WebEdit object after one of the learned description property values changed.
A Smart An indication that the Smart Identification mechanism successfully found the object, and information on
Identification icon the properties used to find the object. You can use this information to create a unique object description
for the missing for the object, so that UFT can find the object using the description in future run sessions.
object. For example:
The actual step Normal result details for the performed step.
performed. For
example:
The image below shows the results for a test or component in which Smart Identification was used to
uniquely identify the Flight Confirmation: Mercury object after the learned description resulted in
multiple matches.
If the Smart Identification mechanism cannot successfully identify the object, the test or component
fails and a normal failed step is displayed in the run results.
The run results tree displays a separate step for each accessibility option that was checked in each
checkpoint. For example, if you selected all accessibility options, the run results tree for an accessibility
checkpoint may look something like this:
The run result details provide information that can help you pinpoint parts of your Web site that may
not conform to the W3C Web Content Accessibility Guidelines. The information provided for each check
is based on the W3C requirements.
Note: Some of the W3C Web Content Accessibility Guidelines that are relevant to accessibility
checkpoints are cited or summarized in the following sections. This information is not
comprehensive. When checking whether your Web site satisfies the W3C Web Content Accessibility
Guidelines, you should see the complete document at: http://www.w3.org/TR/WAI-WEBCONTENT/.
For details on accessibility checkpoints, see the HP Unified Functional Testing User Guide.
ActiveX Check
Guideline 6 of the W3C Web Content Accessibility Guidelines requires you to ensure that pages are
accessible even when newer technologies are not supported or are turned off. When you select the
ActiveX check, UFT checks whether the selected page or frame contains any ActiveX objects. If it does
not contain any ActiveX objects, the checkpoint passes. If the page or frame does contain ActiveX
objects then the results display a warning and a list of the ActiveX objects so that you can check the
accessibility of these pages on browsers without ActiveX support. For example:
The Captured Data pane displays the captured page or frame, so that you can see the objects listed in
the Alt property check list.
Applet Check
The Applet Check also helps you ensure that pages are accessible, even when newer technologies are
not supported or are turned off (Guideline 6 of the W3C Web Content Accessibility Guidelines), by finding
any Java applets or applications in the checked page or frame. The checkpoint passes if the page or
frame does not contain any Java applets or applications. Otherwise, the results display a warning and a
list of the Java applets and applications. For example:
The Captured Data pane displays the captured page or frame, so that you can see the frames listed in
the Frame Titles check list.
Tables Check
Guideline 5 of the W3C Web Content Accessibility Guidelines requires you to ensure that tables have the
necessary markup to be transformed by accessible browsers and other user agents. It emphasizes that
you should use tables primarily to display truly tabular data and to avoid using tables for layout
purposes unless the table still makes sense when linearized. The TH, TD, THEAD, TFOOT, TBODY, COL, and
COLGROUP tags are recommended so that user agents can help users to navigate among table cells and
access header and other table cell information through auditory means, speech output, or a Braille
display.
The Tables Check checks whether the selected page or frame contains any tables. If it does not, the
checkpoint passes. If the page or frame does contain tables, the results display a warning and a visual
representation of the tag structure of the table. For example:
Note: By default, the information in the Captured Data pane is available only if the bitmap
checkpoint fails. You can change the conditions for when bitmaps are saved in the run results,
using the Save still image captures to results option in the Screen Capture pane (Tools > Options
> GUI Testing tab > Screen Capture node) of the Options dialog box. For details, see the section
describing the Screen Capture pane in the HP Unified Functional Testing User Guide.
For details on bitmap checkpoints and custom comparers, see the section describing bitmap
checkpoints in the HP Unified Functional Testing User Guide.
The details area also specifies whether the checkpoint includes the following options: Match case,
Ignore spaces, Verify page count, and Fail checkpoint for added or removed lines
For failed steps, the Captured Data pane displays any differences found for all lines in the actual file,
regardless of whether they were selected for comparison in the checkpoint. An asterisk (*) adjacent to
the line number indicates that a regular expression was selected for comparison against the actual file.
In the following example, the details of the failed checkpoint indicate that the expected results and the
current results do not match.
Color Opens the "Color Settings Dialog Box (Captured Data Pane - Run Results Viewer) (UFT GUI Tests
Settings Only) " on page 94 dialog box, enabling you to define the text and background color for each filter type.
For details, see the HP Unified Functional Testing User Guide .
Next Finds the next difference between the lines in the compared versions.
Difference
Previous Finds the previous difference between the lines in the compared versions.
Difference
Filter Opens the "Filter Dialog Box (Captured Data Pane - Run Results Viewer) (UFT GUI Tests Only) "
on page 95 dialog box, enabling you to show or hide the following types of filter elements in the
comparison window:
l Modified
l Deleted
l Added
l Identical
Tip: The legend in the top-right corner of the comparison window indicates how many lines match
each filter type. The legend adjacent to a collapsed node indicates how many sub-nodes match each
filter type. For details, see the HP Unified Functional Testing User Guide .
View View Horizontal. Displays the open documents one above the other.
Horizontal View Vertical. Displays the open documents side-by-side.
or
View
Vertical
For details, see the section describing file content checkpoints in the HP Unified Functional Testing User
Guide.
The Captured Data pane displays the image capture for the checkpoint step (if available).
In the following example, the details of the failed checkpoint indicate that the expected results and the
current results do not match. The expected value of the flight departure is Paris, but the actual value is
Frankfurt.
For details, see the section describing standard checkpoints in the HP Unified Functional Testing User
Guide.
If the checkpoint failed, the Captured Data pane shows the table cells or database records that were
checked by the checkpoint. Cell values or records that were checked are displayed in black; cell values
or records that were not checked are displayed in gray. Cells or records that failed the checkpoint are
marked with a failed icon.
You can click the Next Mismatch button in the Captured Data pane to highlight the next table cell
or database record that failed the checkpoint.
You can click the Compare Values button in the Captured Data pane to display the expected and
actual values of the selected table cell or database record.
For details, see the sections describing table checkpoints and database checkpoints in the HP Unified
Functional Testing User Guide.
Text and Text Area Checkpoint Results (UFT GUI Tests Only)
The Result Details pane displays the checkpoint step results, including its status (Passed or Failed), the
date and time the checkpoint was run and the portion of the checkpoint timeout interval that was used
(if any). It also shows the expected text and actual text that was checked, and the verification settings
you specified for the checkpoint.
For details, see the section describing text and text area checkpoints in the HP Unified Functional
Testing User Guide.
The Captured Data pane shows the details of the schema validation (if applicable) and a summary of the
checkpoint results. If the schema validation failed, the reasons for the failure are also shown.
If the checkpoint failed, you can view details of each check performed in the checkpoint by clicking View
XML Checkpoint Results in the Captured Data pane. The XML Checkpoint Results window opens,
displaying details of the checkpoint's failure. For details, see "XML Checkpoint Results Window (UFT GUI
Tests Only) " on page 95.
Note: By default, if the checkpoint passes, the View XML Checkpoint Results button is not
available. The availability of these detailed results is dependent on the Save still image captures
to results setting in the Screen Capture pane (Tools > Options > GUI Testing tab > Screen Capture
node) of the Options dialog box. For details, see the section describing the Screen Capture pane in
the HP Unified Functional Testing User Guide.
including the value that was captured during the run session, its type, and its name, as shown in the
following example. Similar results would be displayed for a component.
For details, see the section describing output values in the HP Unified Functional Testing User Guide.
For details on XML output value steps, see "XML Output Value Results (UFT GUI Tests Only) " on the next
page.
For details, see the section describing file content output values in the HP Unified Functional Testing
User Guide.
From the Captured Data pane, you can view detailed results by clicking View XML Output Value Results
to open the XML Output Value Results window. For details, see "XML Output Value Results Window (UFT
GUI Tests Only) " on page 103.
Note: By default, the View XML Output Value Results button is available only when an error
occurs. The availability of these detailed results is dependent on the Save still image captures to
results setting in the Screen Capture pane (Tools > Options > GUI Testing tab > Screen Capture
node) of the Options dialog box. For details, see the section describing the Screen Capture pane in
the HP Unified Functional Testing User Guide.
For details, see the section describing XML output values in the HP Unified Functional Testing User Guide.
To view parameterized values, expand the nodes in the run results tree and click the root node to view
test or component input and output parameters, or click an action node that contains parameterized
values (tests only).
Test and component parameters are displayed in the Parameters section of the Executive Summary
area of the Results Details pane, which you display by clicking the root node of the run results tree. The
example below shows input test parameters. The Parameters section would be identical for input
component parameters.
If output test or component parameters were defined, they would be displayed in this pane beneath the
input parameters.
For action parameters, the name and value of the input and output parameters are displayed in the
Result Details pane. Similar results would be displayed for a component.
The example above shows input parameters that were defined at the action level. If output parameters
were defined at this level, they would also be displayed in this pane.
For details on defining and using parameters in your tests and components, see the HP Unified
Functional Testing User Guide.
For details on what is displayed for UFT API or Service Test test steps, see the following sections:
To access
In the Captured Data pane, click the Color Settings toolbar button .
UI Elements Description
Modified Text color and background color for the relevant filter elements.
Deleted You can:
Added
Identical l Click a down arrow to select a color from the list of colors in the Custom, Web, or System tabs.
Restore Restores the default color values for each of the filter elements.
To access
In the Captured Data pane, click the Filter toolbar button .
UI Elements Description
Select elements Select or clear a check box. The pane displays only those lines that match the defined filter. You can
to show show or hide the following types of lines:
l Modified
l Deleted
l Added
l Identical
l Expected XML Tree pane. Displays the expected results—the elements, attributes, and values, as
stored in your XML checkpoint.
l Actual XML Tree pane. Displays the actual results—what the XML document actually looked like
during the run session.
l Checkpoint Summary pane. Displays results information for the check performed on the selected
item in the expected results pane.
To access In the Captured Data pane of the Run Results Viewer, click the View XML Checkpoint Results button.
Important When you open the XML Checkpoint Results window, the Checkpoint Summary pane displays the summary
information results for the first checked item in the expected results pane.
Tip: You can double-click any element value in this window to open the Element Value dialog box, which
displays the value in a multi-line edit control. For details, see "Element Value Dialog Box (Run Results
Viewer) (UFT GUI Tests Only)" on page 102.
See also "XML Checkpoint Results (UFT GUI Tests Only) " on page 85
UI Description
Elements
View Checkpoint Summary. Displays the Checkpoint Summary pane, which provides a detailed description of
which parts of an element passed or failed.
View Attribute Details. Displays the Expected Attributes and Actual Attributes panes, for an element whose
attributes were checked.
UI Description
Elements
Find Next Check. Jumps directly to the next checked item in the XML Tree.
Menu option: View > Find Next Check
Find Previous Check. Jumps directly to the previous checked item in the XML Tree.
Menu option: View > Find Previous Check
Find Next Error. Jumps directly to the next error in the XML Tree.
Menu option: View > Find Next Error
Find Previous Error. Jumps directly to the previous error in the XML Tree.
Menu option: View > Find Previous Error
Scroll Trees Simultaneously. Synchronizes the scrolling of the Expected and Actual XML Trees. If this option is
selected, the Expected and Actual XML Trees scroll simultaneously as you navigate through either of the tree
structures. If this option is not selected, you can scroll only one tree at a time.
Help Topics. Opens the help for the XML Checkpoint Results window.
Menu option: View > Help Topics
Scenario 1
In the following example, the airline element tag was changed to airlines and the XML checkpoint
identified the change in the tag structure. The airline element's child element check also failed
because of the mismatch at the parent element level.
To view details of the failed element, select the airline tag from the Expected XML Tree and select
View > Checkpoint Summary to view the Checkpoint Summary in the bottom pane in the XML
Checkpoint Results window.
The text "This element is missing" indicates that the airline element tag changed in your XML
document.
Scenario 2
In the following example, an attribute that is associated with the orders element tag was changed
from the original, expected value of orders1, to a new value of orders2.
To view details of the failed attribute, select the failed element from the Expected XML Tree and select
View > Attribute Details. The Expected Attributes and Actual Attributes panes are displayed at the
bottom of the XML Checkpoint Results window.
Using the Expected Attributes and Actual Attributes panes, you can identify which attribute caused the
error and which values were mismatched.
Scenario 3
In the following example, the actual value of the total element was changed between execution runs,
causing the checkpoint to fail.
To view details of the failed value, select the failed element from the Expected XML Tree and select
View > Checkpoint Summary to view the Checkpoint Summary in the bottom pane in the XML
Checkpoint Results window.
Using the Checkpoint Summary pane, you can compare the expected and actual values of the total
element.
Scenario 4
In the following example, the value of the total element was parameterized and the value's content
caused the checkpoint to fail in this iteration.
The value icon is displayed with a pound symbol to indicate that the value was parameterized.
To view details of the failed value, select the failed element from the Expected XML Tree and select
View > Checkpoint Summary to view the Checkpoint Summary in the bottom pane in the XML
Checkpoint Results window. The procedure for analyzing the checkpoint results does not change even
though the value was parameterized.
Using the Checkpoint Summary pane, you can compare the expected and actual values of the total
element.
See also "XML Checkpoint Results (UFT GUI Tests Only) " on page 85
User interface elements are described below (unlabeled elements are shown in angle brackets):
UI Description
Elements
Value x Indicates the ordinal position of the selected value within the Expected XML Tree or Actual XML Tree.
of y
<edit Displays the full value of the element or attribute in a multi-line window.
window>
<< Enables you to navigate backward through the element values in the XML Checkpoint Results window. Clicking this
Previous button displays the next value in the Expected XML Tree or Actual XML Tree.
Value
Next Enables you to navigate forward through the element values in the XML Checkpoint Results window. Clicking this
Value >> button displays the next value in the Expected XML Tree or Actual XML Tree.
l Data Table Names pane. Displays the XML output value settings—the structure of the XML and the
Data Table parameters (column names) you selected to output for Data Table output values.
l Output Values pane. Displays the actual XML tree—what the XML document or file actually looked
like and the actual values that were output during the run.
This window also displays:
l Additional Details pane. Displays results information for the selected item. (Available only if the
Output Value Summary option is selected.)
l Expected Attributes pane. Displays each attribute name and its expected value or output value
name. (Available only if the Attribute Details option is selected.)
l Actual Attributes pane. Displays the attribute name and the actual value of each attribute during
the run session. (Available only if the Attribute Details option is selected.)
To access In the Captured Data pane of the Run Results Viewer, click the View XML Output Value Results button.
See also "XML Output Value Results (UFT GUI Tests Only) "
UI Description
Elements
View Output Value Summary. Displays the Output Value Summary pane, which provides information regarding
the output value for the element, attribute, or value currently selected in the XML tree.
View Attribute Details. Displays the Expected Attributes and Actual Attributes panes containing the details of
the attribute’s output value for the selected element in the XML tree.
Find Next Output Value. Jumps directly to the next output value in the XML Tree.
Menu option: View > Find Next Output Value
UI Description
Elements
Find Previous Output Value. Jumps directly to the previous output value in the XML Tree.
Menu option: View > Find Previous Output Value
Find Next Error. Jumps directly to the next error in the XML Tree.
Menu option: View > Find Next Error
Find Previous Error. Jumps directly to the previous error in the XML Tree.
Menu option: View > Find Previous Error
Scroll Trees Simultaneously. Synchronizes the scrolling of the Data Table Names and Output Values trees.
If this option is selected, the Data Table Names and Output Values trees scroll simultaneously as you navigate
through either of the tree structures. If this option is not selected, you can scroll only one tree at a time.
Help Topics. Opens the help for the XML Output Value Results window.
Menu option: View > Help Topics
Tell us how: sw-doc@hp.com