Thursday, 28 April 2011

Highlight the text on page using the QTP

Hi All,
Someone asked me how to highlight the text on page using the QTP. So here I have created a function that will find the text on page and highlight it if finds else not.

REM  ——  Set page object     ———
set objpage = Browser("BrowserName").Page("Pagename")

call   HighLightTextPresentOnPage(objpage ,"News" )

Function HighLightTextPresentOnPage(byval objpage , byval Textvalue )

On error resume next

REM ——- Create child object description
Set childobj = Description.Create()
childobj("html tag").value=".*[A-Za-z0-9].*"
childobj("outertext").value =Textvalue

REM  ———-Create ALL child object 
set allobj = objpage.ChildObjects(childobj)

 REM here highlight method we will use that is in build in QTP for object
For i=1 to allobj.count-1
           If allobj.count > 0 then
              HighLightTextPresentOnPage = true
              HighLightTextPresentOnPage = false
           End if

             On Error GoTo 0
End Function

Monday, 18 April 2011

Close All Browser QTP

‘ This function Close All open Browser

REM *************************************************************************
REM this function close All open browser
Public Function   fn_CloseAllBrowser()

    While Browser(“CreationTime:=0″).Exist



End Function

REM *************************************************************************
Rem another way to close browser here  this function terminate application ‘process
rem like internet explorer exe will close from system process
dim sApplicationExe
sApplicationExe = “iexplore.exe”
Rem call function to close application process
call fn_CloseApplication( sApplicationExe)
REM This function kill the given process exe  through task manager
Public Function  fn_CloseApplication( byval sApplicationExe)

   Dim strComputer

   Dim objWMIService

   Dim colProcesses

  Dim objProcess

  strComputer = “.”

  Set objWMIService = GetObject(“winmgmts:\\” & strComputer & “\root\cimv2″)
  Set colProcesses = objWMIService.ExecQuery (“Select * from Win32_Process Where Name = ‘”&sApplicationExe&”‘”)

  For Each objProcess in colProcesses



  Set objWMIService = Nothing

  Set colProcesses=Nothing

End Function

REM through this function you can close any application process

QTP is not recording the web application

Hi All,
I faced the problem when I installed the QTP in vista.QTP  was not recording any web application then i tried to check with OBJECT SPY how its identify the web object Object Spy identify the each web object as a winobject. Then i found the solution to solve this problem this was because vista User control . In Vista you need to off USER CONTROL option after that QTP works fine and records the web application. To off the USER CONTROL option follow the following steps:
Click Start  >Control Panel>User Accounts and Family Safety>User Accounts
and uncheck  the Turn User Account Control On or OFF option

QTP not recording web application in VISTA

