• QTP 11: How to Enable Enhanced Debugging Features

    Posted on March 26, 2013 by Admin

    QTP 11 (and versions 9-10) installs Microsoft Script Debugger to provide the debugging features in QuickTest Pro scripts. Without the debugging engine, all of the QTP debug features are unavailable. Microsoft Script Debugger ships with an archaic version (7.10.3077) of Process Debug Manager (PDM).

    Out of the box, QTP provides limited VBScript debugging capabilities. An automation engineer does not have the ability to view the properties/methods of variables/objects in their full extent. Objects, like Object Repository obje Read Entire Entry

  • QuickTest Pro: Working with the Windows Clipboard (Clear, Copy and Paste Text)

    Posted on July 10, 2012 by Admin

    QuickTest Pro can interface directly with the Windows OS clipboard during replay using the VBScript “Mercury.Clipboard” object built in to QTP. This object can be used to validate clipboard data if the AUT programmatically manipulates the clipboard (and your test case requires validation of this functionality).
    Some of the more common methods supported in the “Mercury.Clipboard” object include:

    Clear – clear the clipboard contents
    SetText – write text to the clipboard
    GetText – retrieve text from the Read Entire Entry

  • Open Multiple Windows System Files With One Click

    Posted on July 5, 2012 by Admin


    1. You are on a windows platform.
    2. You have Windows Scripting (WSH) enabled.
    3. You have no security issues running VBS scripts.

    The following code will pull up several system files in notepad all in one place. Save this code into a text file and then rename the extension to .vbs for it to become executable. Modify it to take out or add more by changing what is in the array. For example, taking out everything except the hosts file from the array will mean only the hosts file will be opened in notepad:
    Set Sh Read Entire Entry

  • ALM Workflow: Always Trigger Bug_New when “New Defect” is Clicked

    Posted on May 9, 2012 by Admin

    One “feature” in HP’s Application Lifecycle  Management (ALM) and Quality Center relating to the Defects module is the ability to add multiple defects without ever closing the “New Defect” window, and to resume populating a new defect after the “Close” button is clicked. When the user clicks the “Close” button and then “New Defect”, the field values are cached. This can be a great time saver; however, it is not without its unintended consequences. This means that the Bug_New event is not triggered when clicking the “New Defect” Read Entire Entry