US readers: Order your copy of And I Thought I Knew QTP From Lulu.

I thought I knew QTP is the only book available that is aimed to explain concepts and theories behind automation using QuickTest Professional. Its quite common to the QTP community to choose an approach provided an issue arises. However, when asked why we choose one particular approach over the other or why an approach works well in a given scenario and fails in another, there are no answers available or poorly drafted ones. This book uncovers the ‘why’ by providing ample examples and scenarios.

And I Thought I Knew QTP can be described as a journey of an individual who goes through a series of questions that make him wonder if his QTP skills are as good as he thought they were. The questions are the ones we face on an every day basis to questions we have always wanted to seek answers for. The information made available through this book is written by the world renowned QTP expert, Tarun Lalwani. This book is written with only one vision in mind – there should be a formal source that aims to get rid of all misinformation that we see on an every day basis when searching answers to questions involving QTP.

Because this book is written in the form of a novel with a simple storyline it is very easy to follow through. So, instead of being a completely technical read, this book can be said to be a “technical novel” – it includes technical concepts by not being boring :)

Preview

The preview of the book is now available here.

Preorder

Go ahead and pre-order this book to make sure you have it before the official launch. Order HERE.

Giveaway (Winners now announced)

I will be giving out 1 copy of And I Thought I Knew QTP to one VERY lucky person! :) All you have do to participate is post a comment in the comments section letting us know that you’re interested. That’s all! After a random vote, the winnerS will be declared. Update: 2 more lucky winners (total of 3) will be announced, compliments of Tarun.

Winners

Link to the recorded video: http://www.screenr.com/embed/cXls. Anish Pillai, Priyanka & Suni: congratulations! :)

Links

Links that you will find helpful to order the book, find information and see the previews. I will be updating this section as more links become available.

• US readers: Order your copy of And I Thought I Knew QTP From Lulu
• KnowledgeInbox page
• Facebook page

UI Changes

To begin with, if you’re a regular reader here you will notice that there have been some changes to the post design here. I received an email from a reader who brought the site contrast to my attention which caused difficulty when reading for a long time. Well, the old contract for all post-pages is now gone and we have the following changes:

• Gray background replaced by white
• Code font-family changed from Mono to Consolas
• Code background changed from gray to yellow
• All floating notes are lighter and easy on the eyes

Next Automation Framework

I’ve done some preliminary work for the upcoming framework and would like it to be data-driven. The biggest challenge has been to find an application on which the framework can run and not hurt it by loading a ton of data to it. Chances are I may create the AUT for this. BUT, if you have something in mind that can be used, please do let me know.

Have an idea for an article?

If you have an idea for an article, please let us know! I am always looking to write new stuff, but ideas are the hardest to gather. Your help will be much appreciated!

Subscribe

Please help Relevant Codes by becoming a subscriber. Click one of the buttons above to choose your method of receiving updates. Thank you!

I have been using classes in my frameworks for a long time now, and my biggest gripe about QTP is its lack of Intellisense for custom classes. It also happens to be my biggest complaint. I understand this is not high priority for HP to include in its newer versions as there is a very small group of people who use OO techniques in test automation with QTP. There has been another workaround by Yaron, who used WSC to create intellisense.

I have been researching this topic for a very long time and I finally have a workaround which I have tested for for the past few weeks with great success. The best part about this workaround is, I just need to create wrappers, without including any of the code I have in my QTP function libraries. If I add a new method to my class, all I do to update the Intellisense is add the method (without the QTP code) in my VB lib, create a DLL and Register the library for COM Interop.

Let’s get working then!

Step 1: Create your QTP Modular/Custom/Generic Class

Class LoginClass
 
'#region Private Variables
    Private UserName    'As String
    Private UserRole    'As String

'#region Public Variables
    Public PageTitle    'As String
    Public LinksCount   'As Integer
    
'#region Public Methods
    Public Sub CheckLinks()
        Dim arrLinks
 
        arrLinks = Array("Home", "Register", "Language", "Sign-In")
 
        Call FunctionToCheckLinks(arrLinks)
    End Sub
 
    Public Function IsPageFound() 'As Boolean
        If Browser("title:=MyApp").Exist(15) Then IsPageFound = True
    End Function
 
'#region Class Constructor & Destructor
    Private Sub Class_Initialize()
        UserName = "test"
        UserRole = Global.UserRole
    End Sub
 
    Private Sub Class_Terminate
        'code
    End Sub
 