Here is the sequence of tries
1. Try Opening QTP-11 as Administrator mode
Right click QTP short cut>>Run As Administrator Mode
2. If above does not work then go to control panel and set User account setting to low level ie. not to notify and then repeat step-1
3. If both 1&2 does not work then go to IE>Tools>Internet Options>Advanced>Browsing>Enable Third Party Browser extension ( usually in IE8 by default it will be enabled) and then repeat step-1/2
4. If all above 3- does not work then you may think of running IE as 32-bit ( but i din;t understood how one can run IE8 32-bit browser on 64-bit machine. ( I have not tried this solution…/ And i suggest not to try step-4.)

Sunday, 17 April 2011

QTP 11 Installation Issues/Errors

Hi All ,Most of time, we are facing the problem while running the QTP OR installation but some times these problems are unknown to us because we did not read the installation procedure or limitations or known issues, So please have a look :-

Notes and Limitations

This section includes the following:
  • Before You Install
  • Supplemental Information

Before You Install

This section includes information that is important for you to know before you install QuickTest.
  • You cannot install QuickTest when a McAfee Anti-Virus application is running.
  • Workaround: Disable the antivirus application during the QuickTest installation process.
  • QuickTest Professional supports the Sentinel RMS License Manager version 8.3.0 as its concurrent license server. Earlier versions of the concurrent license server are not supported.
  • QuickTest does not support Windows user names with non-English letters. If you log in to Windows using a user name (with administrative privileges) that contains non-English characters and then install QuickTest, the installation may complete successfully, but you may not be able to open QuickTest or it may not behave correctly.
  • The path in which installation files for QuickTest are located, and the path in which QuickTest is installed, can contain only English characters.
  • When upgrading to QuickTest 11.00 from a QuickTest 9.5 or 10.00 installation on which a Language Pack (localized version of QuickTest) was previously installed, you may get an error message when opening QuickTest after the upgrade.
  • Workaround: Repair the installation:
    1. In the Control Panel, select Add/Remove Programs and select the HP QuickTest Professional entry.
    2. Click the Change button.
    3. In the installation wizard that opens, choose the Repair option and follow the on-screen instructions.
  • If you install QuickTest 11.00 while the QTPNET_00015 patch (a QuickTest 10.00 patch) is installed on your computer, QuickTest may behave unexpectedly.
  • Workaround:
    1. Open the Add/Remove Programs dialog box from the Control Panel.
    2. Display the installed patches by selecting the Show updates check box (or click the View Installed Updates button, depending on your operating system version.)
    3. Locate HP QuickTest Professional in the list and check whether QTPNET_00015 for HP QuickTest Professional 10.00 QFE is listed as an installed update.
    4. If it is installed, click Remove to uninstall this patch before you install QuickTest 11.00.
  • If you want to work with .NET 4.0, it is best to install it before you install QuickTest. If you install .NET 4.0 after you install QuickTest, you must manually register two .NET DLLs as follows:
  • In <QuickTest installation folder>\GlobalAssemblyCache\Net4, execute the following commands:
    • ..\..\bin\GACRegUtil4x86.exe -i Mercury.QTP.Agent.dll
    • ..\..\bin\GACRegUtil4x86.exe -i Mercury.QTP.WpfAgent.dll
  • In Windows XP and Windows 2003, if you install the Oracle Add-in, the Windows Remote Shell Service (rshsvc.exe) may fail and display an error message every time you restart the computer. This occurs only if the Remote Shell Service is configured to run automatically.

Supplemental Information

Use the information in this section as a supplement to the product documentation.

Additional troubleshooting information, guidelines, and feature-specific limitations are described in the relevant locations of the installation and product documentation. Make sure you are aware of those issues when working with the relevant features.

This section includes the following:


  • When you install a new QuickTest 11.00 installation and you specify a single concurrent license server in the License Wizard, QuickTest now automatically specifies the server in an LSFORCEHOST environment variable, to optimize performance. However if you perform an upgrade from QuickTest 10.00, and you already had an LSHOST variable defined, the upgrade installation does not change the setting to LSFORCEHOST.
  • Workaround: If desired, set the LSFORCEHOST variable manually, as described in the HP Functional Testing Concurrent License Server Installation Guide.
  • If you manually set an LSHOST environment variable to a particular server (or upgrade from a previous version of QuickTest where the LSHOST variable was set), QuickTest sometimes gets its license from another server, even when the specified server has the required licenses available.
  • Workaround: To ensure that a specific server will be used, specify an LSFORCEHOST environment variable instead.

Operating Systems

If you work with QuickTest on a Windows 7 operating system with User Account Control (UAC) turned on, and you open a test from a protected location (such as Program Files), it is opened in read-only mode and a message is displayed that you do not have permissions to open it in read-write mode.


  • When you save a test using the Save Test with Resources option, it also saves any tests containing called external actions. However, to preserve space, these called tests contain only the called actions, and not all of the actions from the original test. Therefore, you cannot open these called tests in QuickTest from the local copy.
  • Workaround: If you need to have full access to the called tests as well as the main test that you save using the Save Test with Resources option, then you must manually save all required tests locally and then manually edit all references to the relevant actions from the main test to the actions it calls.

Web Add-in

  • The If Handler option in the Web Event Recording Configuration dialog box works on Mozilla Firefox browsers only if the handler is assigned as an attribute (for example, <A onclick = “some code”/>) and not if it is assigned as a property (for example, aObj.onclick = function() {some code})

Silverlight Add-in

  • When Silverlight applications are opened in two tabs sequentially (without QuickTest performing any operations on the first one before the second opens), QTP will use a custom server to support controls only in the first application with which you interact. The same is true when two tabs are refreshed sequentially.
  • Workaround: Perform an operation (for example, use the Object Spy) with the first tab opened/refreshed before opening/refreshing the second one.
  • If a Web page contains a Silverlight application that is windowless and is scrolled out of view when the page opens the first time, QuickTest will not be able to make this application visible. (For example, in this scenario, QuickTest will not be able to perform an SlvWindow.MakeVisible step).

Quality Center and Business Process Testing

  • When comparing two baselines, if the only change in a resource is its association to a test or component, the Asset Comparison Tool does not indicate any change in the resource even though HP ALM or Quality Center may indicate that the resource is Modified.
  • If an HP ALM or Quality Center user manually changes the status of a test instance run, HP ALM/Quality Center creates something called fast run results to record the change of the test status. The fast run results are not valid QuickTest run results files. However, when you try to select results to open or delete in the Run Results Viewer or Run Results Deletion tool, the fast run results are available in the list.
  • After you run a component locally in QuickTest, you cannot use the Jump to Step in QuickTest option from the Run Results Viewer.
  • You cannot perform a remote execution of a business process test on a Windows 2008 R2 QuickTest computer.


  • The QuickTest Help Index tab contains only reference items, such as objects, methods, properties, and functions. It does not contain any entries from the user guides.
  • To search for information from all the documents in the QuickTest Documentation Library, use the Search tab.
  • On some operating systems or after installing certain Windows service packs or updates, you may not be able to view the content of some Help files.
  • Workaround:
    1. Right-click the CHM file in <QTP installation folder)\help, and click Properties.
    2. In the dialog box that opens, click Unblock.
    3. For details, see http://support.microsoft.com/kb/902225


  • If you are working with a QuickTest User Interface Pack, install it before running QuickTest for the first time, if possible.
  • If you install a QuickTest User Interface Pack after running QuickTest, the following items may remain in English after installing the User Interface Pack:
    • Menus and toolbars in the Object Repository window (in QuickTest or in the Object Repository Manager)
    • The Find dialog box in the Expert View
    • Workaround: Close QuickTest and delete the folder: %APPDATA%\HP\QuickTest Professional(For example, C:\Documents and Settings\<username>\Application Data\HP\QuickTest Professional).
  • When working on an operating system using a Spanish locale, you may get an assertion error message at the beginning of the QuickTest installation.
  • Workaround: Modify the sLanguage registry key value as follows:
    1. In the Start > Run dialog box, type: regedit.
    2. Go to the registry path: HKEY_CURRENT_USER\Control Panel\International
    3. Change the sLanguage value from ES to ESN
    4. If the above steps do not solve the problem, restart your computer and try again.
    5. Run the QuickTest installation again.
  • Selecting the View Sample Snapshot option in the QuickTest Asset Comparison Tool opens a window containing a sample image of the selected element in QuickTest. The image displays the English user interface.
  • The Add-in Extensibility SDKs are not localized.

