The default is that the Test Results window opens at the end of a run. To change this behavior, check (or uncheck) View results when run session ends in the Run tab of Options window (Tools->Options).
2.
For a test that does not contain Data Table parameters, the Test Results window shows single test iteration.
On the contrary, if the test contains Data Table parameters, and the test settings are configured to run multiple iterations, the Test Results window displays details for each iteration of the test run. The results are grouped by the actions in the test.
The Run-Time Data Table is also shown in Test Results.
3.
The Test Results window displays all aspects of the run session and can include:
3a. A high-level results overview report (pass/fail status)
3b. The data used in all runs
3c. An expandable tree of the steps, specifying exactly where application failures occurred
3d. The exact locations in the test or component where failures occurred
3e. A still image of the state of your application at a particular step.
[I intentionally removed ‘r’ from “Denver” and made it “Denve” from the recorded script in order to make it fail]
For setting this go to Tools->Option and go to Run tab.
3f. A movie clip of the state of your application at a particular step or of the entire test or component
For setting this go to Tools->Option and go to Run tab.
3g. Detailed explanations of each step and checkpoint pass or failure, at each stage of the test or component
4
You can view the results of previous runs of the current test or component, and results of other tests or components.
Choose File-> Open from within the Test Results window.
To update the results list after you change the specified test or component path, click Refresh
5
You can filter the information displayed in the Test Results window. In the Test Results window go to View->Filters.
6
When you run your test or component, you can specify a different location to store the results, using the Results Location tab of the Run dialog box.
7
By default, result files for tests are stored in
For example C:\Program Files\HP\QuickTest Professional\Tests\Test7\Res1\Report
8
The Test Results window contains a graphic and text summary of the results of a run as well as details of each step in the run.
9
If the Test Results window is not already open choose Automation > Results.
10
You can view the results of an individual iteration, an action, or a step.
- Iterations, actions, and steps that contain checkpoints are marked Passed or Failed in the right part of the Test Results window and are identified by the icon
or 
in the tree pane. - Iterations, actions, and steps that ran successfully, but do not contain checkpoints, are marked Done in the right part of the Test Results window. (Not relevant for components)
- Steps that were not successful, but did not cause the test or component to stop running, are marked Warning in the right part of the Test Results window and are identified by the icon
or 
- A test, component, iteration, or action containing a step marked Warning may still be labeled Passed or Done.
The Test Results window can show results with up to 300 levels in the tree hierarchy. If you have results with more than 300 nested levels, you can view the entire report by manually opening the results.xml file.
12
You can use the Test Results Deletion Tool (Start > Programs > QuickTest Professional > Tools > Test Results Deletion Tool) to view a list of all the test results in a specific location in your file system or in a Quality Center project. You can then delete any test results that you no longer require.
13
You can print test results from the Test Results window. You can select the type of report you want to print, and you can also create and print a customized report. You can preview test results on screen before you print them.
14
You can instruct QuickTest to automatically submit a defect to a Quality Center project for each failed step in your test. You can also manually submit a defect for a specific step to Quality Center directly from within your QuickTest Test Results window. These options are only available when you are connected to a Quality Center project.
15
If the test was run from Quality Center, the name of the test set and the test instance are also shown.
Note: A test set is a group of tests selected to achieve specific testing goals. For example, you can create a test set that tests the user interface of the application or the application's performance under stress. You define test sets when working in Quality Center's test run mode.
Test instance: Specifies the instance number of the test in the business process test. For example, if the same test is included twice in the business process test, you can view the results of Test instance 1 and Test instance 2.
16
[For use in Expert View]
Reporter Object
The object used for sending information to the test results.
Filter Property
Retrieves or sets the current mode for displaying events in the Test Results. You can use this property to completely disable or enable reporting of steps following the statement, or you can indicate that you only want subsequent failed or failed and warning steps to be included in the report.
Reporter.Filter retrieves or sets the current mode for displaying events in the Test Results. You can use the Report.Filter method to determine which steps or types of steps are included in the Test Results. You can completely disable or enable reporting of steps following the statement, or you can indicate that you only want subsequent failed or failed and warning steps to be included in the report.
17
[For use in Expert View]
ResultsLocation Property: The path in which the run results will be stored.
18
The results of each QuickTest run session are saved in a single .xml file (called results.xml).
You can take test 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 QuickTest Test Results window, when displaying test results in your own customized results viewer, or when exporting the test results to an HTML file).
XSL provides you with the tools to describe exactly which test result information to display and exactly where and how to display, print or export it.
You may find it easier to modify the existing .xsl and .css files provided with QuickTest, instead of creating your own customized files from scratch. The files are located in
PShort.xsl. Specifies the content of the test 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.
PDetails.xsl. Specifies the content of the test 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.
PSelection.xsl. Specifies the content of the test results report printed, or exported to an HTML file, when you select the Selection option in the Print or Export to HTML File dialog boxes.
PResults.css. Specifies the appearance of the test results print preview. This file is referenced by all three .xsl files.