End Class
 
Public LoginX: Set LoginX = New LoginClass

Step 2: Converting QTP Class into VB.NET code

The next step is converting the method and property names to VB.NET. If you have never used VB.NET, don’t be scared! The syntax is quite straight-forward. The only thing to note here is, you must return values for Functions and Property Get. Also, the syntax of the Property construct differs slightly in VB.NET. Still, all you are including here are the names. You do NOT have to add the code from your QTP methods.

Always remember to include the Microsoft.VisualBasic.ComClass() flag before the class, and also, remember to make the class Public

All that goes in the VB.NET code are the names of the properties and methods. Do not include any QTP code here!

Below is a conversion of the QTP code above, to VB.NET. Notice that I have not included any of the code from my QTP class here:

Save the converted code in a .VB format file

Namespace RelevantCodes
    <Microsoft.VisualBasic.ComClass()> Public Class LoginClass
 
        Public Property PageTitle As String
            Get
                return "title"
            End Get
            Set(ByVal value As String)
                'code
            End Set
        End Property
 
        Public Property LinksCount As Integer
            Get
                return 10
            End Get
            Set(ByVal value As Integer)
            End Set
        End Property
 
        Public Sub CheckLinks()
        End Sub
 
        Public Function IsPageFound() As Boolean
        End Function
 
    End Class
End Namespace

Also remember that, your Public variables become Public Properties in VB.NET.

Step 3: Creating DLL from VB.NET Class using VBC.exe

Once our class is ready and we have saved it in .vb format, let’s create the DLL using VB’s command line compiler VBC/target:library creates a .NET code library (DLL), which is what we’re looking for.

C:\windows\Microsoft.NET\Framework\v2.0.50727\vbc.exe /target:library c:\RelevantCodes.vb

Executing the above syntax in cmd.exe will create a DLL file: RelevantCodes.DLL.

The path to your VBC.exe file may be different than the one I have used.

Step 4: Registering Class using RegAsm.exe

Next, we will use the .NET assembly registration tool RegAsm.exe that reads the metadata within an assembly (which we created using VBC.exe) and adds the necessary values to your registry. RegAsm.exe syntax: regasm assemblyFile [options].

C:\windows\Microsoft.NET\Framework\v2.0.50727\regasm.exe c:\Relevantcodes.dll /codebase

If QTP is already open, save all your tests and resources with libraries and re-open it. Launch it, and use CreateObject to create an instance of your class to see if its working. The syntax will be:

Set InstanceName = CreateObject("Namespace.Class")
 
'for our class:
Set LoginX = CreateObject("RelevantCodes.LoginClass")

You must see Intellisense for the instance to ensure everything has been a success until now. If this works, rest is just adding a few values to Registry and we’re done!

Step 5: Adding the Class Reference as a QTP Reserved Word

If the above works, we’re almost done! To get the intellisense for your class, we need to navigate to the registry key below and add a few values to the new key you create. Navigate to the following key in regedit.exe:

HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\ReservedObjects\

If the above tree does not exist, try this:

HKEY_LOCAL_MACHINE\Software\Mercury Interactive\QuickTest Professional\MicTest\ReservedObjects\

Once you’re there, add a new key under reserved objects. You can give this key any name. What I generally do is, I give the same name as my QTP class. My key, then, becomes LoginClass. Once the key is created, I create the following entries in the key: ProgID (string), UIName (string) and VisibleMode (DWord).

New Key in \ReservedObjects: Name of your QTP Class

String: ProgID,      Value: Namespace.ClassName
String: UIName,      Value: Name of your reference for your custom QTP class
DWord:  VisibleMode, Value: 2

Therefore, in our case, considering the above, we will have the following values:

New Key in \ReservedObjects: LoginClass

String: ProgID,      Value: RelevantCodes.LoginClass
String: UIName,      Value: LoginX
DWord:  VisibleMode, Value: 2

The final output of adding the key and all entries to it must look like below:

Step 6: Reference the Class Instance with another Keyword

Lastly, all you need to do now is add a new variable and reference your Class Instance with it (as shown by Login below):

Public LoginX: Set LoginX = New LoginClass
Public Login : Set Login = LoginX

To create your tests and to get Intellisense, remember to associate your library with the test and use the Login keyword to see the intellisense.

I need to add a new method to my existing class. How do I do that!?!!