Visual Relation Identifiers QTP 11

HI All,
In QTP 11 has added one more advanced feature Visual Relation Identifiers that will help to identify the objects with relation to other objects
You can now use visual relation identifiers to identify application objects based on other objects that are always near them.

This enables you to create a more reliable identification definition for test objects that are otherwise difficult to differentiate, and to ensure that the identification remains reliable even if the user interface design changes.
When testing applications with multiple identical objects, QuickTest assigns an ordinal identifier to each test object. This may lead to unreliable object identification. However, it may not (immediately) result in a failed step.
A visual relation identifier is a set of definitions that enable you to identify the object in the application according its neighboring objects in the application. You can select neighboring objects that will maintain the same relative location to your object, even if the user interface design changes. This enables you to help QuickTest identify similar objects much as a human tester would, and helps in creating more stable object repositories that can withstand predictable changes to the application’s user interface.
How Visual Relation Identifiers Work
Suppose that you are shown a photograph of a classroom, and are then asked to note identical twins sitting at different desks, and to be able to identify each twin successfully when shown different photographs of the same classroom at a later time.
You are told that one differentiating characteristic is that one twin always carries a blue school bag, and that the other twin always carries a red school bag. You are then also told that each twin has an assigned desk partners, which means that even if the twins sit at a different desk in other photographs, they always sit next to their assigned lab partners.
Therefore, the solution is to identify the twin with the blue school bag in this manner: <twin> is nearest to <twin’s desk partner>, and carries <blue school bag>.
QuickTest uses visual relation identifiers in a similar manner, by examining related objects in the application that you are testing. However, because QuickTest compares the related objects based on their relation to the test object to identify as a set of definitions, you would state that <twin’s desk partner> is nearest to <twin>, and not vice versa.
Watch the Visual Relation Identifiers movie to see a demonstration of how this functionality can be used in an end-to-end process.

