You are on page 1of 7

New Features added to QTP10.

Monitoring System Performance:
To all those who are eager to know about the memory being consumed, processors time
being used or the memory leaks by you AUT, here is an interesting features that not only
lets you know all these but also make you feel like a performance tester
It is Local System Monitor.
This feature was not in the earlier versions of QTP, using this feature we can monitor
system counters like the memory being used, handle counts, GDI objects, processor
This feature even provides the user with the ability to define upper limits to the system
counters (memory, handle counts, % processor time) and at any point of time in any step
if that upper limit exceeds, test run will fail.
Here is how we can access Local System Monitoring feature
File > Settings > Local System Monitor

Figure1: Accessing Local System Monitor from Test Settings Dialog

Additionally, the results generated for the counters are available in test results window. A
separate tab - System Monitor was provided in the test result files to view the
performance counters.

Figure2: Separate tab - System Monitor to view the system performance counters from
the Test Results Window
Save Test with Resource Files:
Earlier versions of QTP10.0 allow users to save only the test but not the resources
associated with it.
With inclusion of option - Save Test with Resource Files users can now save the test
along with resources associated with it.
The resources associated could be anything like associated function libraries, associated
shared object repositories, associated recovery scenarios etc.
This feature is accessible from File > Save Test with Resources

Call Actions Dynamically During the Test Run

Have you ever tried to insert a call to an external action (an action form other tests)
dynamically, I mean during test run?
If you have tried this on earlier versions of QTP10.0, you must have no idea how to do it,
as they do not provide user the ability to load and call an action dynamically.
QTP10.0 came with this interesting and useful feature LoadAndRunAction statement.
Generally, when you insert a call to an external action, the action call becomes part of the
test, and the called action is loaded each time you open the test.
However, there are situations where we do not want the action to be loaded each time we
open the test but we would like to load and run the action dynamically based on some
condition, this is where the above statement LoadAndRunAction is used.
Here is the syntax:
LoadAndRunAction (TestPath, ActionName, [Iteration], [Parameters])
Improvements to Test Results:
Jump to Step: If you want to know the line in which failure is occurring, just go to the
test results window, right click on the failed step and select Jump to Step in Quickest, it
will take the user to the line in the script where the test it is failing.
Export Test Results to Microsoft Word or PDF Formats: In addition to HTML
format, you can now select to save your QuickTest run results in Microsoft Word or PDF
formats. You can then share this information, together with any local system monitoring
data, with your developers and performance testing teams.

Figure3: Export Report Dialog box

IntelliSense and Auto-Complete Functionality:

This feature made my life easy a bit, now it extends its intellisense and auto complete
mechanism to variables as well as COM component objects up to any hierarchy and
level. What you need to do is, type the first letter of the variable or the object and hit
Control-Space, qtp will auto complete it or will provide you with the list of variables or

Figure4: Shows intellisense for an object created in the test

QuickTest now provides full IntelliSense for the following types of objects:

Objects created by a step or function (for example, by calling the CreateObject

Variables to which an object is assigned
Reserved objects
COM objects

IntelliSense sentence completion now provides lists of local variables.

Multi-level IntelliSense information is also available for all reserved objects, COM
objects, and objects created using the CreateObject method.

Figure5: Intellisense feature lists all the methods of fso object created

Improved Debugger Pane Design and Functionality

The Debug Viewer pane has a new look, including icons to help you identify the type of
information displayed.
The Watch tab and Variable tab now display the types of expressions or variables, in
addition to their names and values.
The Command tab now displays the command history (in read-only format) in addition to
the command line, enabling you to view previously run commands and select commands
to reuse.
In addition, a right-click context menu in the Command tab enables you to:
Copy from the command history and edit the command line using the clipboard.
Custom Toolbars:
You can use the new Customize Dialog box (Tools > Customize) to customize the
appearance of existing menus and toolbars, and to create your own user-defined menus,
toolbar buttons, and shortcuts.
You can also add new commands to the Quickest Tools menu so that you can launch an
application directly from the menu. For example, you can use this option to create a
shortcut to the application you want to test or to an automation script.

Creating and Editing Actions in Automation scripts:

Do you want to create actions and modify actions programmatically?
Quick Test Professional now extends its Automation Object Model in a way that users
will now have the ability to create and modify actions programmatically in scripts.

Figure6: Automation Object Model, the ability to create a new action in the script using
Action object

Tasks and Comments

Another addition is the To-Do pane, you can see this pane from View>To Do. It contains
two tabs - Tasks and Comments.
Tasks are designed such that a user can create and manage the ongoing project tasks and
can save them with the current test.
Comments work pretty much similarly but, seem to be more interesting, useful and
advanced than Tasks.

Whenever we write any comment starting with either To Do, TO DO:, to-do or
with any other combination of To-do in the test (either in any action or in function
library), the comments editor will pick that up dynamically and shows it in the To-do
Comments tab.
Double clicking on the comment in the Comments tab will jump to the line in the test
where comment is appearing.
Look and Feel
The QuickTest Options and Settings dialog boxes have changed from their former tabbased design to a more easily navigable tree-based structure. The tree contains only the
options relevant for the add-ins that are currently loaded.

Figure7: New look of Test Settings dialog box