Well, once you converted the code for your original VB.NET library, DO NOT delete it. Once you add a new Public method to your QTP class, just add it to your VB.NET code, create (update) DLL using VBC.exe and re-register it using RegAsm. The new methods will now be available.

Summary

In summary, you have to follow the below 6 steps to create Intellisense for your custom QTP class:

1. Create your QTP class
2. Convert “Public” QTP methods to VB.NET (only the method names required!)
• Public Class
• Microsoft.VisualBasic.ComClass() attribute
3. Use VBC.exe to create .NET library
• Creates a DLL in the same location as the .VB file
4. Use RegAsm.exe Assembly Registration tool to add necessary values to Registry
5. Add the Class Instance as a Reserved word in Registry
6. Reference the class with another Keyword

I hope you will find this helpful. As always, thanks for visiting Relevant Codes :)

A lot of time and effort has been put into this article, to research and to test it. The information here is available absolutely free of cost. If you like this article, and if it works for you, please make a donation to a charity of your choice. There is no way we will be able to check if you did, but we know you will. There is a lot of on-going crisis today, and your donation will only help. Thank you.

This article shows a simple way of finding out in which cell a QTP’s Test Object resides. I find the method shown in this article a more effective and faster way of finding the cell I’m looking for. I have found that this method performs better than traversing rows/cells of a WebTable using in-built WebTable methods such as ChildItem, ChildItemCount and GetCellData. Also, for test objects, it is also not possible to find an exact match with the methods provided for WebTable – it is only possible for strings.

A workaround to find objects inside WebTable using DOM table/tr/td is shown in this article. The code snippets below show how to retrieve the row and column of a given object from a WebTable.

Consider the element “Doe” in the table below. We can visually see that the link is in the 5th row (starting at the heading) and the 3rd column.

Executing the following code will provide us our expected output:

Set element = Browser("creationtime:=0").WebElement("innertext:=Doe", "index:=0")

MsgBox "Row# " & element.GetRow()
MsgBox "Col# " & element.GetColumn()

The above example uses WebElement, but this approach works for all Web objects. Similarly, the code for finding the 2nd WebCheckBox for Anne Johnson will give us: Row# 3 and Column#5 with the following code:

MsgBox Browser("creationtime:=0").WebCheckBox("name:=attending", "index:=1").GetRow
MsgBox Browser("creationtime:=0").WebCheckBox("name:=attending", "index:=1").GetColumn

The Code

The following two methods can be used directly for the object and will retrieve ‘either’ the row or the column. The below method retrieves the Row for an object residing in a WebTable:

Find Row of the Object from WebTable

Function GetRow(ByVal TObject)
    GetRow = -1
 
    Set TObject = TObject.Object
 
    Do
        If TObject.nodeName = "TR" Then
            GetRow = TObject.rowIndex + 1
            Exit Function
        End If
 
        Set TObject = TObject.parentNode
    Loop Until TObject.nodeName = "HTML"
End Function
 
RegisterUserFunc "Image", "GetRow", "GetRow"
RegisterUserFunc "Link", "GetRow", "GetRow"
RegisterUserFunc "WebEdit", "GetRow", "GetRow"
RegisterUserFunc "WebList", "GetRow", "GetRow"
RegisterUserFunc "WebCheckBox", "GetRow", "GetRow"
RegisterUserFunc "WebElement", "GetRow", "GetRow"
RegisterUserFunc "WebRadioGroup", "GetRow", "GetRow"

Example

MsgBox Browser("title:=myBrowser").Link("innertext:=myLink", "index:=1").GetRow

This method returns the column of the object inside a WebTable:

Find Column of the Object from WebTable

Function GetColumn(ByVal TObject)
    GetColumn = -1
 
    Set TObject = TObject.Object
 
    Do
        If TObject.nodeName = "TD" Then
            GetColumn = TObject.cellIndex + 1
            Exit Function
        End If
 
        Set TObject = TObject.parentNode
    Loop Until TObject.nodeName = "HTML"
End Function
 
RegisterUserFunc "Image", "GetColumn", "GetColumn"
RegisterUserFunc "Link", "GetColumn", "GetColumn"
RegisterUserFunc "WebEdit", "GetColumn", "GetColumn"
RegisterUserFunc "WebList", "GetColumn", "GetColumn"
RegisterUserFunc "WebCheckBox", "GetColumn", "GetColumn"
RegisterUserFunc "WebElement", "GetColumn", "GetColumn"
RegisterUserFunc "WebRadioGroup", "GetColumn", "GetColumn"