NOTE : — > QuickTest uses visual relation identifiers only when one or more objects match the test object’s description properties during the identification process. If no objects in the application match the test object’s description properties, then the visual relation identifier you defined is ignored, and QuickTest continues to Smart Identification (if defined for that test object class).

Wednesday, 13 April 2011

Use Regular Expressions QTP

Some Time QTP not recognize the application object during seond run it Or it run first time successfully then QTP give an error cannot identified the application Window object properties does not match with the test object. there might be a case of window name /object name change each time. Here we required the use of regular expression See the example
Regular Expression
Regular Expression
During Recording of  Flight application QTP record the flight application it identified the Fax order window name property like this
It Text Property is Fax order 11
If you run this script Again it will give an error because Fax order Window name will be
Fax order 12
Cannot identify the object “Fax Order No. 11″ (of class Dialog). Verify that this object’s properties match an object currently displayed in your application.
Line (1): “Window(“Flight Reservation”).Dialog(“Fax Order No. 11″).Activate”.
Now we change text property to regular expression open Object properties from object repository  .Click on text property value cell
Check regular expression check box A message will appear click NO. Now change Text box value according to Regular expreesion.
Fax Order No. 11 to Fax Order No.*
Here each time only last part getting changed here we use .* as regular expression means it will check only Fax order No text not whole string
Same case can we apply for different object properties if they getting changed
A regular expression is a string that describes or matches a set of strings. It is often called a pattern as it describes set of strings.
Given underneath is one of the most widely used and ever confused BackLash character. The remaining expressions are serialized below that.
Using the Backslash Character

A backslash (\) instructs QuickTest to treat the next character as a literal character, if it is otherwise a special character. The backslash (\) can also instruct QuickTest to recognize certain ordinary characters as special characters. For example, QuickTest recognizes \n as the special newline character.

For example:

w matches the character w

\w is a special character that matches any word character including underscore

For example, in QTP, while entering the URL of a website,


The period would be mistaken as an indication of a regular expression. To indicate that the period is not part of a regular expression, you would enter it as follows:

mercurytours\.mercuryinteractive\.com Note: If a backslash character is used before a character that has no special meaning, the backslash is ignored. For example, \z matches z.
Expressions & Explanation

Special characters and sequences are used in writing patterns for regular expressions. The following describes the characters and sequences that can be used\