Example

MsgBox Browser("title:=myBrowser").Link("innertext:=myLink", "index:=1").GetColumn

The below implementation retrieves both row and column as a Scripting.Dictionary.

Find Row & Column Info as Scripting.Dictionary

Function CellInfo(ByVal TObject)
    Dim dic
 
    Set dic = CreateObject("Scripting.Dictionary")
    dic.Add "row", -1
    dic.Add "col", -1
 
    Set TObject = TObject.Object
 
    Do
        If TObject.nodeName = "TD" Then dic("col") = TObject.cellIndex + 1
 
        If TObject.nodeName = "TR" Then
            dic("row") = TObject.rowIndex + 1
            Exit Do
        End If
 
        Set TObject = TObject.parentNode
    Loop Until TObject.nodeName = "HTML"
 
    Set CellInfo = dic
End Function
 
RegisterUserFunc "Image", "CellInfo", "CellInfo"
RegisterUserFunc "Link", "CellInfo", "CellInfo"
RegisterUserFunc "WebEdit", "CellInfo", "CellInfo"
RegisterUserFunc "WebList", "CellInfo", "CellInfo"
RegisterUserFunc "WebRadioGroup", "CellInfo", "CellInfo"
RegisterUserFunc "WebElement", "CellInfo", "CellInfo"
RegisterUserFunc "WebCheckBox", "CellInfo", "CellInfo"

Example

Set cells = Browser("title:=myBrowser").Link("innertext:=myLink", "index:=1").CellInfo()

MsgBox cells("row")
MsgBox cells("col")

cells.RemoveAll
Set cells = Nothing

I hope you find this helpful. As always, thanks for visiting Relevant Codes :)

Over the past few years, I have read numerous threads and posts talking about working with Excel using VBScript. Not only have there been numerous threads, but also frameworks that use Excel as the input and/or driver engine. I wanted to work on this mini-project for a long time, and I finally have Version 1.0 of ExcelUtil ready for download! It comes with .CHM documentation.

I’m quite sure I have missed some methods that the community uses, which I have not been able to include in the 1st version. I, however, am open to suggestions and would gladly include your ideas for Version 2.0.

Download RelevantCodes.ExcelUtil Class Library (1054)

IMPORTANT: To use any method of ExcelUtil, be sure to use SetFile. This will set the Excel WorkBook and WorkSheet ready for use. To use a different WorkBook or WorkSheet, SetFile will have to be called again.

SetFile Property

Value Type

Read only. A [RelevantCodes.ExcelUtil] object.

Description

Sets the region instances for Excel WorkBook and WorkSheet. These instances for the Excel source are created only once and used by other methods. NOTE: For any method to execute, SetFile must be executed first to set the WorkBook and WorkSheet.

Syntax

ExcelUtil.SetFile WorkBookPath, WorkSheet

Examples

'Example 1
ExcelUtil.SetFile "C:\Student.xls", "Sheet1"
 
'Example 2:  Reading value directly from a file
sCellValue = ExcelUtil.SetFile("C:\Student.xls", "Sheet1").GetCellValue(1, 1)
 
'Example 3:  Reading values from 2 different files - Approach 1
ExcelUtil.SetFile "C:\Student.xls", "Sheet1"
var1 = ExcelUtil.GetCellValue(1, 1)
ExcelUtil.SetFile "C:\Teacher.xls", "Sheet1"
var2 = ExcelUtil.GetCellValue(1, 1)
 
'Example 4:  Reading values from 2 different files - Approach 2
var1 = ExcelUtil.SetFile("C:\Student.xls", "Sheet1").GetCellValue(1, 1)
var2 = ExcelUtil.SetFile("C:\Teacher.xls", "Sheet1").GetCellValue(1, 1)

I found a Bug. What should I do next?

Reporting the bug in the comments section will ensure the next version of this class library is more robust! It may not be possible to release the fixed code immediately, but notifying me and the readers of all potential bugs will be highly appreciated! Thank you.

I have something cool I would like you to add to ExcelUtil.

I would love to hear all ideas and suggestions to improve or enhance this library. Please use the comments section to share them with me and the community. Thank you.

Download RelevantCodes.ExcelUtil Class Library (1054)

For the past few weeks, I have been actively working on Quality Center (ALM) and its integration with QuickTest Professional. One of the mini-projects I’ve worked on is creating a custom object that executes a test set and sends an email to the supplied distribution list from ALM TestSet’s Automation tab (as shown below):

Note: The above part (EMailTo) can be modified by either hard-coding it, or supplying an input from the Class Constructor.

I’ve extensively used the OTA API Reference to build this object and to understand how the API works. .NET developers having difficulty converting the VBScript code, please post in the comments section and I will mail you the class library (currently only C#).

Download (ALM Only)

QCRunTestSet is available for download, but comes as-is and currently executes TestSets on the localHost. However, I would be more than happy in helping you to modify this code to suit your needs.

QCRunTestSet.cls.vbs.zip [for ALM] (1219)

If you’re having issues creating an instance of the TSScheduler object, please read this thread carefully. You may need to upgrade to a higher patch or perform a client registration on the execution machine.

Running QCRunTestSet from CommandLine

If you would like to pass parameters from the CommandLine instead of hard-coding them in the code, use WScript to pass arguments and WScript.Arguments to retrieve them in the class library. Example:

'Passing arguments
wscript C:\QCRunTestSet.cls.vbs "http//<server>:8080/qcbin" myUser myPassword myDomain _
                                                  myProject myTestSetPath myTestSetName

'Retrieving arguments
Set args = WScript.Arguments
 
QCServer = args(0)
UserName =  args(1)
Password = args(2)
QCDomain = args(3)
QCProject = args(4)
QCTestSetPath = args(5)
QCTestSetName = args(6)

I hope you find this helpful. Thanks for visiting Relevant Codes! :)

While testing a script on IE8, me and my colleague kept getting the error “A script on this page is causing Internet Explorer to run slowly”. Below is a snapshot of the error:

After some research, I came across an article on MSDN which already had the solution: Microsoft KB # 175500. The part we are concerned about is in the section “Let me fix it myself”:

1.Using a Registry Editor such as Regedt32.exe, open this key: HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles
Note: If the Styles key is not present, create a new key that is called Styles.
2. Create a new DWORD value called “MaxScriptStatements” under this key and set the value to the desired number of script statements. If you are unsure of what value you need to set this to, you can set it to a DWORD value of 0xFFFFFFFF to completely avoid the dialog.

For the curious ones, the article states that, to encounter the error, the DWord value of 0xFFFFFFFF must be added. The value equates to -1, which is what has been used in the function below.

The VBScript:

Sub IE_ChangeScriptTimeOut()
	Dim Registry, sKeyPath, sValueName, dwValue, sComputer
	CONST HKEY_CURRENT_USER = &H80000001
 
	sKeyPath = "Software\Microsoft\Internet Explorer\Styles"
	sValueName = "MaxScriptStatements"
	dwValue = -1
	sComputer = "."
 
	On Error Resume Next
		Set Registry = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &_ 
				sComputer & "\root\default:StdRegProv")
 
		Registry.CreateKey HKEY_CURRENT_USER, sKeyPath
		Registry.SetDWORDValue HKEY_CURRENT_USER, sKeyPath, sValueName, CLng(dwValue)
	On Error Goto 0
 
	Set Registry = Nothing
End Sub

Thanks for reading, and thanks for visiting Relevant Codes! :)

I’ve generally seen some confusion around CreationTime. I think between the 3 Ordinal Identifiers, this one may be the easiest to understand and implement. That’s mostly because CreationTime is used only for the Browser object. Below is how CreationTime is applied to browsers:

1st open browser -> CreationTime of -> 0
2nd open browser -> CreationTime of -> 1
3rd open browser -> CreationTime of -> 2
4th open browser -> CreationTime of -> 3

According to QTP help:

This value indicates the order in which the browser was opened relative to other open browsers. For example, if QuickTest learns three browsers that are opened at 9:01 pm, 9:03 pm, and 9:05 pm, QuickTest assigns the CreationTime values, as follows: CreationTime = 0 to the 9:01 am browser, CreationTime = 1 to the 9:03 am browser, and CreationTime = 2 to the 9:06 am browser.

Really, that’s it! No tricks here! To test it for proof, you can open 4 browsers (with different websites) and run the following code in QTP:

For ix = 0 to 3
	Print "CreationTime->" & ix & "->" & Browser("creationtime:=" & ix).GetROProperty("title")