Marks the next character as either a special character or a literal. For example, “n” matches the character “n”. “\n” matches a newline character. The sequence “\\” matches “\” and “\(” matches “(“.

Matches the beginning of input.

Matches the end of input.

Matches the preceding character zero or more times. For example, “zo*” matches either “z” or “zoo”.

Matches the preceding character one or more times. For example, “zo+” matches “zoo” but not “z”.

Matches the preceding character zero or one time. For example, “a?ve?” matches the “ve” in “never”.

Matches any single character except a newline character.

Matches pattern and remembers the match. The matched substring can be retrieved from the resulting Matches collection, using Item [0]…[n]. To match parentheses characters ( ), use “\(” or “\)”.

Matches either x or y. For example, “zwood” matches “z” or “wood”. “(zw)oo” matches “zoo” or “wood”.

n is a nonnegative integer. Matches exactly n times. For example, “o{2}” does not match the “o” in “Bob,” but matches the first two o’s in “foooood”.

n is a nonnegative integer. Matches at least n times. For example, “o{2,}” does not match the “o” in “Bob” and matches all the o’s in “foooood.” “o{1,}” is equivalent to “o+”. “o{0,}” is equivalent to “o*”.

m and n are nonnegative integers. Matches at least n and at most m times. For example, “o{1,3}” matches the first three o’s in “fooooood.” “o{0,1}” is equivalent to “o?”.

A character set. Matches any one of the enclosed characters. For example, “[abc]” matches the “a” in “plain”.

A negative character set. Matches any character not enclosed. For example, “[^abc]” matches the “p” in “plain”.

A range of characters. Matches any character in the specified range. For example, “[a-z]” matches any lowercase alphabetic character in the range “a” through “z”.

A negative range characters. Matches any character not in the specified range. For example, “[m-z]” matches any character not in the range “m” through “z”.

Matches a word boundary, that is, the position between a word and a space. For example, “er\b” matches the “er” in “never” but not the “er” in “verb”.

Matches a non-word boundary. “ea*r\B” matches the “ear” in “never early”.

Matches a digit character. Equivalent to [0-9].

Matches a non-digit character. Equivalent to [^0-9].

Matches a form-feed character.

Matches a newline character.

Matches a carriage return character.

Matches any white space including space, tab, form-feed, etc. Equivalent to “[ \f\n\r\t\v]“.

Matches any nonwhite space character. Equivalent to “[^ \f\n\r\t\v]“.

Matches a tab character.

Matches a vertical tab character.

Matches any word character including underscore. Equivalent to “[A-Za-z0-9_]“.

Matches any non-word character. Equivalent to “[^A-Za-z0-9_]“.

Matches num, where num is a positive integer. A reference back to remembered matches. For example, “(.)\1″ matches two consecutive identical characters.

Matches n, where n is an octal escape value. Octal escape values must be 1, 2, or 3 digits long. For example, “\11″ and “11″ both match a tab character. “011″ is the equivalent of “01″ & “1″. Octal escape values must not exceed 256. If they do, only the first two digits comprise the expression. Allows ASCII codes to be used in regular expressions.

Matches n, where n is a hexadecimal escape value. Hexadecimal escape values must be exactly two digits long. For example, “\x41″ matches “A”. “\x041″ is equivalent to “\x04″ & “1″. Allows ASCII codes to be used in regular expressions

Use Send Key Method QTP VB

Hi All,
Some time we requre keyboard event in Automation so we can use Send key method

rem **********************************************
rem create shell object
set WshShell = CreateObject(“WScript.Shell”)
SystemUtil.Run “C:\Program Files\HP\QuickTest xcxProfessional\samples\flight\app\flight4a.exe”,”C:\Program Files\HP\QuickTest Professional\samples\flight\app\flight4a.exe”,”",”"
rem first click in the text box then use send key method
Dialog(“text:=Login”).WinEdit(“attached text:=Agent Name:”).Click
rem enter rajiv in agent name text box
WshShell.SendKeys “rajiv”
rem click Password Edit box
Dialog(“text:=Login”).WinEdit(“attached text:=Password:”).Click
rem enter check in Password text box
WshShell.SendKeys “check “
rem press escape using send key method
WshShell.SendKeys “{ESC}”
WshShell.SendKeys “{ESC}”
rem **********************************************************
Use the SendKeys method to send keystrokes to applications that have no automation interface. Most keyboard characters are represented by a single keystroke. Some keyboard characters are made up of combinations of keystrokes (CTRL+SHIFT+HOME, for example). To send a single keyboard character, send the character itself as the string argument. For example, to send the letter x, send the string argument “x”.
Note To send a space, send the string ” “.
You can use SendKeys to send more than one keystroke at a time. To do this, create a compound string argument that represents a sequence of keystrokes by appending each keystroke in the sequence to the one before it. For example, to send the keystrokes a, b, and c, you would send the string argument “abc”. The SendKeys method uses some characters as modifiers of characters (instead of using their face-values). This set of special characters consists of parentheses, brackets, braces, and the:
  • plus sign       ”+”,
  • caret             ”^”,
  • percent sign “%”,
  • and tilde       ”~”
Send these characters by enclosing them within braces “{}”. For example, to send the plus sign, send the string argument “{+}”. Brackets “[ ]” have no special meaning when used with SendKeys, but you must enclose them within braces to accommodate applications that do give them a special meaning (for dynamic data exchange (DDE) for example).
  • To send bracket characters, send the string argument “{[}" for the left bracket and "{]}” for the right one.
  • To send brace characters, send the string argument “{{}” for the left brace and “{}}” for the right one.
Some keystrokes do not generate characters (such as ENTER and TAB). Some keystrokes represent actions (such as BACKSPACE and BREAK). To send these kinds of keystrokes, send the arguments shown in the following table:
To send keyboard characters that are comprised of a regular keystroke in combination with a SHIFT, CTRL, or ALT, create a compound string argument that represents the keystroke combination. You do this by preceding the regular keystroke with one or more of the following special characters:
KeySpecial Character
Note When used this way, these special characters are not enclosed within a set of braces.
To specify that a combination of SHIFT, CTRL, and ALT should be held down while several other keys are pressed, create a compound string argument with the modified keystrokes enclosed in parentheses. For example, to send the keystroke combination that specifies that the SHIFT key is held down while:
  • e and c are pressed, send the string argument “+(ec)”.
  • e is pressed, followed by a lone c (with no SHIFT), send the string argument “+ec”.
You can use the SendKeys method to send a pattern of keystrokes that consists of a single keystroke pressed several times in a row. To do this, create a compound string argument that specifies the keystroke you want to repeat, followed by the number of times you want it repeated. You do this using a compound string argument of the form {keystroke number}. For example, to send the letter “x” ten times, you would send the string argument “{x 10}”. Be sure to include a space between keystroke and number.
Note The only keystroke pattern you can send is the kind that is comprised of a single keystroke pressed several times. For example, you can send “x” ten times, but you cannot do the same for “Ctrl+x”.
Note You cannot send the PRINT SCREEN key {PRTSC} to an application.

QTP 11.00 New Features

QuickTest 11.00 now offers the following new features.

Manage Your Test Data

Quality Center (HP ALM) test configuration functionality enables you to determine at runtime which data sets to use for your tests.
ALM test configurations enable you to:
  • Unbind your data from your tests
  • Share common data sources across different tests
  • Filter your data to fit your testing needs
  • Increase requirements traceability
You store the data for your tests in the Quality Center Test Resources module in the form of data table resource files.
You can then define multiple test configurations for a test in the Test Plan module. When working with data-driven QuickTest tests in HP ALM, each configuration is a QuickTest test that is set to run with a selected data resource file and optional data filter settings.
One or more specific configurations of the test can be included in a Test Set to cover different parts of a requirement or to cover multiple requirements.
By using Quality Center test configurations, you can create more generic tests and reuse them by associating a different set of data with each. You can also reuse your data by associating the same data table file with multiple tests.

Test Your GUI and UI-Less Application Functionality in One Test

The new QuickTest-Service Test integration enables you to test across the GUI and non-GUI layers of your application.
You can use QuickTest steps to start testing the GUI elements in your application, then call a Service Test test to validate service communications (standard Web Services, non-SOAP Web Services, such as REST, etc.), and then step back into your QuickTest GUI testing, all in a single test run.
The results of the QuickTest and Service Test steps are displayed in a unified report in the new Run Results Viewer.

New Run Results Viewer

The new Run Results Viewer provides an Executive Summary page with summary data, pie charts and statistics for both the current and previous runs, a quick link to the previous run results, and more.
The Run Results Viewer displays the results of your run session in a set of panes that you can show, hide, move, dock, and otherwise customize to your needs.
You can install the Run Results Viewer as a standalone installation. This enables you to share the results of your tests with business analysts and developers who do not work with QuickTest.

Help QuickTest Identify Your Objects as a Manual Tester Would – VISUALLY

You can now use visual relation identifiers to identify application objects based on other objects that are always near them.
This enables you to create a more reliable identification definition for test objects that are otherwise difficult to differentiate, and to ensure that the identification remains reliable even if the user interface design changes.
The Visual Relation Identifier Dialog Box provides the interface and tools to help you create and verify your visual relation identifier definitions.

Collaborate with Developers to Pinpoint Defects Using Log Tracking

In today’s more agile development environment, it is more important than ever for QA engineers and developers to work together throughout the development and release process.
QuickTest’s new Log Tracking functionality helps you work with developers to pinpoint the root causes of unexpected behavior in your application.
When you enable log tracking, QuickTest receives the Java or .NET log framework messages from your application and embeds them in the run results.
You can click a log message in the results to jump to the relevant step in the run results tree, or you can click a step in the run results tree and view the log message that was generated at the time that the selected step ran. You can also specify that a log message of a particular level (or higher) will fail your test.
After you view the results, you can print or export 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 desktop.

Out-of-the-Box Support for Web 2.0 Toolkit Applications

QuickTest 11.00 provides Web Add-in Extensibility-based add-ins for ASP .NET Ajax, GWT, Yahoo UI, and Dojo Web 2.0 toolkits.
You can use these add-ins just as you would any other add-in. You can also use Web Add-in Extensibility or Extensibility Accelerator to customize the provided support to match your needs.
You install these add-ins by running the Web 2.0 Toolkit Support Setup from the Add-in Extensibility and Web 2.0 Toolkits option in the QuickTest Professional setup window.
The operations supported for each Web 2.0 test object class are a combination of custom operations developed for that test object class and operations directly inherited from the corresponding (base) Web Add-in test object class.

New Web Testing Capabilities

Many new testing capabilities are now available for working with Web-Based objects.
  • Firefox Testing. You can now record steps on Mozilla Firefox and use the .Object property to access the Firefox DOM.
  • XPath, CSS, Identifiers. You can add the XPath or CSS identifier properties to instruct QuickTest to identify a Web object in your application based on its XPath location or CSS definition.
  • Event Identifiers. You can also now use the attribute/* notation in the test object description to identify a Web-based object based on an event associated with that object. For example, you can add attribute/onClick as a property in a WebButton test object description to identify a button that is associated with the onClick event.
  • Embed or Run JavaScripts in Your Web Pages. You can use the new EmbedScript/EmbedScriptFromFile and RunScript/RunScriptFromFile functions to embed JavaScripts in all loaded browser pages and frames or to run JavaScripts in specific pages. Use these scripts to perform operations on, or retrieve data from, the browser pages in your application.

Automatically Parameterize Steps

You can instruct QuickTest to automatically parameterize the steps in your test’s actions at the end of a recording session.
This enables you to create actions that can be used for a variety of different purposes or scenarios by referencing different sets of data.
You activate this option by selecting the Automatically parameterize steps option in the General tab of the Options dialog box. You can set the option to use Global Data Table Parameters or Test Parameters.
When you stop a recording session while this option is selected, QuickTest replaces the constant values in the test object operation arguments of your steps with either Data Table parameters or action parameters, based on your selection in the Options dialog box.
QuickTest performs this automatic parameterization for all relevant steps in any action in your test, in which you recorded one or more steps during that recording session.
If you work with HP ALM, and you select the Global Data Table Parameters option, you can map the generated parameters to the column names of a data resource and then use different configurations in your test sets.
If you work with SAP eCATT and you select the Test Parameters option, you can then supply the values for the test parameters from eCATT.

New Silverlight Add-in

You can use the new Silverlight Add-in to test objects in Silverlight 2 and Silverlight 3 applications.
After you install the Silverlight Add-in, it is displayed in the Add-in Manager as a child add-in under the WPF Add-in.

Extend WPF and Silverlight Support

The WPF and Silverlight Add-in Extensibility SDK enables you to develop support for testing third-party and custom WPF and Silverlight controls that are not supported out-of-the-box by the relevant QuickTest add-ins.
You install the WPF and Silverlight Add-in Extensibility SDK from the Add-in Extensibility and Web 2.0 Toolkits option in the QuickTest Professional setup window.

Use Extensibility Accelerator for Web Add-in Extensibility Development

The new Extensibility Accelerator for Functional Testing is a Visual Studio-like IDE that facilitates the design, development, and deployment of Web Add-in Extensibility support.
It provides a user interface and special tools that help you define new test object classes, map those test object classes to the controls in your application, and teach QuickTest how to identify the controls, perform operations on the controls and retrieve their properties.
You install the Extensibility Accelerator from the Add-in Extensibility and Web 2.0 Toolkits option in the QuickTest Professional setup window.

It’s Easier Than Ever to Insert Regular Expressions

The Smart Regular Expression list provides syntax hints that make it easier than ever to insert regular expressions into your test steps. It also enables you to access the Regular Expression Evaluator, which lets you test regular expressions to make sure they suit your needs.

Load Function Libraries at Run Time

The new LoadFunctionLibrary statement lets you load a function library when a step runs instead of at the beginning of a run session. This means, for example, that you can define conditional steps that use functions from various function libraries, but load only the required function libraries during a run session.

Avoid Downtime Due to License Server Failures

With redundant license servers you create failover, so that if your main license server fails, your remaining servers maintain availability of your licenses without causing any downtime or loss of licenses for users.
The redundant license server feature is especially useful for enterprise customers
who have a large network installation and want to maintain license server backup.

Improved Documentation Structure Helps You Find the Information You Need

When you open the QuickTest Professional Help, you can now access the entire Documentation Library from one central point, the Home page. It provides links to all available guides in each available format, including PDF files.
The HP QuickTest Professional User Guide and the HP QuickTest Professional for Business Process Testing User Guide are now organized into topic types: Concepts, Tasks, and References. Use each topic type to access specific information about a feature or product area.
For example, you can use the Tasks topic type to learn the overall workflow of a feature to help you accomplish your goals, or you can use the Reference topic type to look up a specific user interface element, such as a window, dialog box, or page.

Connect QC through API using VB script

Hi All,

Here I am mentioning the script that will connect to Quality Center. For this,your system must have QC api dll/QC client installed.

REM Define the Domain name

DomainName =”DEFAULT”

REM ‘Define the ProjectName

ProjectName =”Automation”

REM ‘ login username

UserName =”Rajeev Nandwani”

REM ‘ login password

Password =”RNSystem00″

REM ‘ Server name with Port

ServerName =”QAserver:8080″

Rem Create QC Connection Object

Set objTDConnection = CreateObject(“TDApiOle80.TDConnection.1″)

Rem Connect with server

QCServerName =”http://”& ServerName &”/qcbin”

objTDConnection.InitConnectionEx QCServerName

Rem Connect with Project

objTDConnection.ConnectProjectEx DomainName, ProjectName, UserName, Password

Rem Check login Success or not

If objTDConnection.loggedin Then

msgbox “Connect successfully “


msgbox “not connect with Quality Center Check username /Password/Domain name /Project Name “

End If

Set objTDConnection = nothing

QTP 11 New Object Spy Functionality

Hi All,

In QTP 11 Object Spy has been improved now with following features:

  • Add an object to a repository
  • Highlight an object in your application
  • Copy/paste object properties
    • Add an object to a repository. You can now add an object to the object repository directly from the Object Spy.
    • Highlight an object in your application. When you select a test object in the Object Spy Object hierarchy tree, you can then select to highlight the object in your application that corresponds to that test object.
    • Copy/paste object properties. You can copy the identification properties and values of a selected test object in the Object Spy and paste the details into any document. The details are formatted in programmatic description syntax. This option is especially useful if you want to compare the properties and values of two objects in your application or when creating programmatic descriptions.
Additionally, the Object Spy has a new, cleaner look and feel:
QTP 11 New Object Spy
QTP 11 New Object Spy

Which one is right ?