Next

On my desktop, I’ve 4 open IE windows in the following order: Google, Bing, Yahoo, Microsoft. See snapshot below:

My taskbar: Click to view original size

After running the above code, this is what I see in my print log:

Print log

The output shows the order in which the IE windows are placed on the Desktop, which is same as the order in which they were opened.

The tricky part

The only tricky part in this concept is its applicability when there is only one browser open. With one open browser, regardless of the CreationTime value supplied, QTP will always identify the only open browser. This is because, CreationTime values are generated when there are multiple browsers open – with a single open browser, this value is generally has no usage. This is at least true for QTP 10.0 and previous versions.

As always, thanks for visiting Relevant Codes! :)

If you have any questions, please ask them in the comments section.

VBScript’s error handling techniques have been quite limited to On Error statements, and even though they satisfy our needs to some extent, the lack of incorporating dynamic behavior with them has been a much bigger issue. Lee Harvey here shows how Classes can be extended to create simple Try-Catch-Finally statements with just a bit more work. I like this technique, and have been using it for the past few days with success. We know that this is not the best solution that is possible with a scripting language (JS does a lot better!), but its a start and a terrific workaround (thanks Lee!).

Creating Try-Catch-Finally Statements in VBScript

If you have already read Lee’s article, you can skip this part. Otherwise, a simple implementation is shown below:

1. As soon as the class executes, it enters Class_Initialize – Try statement
2. It encounters an error – Err.Raise 1002
3. As soon as it encounters an error, the Try statement (Class_Initialize) immediately ends execution
4. Because we’re releasing the Class reference using Set NewTryCatchFinally = Nothing right after initializing it, the Class enters Class_Terminate
5. Class_Terminate calls the Catch subroutine
6. When Catch runs in its entirety, Class_Terminate executes

On Error Resume Next
 
Class TryCatchFinally
 
    Private Sub Class_Initialize 'Try
        Print "Entering Try.." & vbNewLine
 
        Err.Raise 1002 'Raise a Syntax Error
        MsgBox "This line will not execute"
    End Sub
 
    Private Sub Catch 'Catch
        If Err.Number = 0 Then Exit Sub
 
        Print "Entering Catch.."
        Print "Error caught: " & Err.Description  & vbNewLine
 
        Err.Clear
    End Sub
 
    Private Sub Class_Terminate : Catch 'Finally
        Print "Exiting.." 
    End Sub
 
End Class
 
Set NewTryCatchFinally = New TryCatchFinally : Set NewTryCatchFinally = Nothing

The output of executing the above code should be the following:

Try Catch Finally Implementation in VBScript

We can see from the result that as soon as the Class executes, it enters Class_Initialize. When it encounters an error, it enters into Class_Terminate which contains (and executes) the Catch method. A simple yet such an elegant solution!

Utility Class & Error Handler

In this article, I will try to implement the technique with QTP’s GUI objects. To begin, let’s create a simple Login class with the following methods:

1. CheckPage
2. CheckImage
3. Login

The Login Class outputs the result through the Result property:

A simple Login Class

On Error Resume Next
 
Class Login
 
    Public Property Get Result
        Result = CheckPage And CheckImage And Login
    End Property
 
    Private Function CheckPage
        MsgBox "CheckPage" : CheckPage = True
    End Function
 
    Private Function CheckImage
        CheckImage = False
 
        Browser("title:=Welcome.*").WebElement("text:=Relevant Codes").Click 'Error here!

        MsgBox "Error!" 'This will not execute
    End Function
 
    'This will not execute
    Private Function Login
        MsgBox "Login"
    End Function
 
End Class
 
Dim NewLogin : Set NewLogin = New Login

Above, the Result property of the Login Class is called, which first executes CheckPage, then CheckImage and finally Login. Note that Login will only execute if CheckImage runs without any errors.

Let’s create another class that calls the methods of the original Login class, but with the error handling capabilities of a Try-Catch-Finally statement. This is also the Class that will always execute the original Login class because that’s where the actual error handling using Try-Catch-Finally exists.

Try..Catch..Finally with Class_Initialize & Class_Terminate

Class LoginHandler 'LoginHandler start

    Public bResult
 
    Private Sub Class_Initialize
         Print "Entering Try.." & vbNewLine
         bResult = NewLogin.Result
    End Sub
 
    Private Sub CatchErr
        If Err.Number = 0 Then Exit Sub
 
        Print "Entering Catch.."
        Print "Error: " & Err.Description & vbNewLine
 
        Err.Clear
    End Sub
 
    Private Sub Class_Terminate : CatchErr
        Print "Exiting.."
    End Sub
 
End Class 'LoginHandler end

Set NewLoginHandler = New LoginHandler
Set NewLoginHandler = Nothing
Set NewLogin = Nothing

The Class_Initialize method of the class calls the Result property of the Login class. Once Result is called, it executes all the methods called by the Result property. If any error occurs, CatchErr is immediately called by Class_Terminate and later, all code inside the Class_Terminate method is executed.

Output of executing Login Class & LoginHandler:

QTP Print Log

Method Containing the Error?

By including the name of each method in the very first line, we can also find out where exactly the error occurred. This, however, I agree is quite time consuming and repetitive work. The only alternative to this has been shown by PowerDebug Beta. However, if you would like to extend the above approach in VBScript, this *may be* the only possible approach. I’ve been wrong before, and would love to see a technique which simplifies the method naming approach used below.

Login Class with Method Names

On Error Resume Next
 
Class Login 'Login start

    Public sMethod
 
    Public Property Get Result
        Result = CheckPage And CheckImage And Login
    End Property
 
    Private Function CheckPage
        Me.sMethod = "CheckPage"
 
        MsgBox "CheckPage" : CheckPage = True
    End Function
 
    Private Function CheckImage
        Me.sMethod = "CheckImage"
 
        CheckImage = False
        Browser("title:=Welcome.*").WebElement("text:=Relevant Codes").Click 'Error here!
        
        MsgBox "Error!" 'This will not execute
    End Function
 
    Private Function Login 'This will not execute
        Me.sMethod = "Login"
 
        Msgbox "Login"
    End Function
 
End Class 'Login end
Dim NewLogin : Set NewLogin = New Login

LoginHandler (Outputs Method Names)

Class LoginHandler 'LoginHandler start

    Public bResult
 
    Private Sub Class_Initialize
         Print "Entering Try.." & vbNewLine
         bResult = NewLogin.Result
    End Sub
 
    Private Sub CatchErr
        If Err.Number = 0 Then Exit Sub
 
        Print "Entering Catch.."
        Print "Error occured in: " & NewLogin.sMethod
        Print "Error: " & Err.Description & vbNewLine
 
        Err.Clear
    End Sub
 
    Private Sub Class_Terminate : CatchErr
        Print "Exiting.."
    End Sub
 
End Class 'LoginHandler end

Set NewLoginHandler = New LoginHandler
Set NewLoginHandler = Nothing
Set NewLogin = Nothing

View code.

Output of executing Login Class & LoginHandler:

QTP Print Log

Notes

After using this technique for several days and manipulating it a bit from the original work, I have found some success. However, implementing Handler classes when the scope of the utility class increases can be quite challenging, and time consuming. I still believe its a start to something that we haven’t witnessed in QTP (yet). To be honest, I still prefer the old way of doing things where I can branch out most of my GUI code in conditional statements – which has enabled me to always create more comprehensive reporting.

My recommendation would be to use this approach with VBScript code instead of using it for QTP’s GUI objects, ofcourse, until absolutely necessary. Most of my usage for the above technique has been with pure VBScript code which has enabled me to create better error handling. In an upcoming article, I will show how this technique will be used to handle Excel errors and recover from them in the CatchErr method using a Select Case block. Including Try-Catch-Finally statements within Try-Catch-Finally statements is quite easily done in .NET, but its very complex to perform the same operation with VBScript. I’m still happy to have a start though.

If you have any questions, please ask them in the comments section.

Hi everyone,

I know and you may have realized that there haven’t been any new article or updates here for the last few weeks. I have been extremely busy with prior obligations, work and a few big projects outside of work that I have been engaged in. However, please be assured that there are some articles on the way and another demo framework over the next few days.

I also appreciate requests for articles that you would like to see here, so please feel free to contribute your ideas!

I really appreciate everyone who visited and supported Relevant Codes during my off-time. I also value all your comments, suggestions, criticism and queries. They keep me coming back everyday to see that this website has grown to such a level from a very little blog that started a year ago.

Also, please don’t forget to subscribe to ensure all articles are delivered to your email as soon as they are published! :)

Thanks!

Anshoo Arora