Functional Pointer in VBScript Abstract Function pointers are used in C and C++ to enable callbacks and as a result, more generic

and parsimonious coding. This article shows how to implement function pointers in VB Script using the Scripting.Dictionary object and the Command Wrapper design pattern. It is also shown how to implement “constructor” functions, callbacks land event handlers.

Keywords: function pointer, callback, delegate, scripting dictionary, hash table, design pattern, command wrapper, event handler. Introduction In the following sections I shall explain several basic concepts that are essential to understand the rationale behind the suggested method. The list might be nonexhaustive and the reader is hereby encouraged to recur to complementary sources to fill-in any eventual knowledge gaps. Function Pointers A function pointer is a variable that stores the memory address of a block of code that is programmed to fulfill a specific function. Function pointers are useful to avoid complex switch case structures; instead, they support direct access in run-time to previously loaded functions or class methods. This enables the construction of callback functions. A callback is, in essence, executable code that is passed as argument to a function. This enables more generic coding, by having lower-level modules calling higher-level functions or subroutines. Function pointers are supported by programming languages like C and C++. A recent good introductory text on the subject with implementation examples is Lars Haendel (2005). This article shows how to implement function pointers in VB script. Design Patterns Design patterns are well established generic design techniques whose aim is to make software design and the derived code more parsimonious, scalable, and reusable, as well as more easily maintainable. This article will delve only into the command wrapper design pattern, which is important for its purpose. For a more extensive explanation of

design patterns, the reader is encouraged to read the literature in the field (e.g., Gamma, Helm, Johnson, & Vlissides, 1997). The command-wrapper design pattern enables to load blocks of code dynamically to memory as well as other uses as will be reviewed below. The singleton design pattern is used to restrict instantiation of a class to one object. This is useful when there is no need for more than one object within a system (e.g., a reporter/logger object). For example, the factory design pattern usually implements the singleton design pattern to have a single interface from which to retrieve references to a specific class object or to a variety of class objects. The Command Wrapper Design Pattern The command wrapper design pattern is a technique that implements a function as a class, usually with a single public method. During run-time, it is possible to instantiate the class and thus to get a reference (or pointer) to the object. This way, the code embodied in such methods can be dynamically loaded, a feature that can be of great value in systems that are poor in resources. This is especially true when the to-be called function is rarely used. After creating the object, it is possible to execute its method according to need. For example, let us assume a function that adds numbers (note: this example is, of course, trivial. It is done just to illustrate the point.)
1: Public Function Sum(ByVal arrNumbers) 2: Dim ix 3: 4: 'Check if an array was passed. If so, there's nothing to do – exit function 5: If (Not IsArray(arrNumbers)) Then 6: 'Add your error handling code here 7: Exit Function 8: End If 9: 10: Sum = 0 11: For ix = LBound(arrNumbers) To UBound(arrNumbers) 12: If (IsNumeric(arrNumbers(ix))) Then 13: Sum = Sum + arrNumbers(ix) 14: Else 15: 'Add your error handling code here 16: End If 17: Next 18: End Function 19: 20: 'Test the function and display result returned by the Sum function 21: MsgBox Sum(Array(23, 56, 78, 95, 114)), vbOKOnly, "Result from simple function" 22: 23: 24: 'Now, let us convert this function into an object using the Command Wrapper design pattern:

25: Class Sum 26: Private m_arrVarNumbers 27: Private m_varResult 28: 29: Private Sub Class_Initialize() 30: 'Initialize the Numbers member as an empty array 31: ReDim m_arrVarNumbers(-1) 32: End Sub 33: 34: Public Function Init(ByVal arrVarNumbers) 35: Numbers = arrVarNumbers 36: End Function 37: 38: Public Default Function Exec() 39: Dim ix, arrNumbers 40: 41: 'Check if an array was passed. If so, there's nothing to do – exit function 42: If (Not IsArray(Numbers)) Then 43: 'Add your error handling code here 44: Exec = "Invalid data type was supplied to perform the operation." 45: Exit Function 46: ElseIf (UBound(Numbers) - LBound(Numbers) + 1 <= 1) Then 47: 'Array is empty or has single item - Add your error handling code here 48: Exec = "Not enough data was supplied to perform the operation." 49: Exit Function 50: Else 51: arrNumbers = Numbers 52: End If 53: 54: Result = 0 55: For ix = LBound(arrNumbers) To UBound(arrNumbers) 56: If (IsNumeric(arrNumbers(ix))) Then 57: Result = Result + arrNumbers(ix) 58: Else 59: 'Add your error handling code here 60: End If 61: Next 62: Exec = Result 63: End Function 64: 65: Public Property Get Numbers() 66: Numbers = m_arrVarNumbers 67: End Property 68: 69: Private Property Let Numbers(ByVal arrVarNumbers) 70: m_arrVarNumbers = arrVarNumbers 71: End Property 72: 73: Public Property Get Result() 74: Result = m_varResult 75: End Property 76: 77: Private Property Let Result(ByVal varResult) 78: m_varResult = varResult

79: End Property 80: End Class 81: 82: 'This function behaves as a constructor and returns an initialized instance of the class 83: Public Function GetSum(ByVal arrNumbers) 84: Set GetSum = New Sum 85: GetSum.Init(arrNumbers) 86: End Function 87: 88: 'Test the class 89: Dim objSum, arrNumbers 90: 91: 'Assign an array of numbers 92: arrNumbers = Array(23, 56, 78, 95, 114) 93: 94: 'Get an instance of class Sum and initialize it with numbers array 95: Set objSum = GetSum(arrNumbers) 96: 97: 'Execute Sum (Exec method) 98: objSum.Exec() 99: 100: 'Display result stored in Result property 101: MsgBox objSum.Result, vbOKOnly, "Result from Result Property" 102: 103: 'Alternatively, display the result returned by the Exec method: 104: MsgBox GetSum(Array(23, 56, 78, 95, 114)).Exec, vbOKOnly, "Result from Exec method"

The Scripting Dictionary In VB Script, the scripting dictionary is an object that stores key-item pairs using a hashing algorithm. The items can be accessed using their corresponding keys. Basically, the dictionary is useful to store variant type, non-structured data, such as the catalog number of an item in an inventory list, or the authors of a list of books, and to retrieve the data using the unique keys supplied, as in the following example:
1: Dim dicBooksAuthors 2: 3: 'Create an instance of the scripting dictionary class 4: Set dicBookAuthors = CreateObject("Scripting.Dictionary") 5: 6: With dicBookAuthors 7: 'Add some books (keys) and authors (items) 8: .Add "The Selfish Gene", "Richard Dawkins" 9: .Add "The Mismeasure of Man", "Stephen J. Gould" 10: .Add "The Da Vinci Code", "Dan Brown" 11: 12: 'Answer the question: who wrote "The Selfish Gene"? 13: strBook = "The Selfish Gene" 14: MsgBox .item(strBook), vbOKOnly+vbInformation, "Author query result for book: " & strBook 15: End With

In addition. arrNumbers 16: 17: If (Not IsArray(Numbers)) Then 'Not an array. so nothing to do – exit function 18: 'Add your error handling code here . it has been indicated that the VBScript Scripting Dictionary object is equipped with the capacity of storing variant data types. Thanks to its capacity to store variant data types. it is actually possible to store references to objects of different types. In the next chapter. For instance. For instance. Recall that a pointer is a variable that stores the memory address of a function or instantiated class object. it is possible to store complex data structures by using nested dictionaries (this issue. it eliminates the need for item search functions (direct access) and avoids duplicate key creation. including references to objects. Here below. the dictionary can be much more than just a data storage and retrieval device. we shall delve into a method to exploit this feature of the scripting dictionary object to implement function pointers in VBScript. is out of the scope of the current paper). In what follows a method will be described to combine these two features into a powerful design and programming technique. However. we shall now show how it is possible to build function pointers using a Scripting Dictionary.The example above demonstrates the power of a dictionary as a data storage and data retrieval device. Implementing Function Pointers in VB Script Earlier in this article. however. Following the example given above in the Command Wrapper section. The Addition Operation 1: Class Sum 2: Private m_arrVarNumbers 3: Private m_varResult 4: 5: Private Sub Class_Initialize() 6: 'Initialize the Numbers member as an empty array 7: ReDim m_arrVarNumbers(-1) 8: End Sub 9: 10: Public Function Init(ByVal arrVarNumbers) 11: Numbers = arrVarNumbers 12: End Function 13: 14: Public Default Function Exec() 15: Dim ix. we have shown that it is possible to encapsulate any function as a class by using the command wrapper design pattern. we shall demonstrate the case of the four basic arithmetic operations.

Add your error handling code here Exec = "Not enough data was supplied to perform the operation.19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32: 33: 34: 35: 36: 37: 38: 39: 40: 41: 42: 43: 44: 45: 46: 47: 48: 49: 50: 51: 52: 53: 54: 55: 56: 57: 58: 59: 60: 61: Exec = "Invalid data type was supplied to perform the operation." Exit Function Else arrNumbers = Numbers End If Result = 0 For ix = LBound(arrNumbers) To UBound(arrNumbers) If (IsNumeric(arrNumbers(ix))) Then Result = Result + arrNumbers(ix) Else 'Add your error handling code here End If Next Exec = Result End Function Public Property Get Numbers() Numbers = m_arrVarNumbers End Property Private Property Let Numbers(ByVal arrVarNumbers) m_arrVarNumbers = arrVarNumbers End Property Public Property Get Result() Result = m_varResult End Property Private Property Let Result(ByVal varResult) m_varResult = varResult End Property End Class 'This function behaves as a constructor and returns an initialized instance of the class Public Function GetSum(ByVal arrNumbers) Set GetSum = New Sum GetSum.Init(arrNumbers) End Function The Subtraction Operation 1: Class Subtract 2: Private m_arrVarNumbers 3: Private m_varResult 4: 5: Private Sub Class_Initialize() 6: 'Initialize the Numbers member as an empty array .LBound(Numbers) + 1 <= 1) Then 'Array is empty or has single item ." Exit Function ElseIf (UBound(Numbers) .

Add your error handling code here 23: Exec = "Not enough data was supplied to perform the operation.LBound(Numbers) + 1 <= 1) Then 22: 'Array is empty or has single item . arrNumbers 16: 17: If (Not IsArray(Numbers)) Then 'Not an array." 20: Exit Function 21: ElseIf (UBound(Numbers) ." 24: Exit Function 25: Else 26: arrNumbers = Numbers 27: End If 28: 29: Result = arrNumbers(LBound(arrNumbers)).arrNumbers(ix) 33: Else 34: 'Add your error handling code here 35: End If 36: Next 37: Exec = Result 38: End Function 39: 40: Public Property Get Numbers() 41: Numbers = m_arrVarNumbers 42: End Property 43: 44: Private Property Let Numbers(ByVal arrVarNumbers) 45: m_arrVarNumbers = arrVarNumbers 46: End Property 47: 48: Public Property Get Result() 49: Result = m_varResult 50: End Property 51: 52: Private Property Let Result(ByVal varResult) 53: m_varResult = varResult 54: End Property 55: End Class 56: 57: 'This function behaves as a constructor and returns an initialized instance of the class 58: Public Function GetSubtract(ByVal arrNumbers) 59: Set GetSubtract = New Subtract 60: GetSubtract. so nothing to do – exit function 18: 'Add your error handling code here 19: Exec = "Invalid data type was supplied to perform the operation.arrNumbers(LBound(arrNumbers)+1) 30: For ix = LBound(arrNumbers)+2 To UBound(arrNumbers) 31: If (IsNumeric(arrNumbers(ix))) Then 32: Result = Result .7: ReDim m_arrVarNumbers(-1) 8: End Sub 9: 10: Public Function Init(ByVal arrVarNumbers) 11: Numbers = arrVarNumbers 12: End Function 13: 14: Public Default Function Exec() 15: Dim ix.Init(arrNumbers) .

Add your error handling code here 23: Exec = "Not enough data was supplied to perform the operation. so nothing to do – exit function 18: 'Add your error handling code here 19: Exec = "Invalid data type was supplied to perform the operation.LBound(Numbers) + 1 <= 1) Then 22: 'Array is empty or has single item ." 20: Exit Function 21: ElseIf (UBound(Numbers) . arrNumbers 16: 17: If (Not IsArray(Numbers)) Then 'Not an array.61: End Function The Multiplication Operation 1: Class Multiply 2: Private m_arrVarNumbers 3: Private m_varResult 4: 5: Private Sub Class_Initialize() 6: 'Initialize the Numbers member as an empty array 7: ReDim m_arrVarNumbers(-1) 8: End Sub 9: 10: Public Function Init(ByVal arrVarNumbers) 11: Numbers = arrVarNumbers 12: End Function 13: 14: Public Default Function Exec() 15: Dim ix." 24: Exit Function 25: Else 26: arrNumbers = Numbers 27: End If 28: 29: Result = arrNumbers(LBound(arrNumbers)) * arrNumbers(LBound(arrNumbers)+1) 30: For ix = LBound(arrNumbers)+2 To UBound(arrNumbers) 31: If (IsNumeric(arrNumbers(ix))) Then 32: Result = Result * arrNumbers(ix) 33: Else 34: 'Add your error handling code here 35: End If 36: Next 37: Exec = Result 38: End Function 39: 40: Public Property Get Numbers() 41: Numbers = m_arrVarNumbers 42: End Property 43: 44: Private Property Let Numbers(ByVal arrVarNumbers) 45: m_arrVarNumbers = arrVarNumbers 46: End Property 47: 48: Public Property Get Result() .

49: 50: 51: 52: 53: 54: 55: 56: 57: 58: 59: 60: 61: Result = m_varResult End Property Private Property Let Result(ByVal varResult) m_varResult = varResult End Property End Class 'This function behaves as a constructor and returns an initialized instance of the class Public Function GetMultiply(ByVal arrNumbers) Set GetMultiply = New Multiply GetMultiply. so nothing to do – exit function 18: 'Add your error handling code here 19: Exec = "Invalid data type was supplied to perform the operation. arrNumbers 16: 17: If (Not IsArray(Numbers)) Then 'Not an array.LBound(Numbers) + 1 <= 1) Then 22: 'Array is empty or has single item ." 34: Exit Function 35: End If .Init(arrNumbers) End Function The Division Operation 1: Class Divide 2: Private m_arrVarNumbers 3: Private m_varResult 4: 5: Private Sub Class_Initialize() 6: 'Initialize the Numbers member as an empty array 7: ReDim m_arrVarNumbers(-1) 8: End Sub 9: 10: Public Function Init(ByVal arrVarNumbers) 11: Numbers = arrVarNumbers 12: End Function 13: 14: Public Default Function Exec() 15: Dim ix." 20: Exit Function 21: ElseIf (UBound(Numbers) .Add your error handling code here 23: Exec = "Not enough data was supplied to perform the operation." 24: Exit Function 25: Else 26: arrNumbers = Numbers 27: End If 28: 29: If (IsNumeric(arrNumbers(LBound(arrNumbers))) And IsNumeric(arrNumbers(LBound(arrNumbers)+1)) And (arrNumbers(LBound(arrNumbers)+1) <> 0)) Then 30: Result = arrNumbers(LBound(arrNumbers)) / arrNumbers(LBound(arrNumbers)+1) 31: Else 32: 'Add your error handling code here 33: Exec = "Invalid data was supplied to perform the operation.

New Divide 12: End With 13: 14: 'Execute the functions using the Function Handler 15: With dicFunctionHandler 16: With .Add "*". New Sum 9: .Add "+".Init(arrNumbers) End Function Using the Function Pointers to Perform the basic Arithmetic Operations 1: Dim dicFunctionHandler 2: 3: 'Create an instance of the scripting dictionary class 4: Set dicFunctionHandler = CreateObject("Scripting.Add "-".item("+") .Add "/". New Multiply 11: .36: 37: 38: 39: 40: 41: 42: 43: 44: 45: 46: 47: 48: 49: 50: 51: 52: 53: 54: 55: 56: 57: 58: 59: 60: 61: 62: 63: 64: 65: 66: 67: 68: For ix = LBound(arrNumbers)+2 To UBound(arrNumbers) If (IsNumeric(arrNumbers(ix)) And (arrNumbers(ix) <> 0)) Then Result = Result / arrNumbers(ix) Else 'Add your error handling code here End If Next Exec = Result End Function Public Property Get Numbers() Numbers = m_arrVarNumbers End Property Private Property Let Numbers(ByVal arrVarNumbers) m_arrVarNumbers = arrVarNumbers End Property Public Property Get Result() Result = m_varResult End Property Private Property Let Result(ByVal varResult) m_varResult = varResult End Property End Class 'This function behaves as a constructor and returns an initialized instance of the class Public Function GetDivide(ByVal arrNumbers) Set GetDivide = New Divide GetDivide.Dictionary") 5: 6: 'Load some functions 7: With dicFunctionHandler 8: . New Subtract 10: .

GetDivide(Array(84. "Result (/)" 'Display result returned by the Exec method 31: End With 32: End With 33: 34: 'Or. 5.Exec(). 56. GetMultiply(Array(7. 23)) 40: . Implement a function handler using a scripting dictionary. using the "constructors": 35: 'First.Exec(). vbOKOnly+vbInformation.item("*"). 78.Exec(). . Implement a “constructor” for a class in VBScript.Add "*". Implement the Command Wrapper design pattern in VBScript.Exec().Init(Array(23.Add "+". 78. "Result (-)" 'Display result returned by the Exec method 48: MsgBox . "Result (*)" 'Display result returned by the Exec method 49: MsgBox . "Result (*)" 'Display result returned by the Exec method 27: End With 28: With . vbOKOnly+vbInformation.Init(Array(7. 5)) 26: MsgBox . vbOKOnly+vbInformation.Add "/".Exec(). 5)) 41: .Exec(). 2.Add "-". 56. 114)) 18: MsgBox .item("*") 25: Call . vbOKOnly+vbInformation. 12)) 30: MsgBox . 12)) 42: End With 43: 44: 'Second. 95.item("+").item("-"). "Result (+)" 'Display result returned by the Exec method 47: MsgBox . vbOKOnly+vbInformation. 114)) 39: .Exec().Init(Array(117. vbOKOnly+vbInformation. 23)) 22: MsgBox .Exec().item("-") 21: Call .item("/").RemoveAll 38: . load some functions 36: With dicFunctionHandler 37: . 4.item("/") 29: Call . GetSum(Array(23. Call the loaded function via the dictionary key and retrieve the result.Init(Array(84. 95.17: Call . Instantiate such custom classes and load them to a scripting dictionary. execute the functions using the Function Handler 45: With dicFunctionHandler 46: MsgBox . GetSubtract(Array(117. vbOKOnly+vbInformation. 3. vbOKOnly+vbInformation. "Result (/)" 'Display result returned by the Exec method 50: End With In the above example we have shown how to: 1. "Result (+)" 'Display result returned by the Exec method 19: End With 20: With . "Result (-)" 'Display result returned by the Exec method 23: End With 24: With .

0922 100 5. vbOKOnly+vbInformation.5630 0. the more worthwhile it is to use function pointers. dicFunctionHandler(“-”). vbOKOnly+vbInformation.Exec(). vbOKOnly+vbInformation.0674 4.5806 2.This is the method suggested in this paper to implement a function pointer in VBScript.Exec(). vbOKOnly+vbInformation. dicFunctionHandler(“*”). There is also another possible way to call a function implemented with this method. We have also shown how to instantiate such custom classes and load them to a scripting dictionary. dicFunctionHandler(“*”). vbOKOnly+vbInformation.9212 50 2.Exec().1219 Discussion We have seen so far how to implement the Command Wrapper design pattern in VBScript and a “constructor” for a class in VBScript. In a similar fashion. dicFunctionHandler(“-”). vbOKOnly+vbInformation. it is possible to define the Exec methods of the above mentioned classes as Default (by declaring it: Public Default Function) and then the code above can be further reduced to: 1: 2: 3: 4: 5: 6: 'Execute the functions using the Function Handler MsgBox MsgBox MsgBox MsgBox dicFunctionHandler(“+”). together with different ways to call the loaded .0943 Function Pointers 0. vbOKOnly+vbInformation. vbOKOnly+vbInformation. "Result "Result "Result "Result (+)" (-)" (*)" (/)" The readers are encouraged to try to execute the sample code shown in this paper. dicFunctionHandler(“/”).1561 10 0.5308 20 1. as well as a function handler using a scripting dictionary. as follows: 1: 2: 3: 4: 5: 'Execute the functions using the Function Handler MsgBox MsgBox MsgBox MsgBox dicFunctionHandler(“+”). "Result "Result "Result "Result (+)" (-)" (*)" (/)" and this is because the item property is the scripting dictionary‟s default property. Number of Calls Single Regular calls 0. dicFunctionHandler(“/”).Exec(). Performance of Function Pointers A small case study comparing the performance of regular function calls with that of function pointers shows that the more a function is used. as well as to try the method to implement their own functionality.0635 0.

First. The Function Pointer Tutorials. (2005). Lars Haendel. Callbacks and Functors.function via the dictionary key and to retrieve the result. and pinpointed the possible uses and advantages of the method in general and particularly for QTP.. and with Quicktest Pro (QTP) in particular. This can be achieved by returning a string with the name of the function to be called. by means of dynamic loading of code blocks. by implementing a function handler as illustrated above. References Haendel. might be of benefit. The general uses and benefits of function pointers are explained elsewhere (e. it would be possible to build a generic controller component that would enable execution of real keyword-driven scripts. and hence they will not be covered here. 2005). for example. With such a component it would be possible. We have also indicated that this method is.e. equivalent to the implementation of a function pointer in C or C++. Second. Recall that common QTP usage requires the automation developer to add every single function library to the test resources. the method can be used to emulate i. An example for this can be found in Appendix 2. Introduction to C and C++ Function Pointers. to define the flow of the different code blocks in an external file. Conclusion This paper attempted to demonstrate how to implement function pointers in VBScript. for it makes the need for decision structures to analyze the return code of a function obsolete. Future forthcoming articles will further expand on several topics mentioned throughout this paper. It is concluded that the technique can help developers to achieve more efficient and generic design and code. when the system is low in RAM. L. and better run-time resources management. Third.pdf .. which is a central feature of function pointers. Source: http://www. the method presented in this paper should be of great value when the basic hardware configuration is poor. Fourth.newty. the method can be used to emulate event handling. such as an XML file.g. in fact. Please notice that this technique would yield a highly parsimonious coding style. This can be easily done by passing the function handler entry (dictionary item) to another function. In what remains I shall attempt to convey in which cases the implementation of this design pattern in VBScript in general.

As can be seen in the code. Johnson. vbOKOnly+vbInformation. _ 6: vbOKOnly+vbCritical. ". This action is then performed by means of the statement: strNextAction = dicFunctionHandler(strNextAction)(arrArgs). vbOKOnly+vbInformation. the functions are loaded using a generic function (class) loader function (GetFunction). J.. Within the TestFlow Sub. "Login" 7: Exec = "AbortTest" 8: Else 9: MsgBox Join(arrArgs. FirstTest and Logout. In addition. & Vlissides. (1997).Exec function returns the name of the action to be performed (AbortTest). the normal course of the test flow is altered such that the FirstTest action is never executed. vbOKOnly+vbCritical. E.". Helm.Gamma. and since the for loop continues to advance.. R. with their corresponding arguments from arrActionArgs. "Login" 10: Exec = "" 11: End If 12: End Function 13: End Class 14: 15: Class Logout 16: Public Default Function Exec(ByVal arrArgs) 17: MsgBox "Exec". The flow includes three functions: Login. in case of error the Login. 1: Class Login 2: Public Default Function Exec(ByVal arrArgs) 3: 'Add your code here 4: If (Not IsArray(arrArgs)) Then 5: MsgBox "Error: username & password are mandatory parameters. and then called according to their order in the arrRunActions.").. R. "AbortTest" 25: Exec = "Cleanup" 26: 'Add your code here 27: End Function 28: End Class 29: 30: Class FirstTest . "Logout" 18: 'Add your code here 19: End Function 20: End Class 21: 22: Class AbortTest 23: Public Default Function Exec(ByVal arrArgs) 24: MsgBox "Exec". two additional functions (AbortTest and Cleanup) are included for error handling and orderly exiting the test flow. Design Patterns: Elements of Reusable Object Oriented Software. Appendix 1: Event Handling Example We shall show here how to implement an event handler in VBScript for a typical login flow in QTP. Addison-Wesley Publishing.

LBound(arrArgs) + 1 = 0) Then 'If no args are found. pass an empty string arrArgs = "" End If 'If the next command is empty If (strNextAction = "") Then 'Run the next planned action strNextAction = dicFunctionHandler(arrRunActions(ix))(arrArgs) Else 'Run the action returned by the previously call action strNextAction = dicFunctionHandler(strNextAction)(arrArgs) End If Next End Sub Call TestFlow(Array("Login". "Logout"). "FirstTest".Dictionary") Set arrArgs = CreateObject("Scripting. "Logout". "FirstTest". "AbortTest".31: 32: 33: 34: 35: 36: 37: 38: 39: 40: 41: 42: 43: 44: 45: 46: 47: 48: 49: 50: 51: 52: 53: 54: 55: 56: 57: 58: 59: 60: 61: 62: 63: 64: 65: 66: 67: 68: 69: 70: 71: 72: 73: 74: 75: 76: 77: 78: 79: 80: 81: 82: 83: 84: Public Default Function Exec(ByVal arrArgs) MsgBox "Exec".Dictionary") 'Load the required functions With dicFunctionHandler For ix = LBound(arrLoadActions) To UBound(arrLoadActions) . GetFunction(arrLoadActions (ix)) Next End With 'Run the required flow strNextAction = "" For ix = LBound(arrRunActions) To UBound(arrRunActions) 'Get the action arguments arrArgs = split(arrActionArgs(ix). vbOKOnly+vbInformation. _ Array("Login".") If (UBound(arrArgs) . ix.Add arrLoadActions (ix). ". "")) .123456". "Cleanup" 'Add your code here End Function End Class 'This generic function will load any class Public Function GetFunction(ByVal strFunctionName) Execute "Set GetFunction = New " & strFunctionName End Function 'This sub will run the flow Public Sub TestFlow(ByVal arrLoadActions. Array("User. arrArgs. ByVal arrRunActions. "Cleanup"). vbOKOnly+vbInformation. ByVal arrActionArgs) Dim dicFunctionHandler. strNextAction Set dicFunctionHandler = CreateObject("Scripting. "FirstTest" 'Add your code here End Function End Class Class Cleanup Public Default Function Exec(ByVal arrArgs) MsgBox "Exec". "".

when done carefully and selectively. the question whether it is “Kosher” to change the run-time properties of the AUT (application under test) was given new life in SQAForums (e. QTP doesn‟t recognize this tab-control. So here it is: In past few days.Appendix 2: Implementing a Callback with Function Pointers We shall show here how to implement a callback with the classes defined in Appendix 1 and used in this paper. RO Vs THE QTP SHELL Update: this is an article from the old site that wasn‟t transferred to the new one. this sucks. while not having any testing value by themselves. for two main reasons (beside being an ugly solution): It tends to break (Click events are often block by focus shifting. and I think an example will illustrate why: Say our application has some input fields. and it is very . On the other hand. that could otherwise fail our script. that calls for serious discussion.155 3: 4: 'Now. 114)). residing within a tab-control.Click X Y. The example used here will be the calculation of the total amount plus the tax on the sum of several items prices. "Result (Tax)" 8: True. _ 7: vbOKOnly. It‟s a tough question. CONST_DBL_VAT)). setting RO properties can give us a robust way of doing certian tasks. I think this opinion is quite easy to understand.g. it becomes obvious that the only method that will work is TabControl.). and could miss UI bugs a user would have encountered. but it is very useful. 56. it could cause serious bugs. by dynamically loading the functions without the function handler (as shown earlier in this article): 5: 'Execute the (*) function on the result of the (+) function to calculate the tax on an item 6: MsgBox GetMultiply(Array(GetSum(Array(23. 78. Thus. and after many attempts to solve the problem elegantly. here). 95. I side with the latter opinion. backstage behavior should be tested via unit-tests). these task could safely get us to a position where we could do some real testing. Now. On the one hand. 1: 'Define a constant with the tax value multiplier 2: Const CONST_DBL_VAT = 1. the syntax looks complicated. slow system behavior etc. divided among various tabs. messing with the application‟s RO objects has no testing value (not emulating user behavior.

different tab layout) We paid for it with: A. we learn that the process works the other way as well – changing the property via QTP. we ask ourselves if we could miss UI bugs due to working backstage. and find out that when the user switches the active-tab. It doesn‟t test the tab control. so we try thinking outside the box. makes the control bring the relevant tab to the front. NEVER on a data-grid control). add a new tab. to sum-up. At the end of the day. change the resolution or the font.Object. After a little creative fiddling. run a few tests of ourselves. where we could rip the application apart. and switch. Just to be clear – I agree we do need to be selective and careful about applying this methond (e. and the script breaks). we gained: A. B. Zero-maintenance growth and change (handles “out of the box” New tabs.g. this is unacceptable. A much more robust script (no . OK. We can run through the tab collection. find the tab with the relevant name (By looping the TabControl.Tabs collection). And this seems like a pretty good balance to me. A generic script (serves multiple systems with various fonts. and after a while. We ask the programmers.VERY demanding from a maintenance point of view (just change the tab-order. but it makes sure we‟ll get to the right tab. It suddenly seems very tempting to just set the RO property whenever we want to switch tabs. VERY small possibility for missing tab-switching UI bugs due to not actually pressing the tab control. do a littlie investigating.) C. and answer a reasonable NO (since any bugs will cause the next step of the script to fail). good-old-fashion QTP style. different tab ordering. get its index. So. Moreover. we become confident that no new bugs will be caused by this. but we shouldn‟t abandon it all together. Here comes the “carefully and selectively” part (which is REALLY important): we make damn sure that setting the object‟s RO property doesn‟t break anything.Click breaking the script) B. the tab control‟s inner object change its ActiveTab property to the new tab‟s index. resolutions etc. we can then decide that tab navigation will be done via RO manipulation. So. VERY small possibility for creating new tab-switching bugs due to messing around with the RO objects. .

QTP descriptive programming (DP) and the Dictionary object to pack together GUI objects with their corresponding business oriented functions. Implementing a GUI Layer with Classes Abstract This article describes a powerful technique that exploits Object Oriented Design Patterns. but many times also on the individual personalities involved. The article includes a valuable bonus: a highly effective tip that enables to exit a test smoothly. I will describe an expansion of the OR concept that is compatible with OO principles – the GUI Layer. then what is the optimal way to implement it?” are quite ubiquitous and the answers given can vary depending on the particular characteristics of the project. which is a set of attributes and values that serve as criteria to .You can read more about RO manipulating techniques in our article about automating custom controls. Subsequently. Questions such as: “Should we use an Object Repository (OR) or Descriptive Programming (DP)? if an OR is chosen. Introduction A central issue in automation development is how to reduce the effort spent on maintenance. preventing QTP from getting stuck when it fails to identify GUI objects during runtime. This concept has been adopted by SOLMAR‟s automation experts based on the observation that it is possible to maximize code reusability (and thus boosting maintainability) by undertaking an OO approach that breaks an automation project into several abstraction levels. I shall attempt to show that QTP‟s Object Repository does not fit well with such principles and what is the impact of this on automation development viz-a-viz costeffectiveness and maintainability. then should we use a shared OR or a local OR for each Action? If DP is selected. A test object stores the description of the referenced object. In this article I will analyze the concept of Test Objects in the context of Object Oriented principles. Test Objects and Run-Time Objects A test object encapsulates a reference to a run-time object – the real world object that is instantiated in the application under test (AUT).

QTP is able to identify a GUI object among all the objects currently loaded to the machine‟s RAM. insomuch that the above account leaves us with an incomplete picture. but at the end of the day we need to perform actions on Runtime objects. It is true that the OR. QTP uses such a description to query the OS if there‟s an object currently loaded to the machine‟s RAM. if you noticed the bdb suffixed files in QTP tests. AutoIt. Following this line of thought. then. Test Objects and the Object Repository The above account of test objects makes it seem only natural to think of them as data entities.locate the right object during the test run session. slim and tall. the OS returns the address of the object (a reference or pointer) and hence QTP gains access to the object‟s public methods and properties. as you would with the brunette. then note that bdb actually stands for Berkeley Data Base – an Oracle product).). Though this description may seem overly simplified. and will be wearing a red dress and shoes”. if lucky!). which essentially is exactly what the Object Repository is (a side note. since the private methods and properties are hidden from view by definition (so QTP never makes progress to the private domain. A more detailed account of the distinction between Test Objects and Run-Time Objects is available in Yaron Assa‟s article “Differences and Connections between Runtime Objects and Test Objects” (2009). What. I will explain below why. The difference is that in this case. What do I mean by this? Based on a description composed of a set of properties and values. This description is pretty much like the one we keep in mind to identify our blind date partner at the meeting time (“I‟m brunette. seems to be the problem with the OR approach? Tests Objects are really data entities. it seems only natural to have these entities – Test Objects – stored in a database. Test Complete. etc. if used properly. Moreover. basically it is this process that enables us to interact with the GUI (and other) objects using QTP or other automation tools (Test Partner. reflects a best practice according to which we ought to store the description of each GUI (Test) Object only once to reduce . it is the OS (Windows). the one that returns the record. not the DB. this record contains a single field that stores a reference to the actual runtime object. If the answer is positive. you‟ve been told on the phone). This is similar to the retrieval of a particular record from a database table based on a SQL WHERE clause. Rational Robot. Similarly.

Given that GUI changes are made quite regularly from one AUT version to the next. redundant. In fact. So. classes mostly are representations of . Because automated tests are. as aforesaid. But. And this is a relatively good result. in general. the aforementioned line of analysis lead me to the conclusion that something in the OR concept is faulty regarding the manageability of a large-scale automation project. changes in the AUT would require matching changes in both the OR and the scripts that refer to its test objects. then using an OR would be an excellent solution. The Object Oriented View The Object Oriented software paradigm is based on the basic concepts of encapsulation. such as keeping separate versions of the OR that match each AUT version and using configuration management software in the automation project. in order to achieve this a great effort must be invested also into managing the automation project properly. regressive by nature. for example. but one is maintaining the scripts for the last version and the other is developing new scripts for the newest one. Moreover. it will not be too long until the OR becomes cluttered with new. there are solutions to such situations. Of course. as well as in the data sources that feed these scripts. inheritanceand polymorphism. If the common situation would have been that only the object descriptions changed from one AUT version to the next. not developed. more often than not. test objects required by the developer working on the newest version. as well as the input data and expected results data. For instance. this requires good project management. GUI changes reflect modifications in the way the AUT actually functions. and the package through which we achieve this is called a class. because ad-hoc requests and resource limitations can endanger the integrity of such a precious resource. keeping versions of the OR leaves one issue still open.maintenance costs. The worst case would be one where each developer would change in turn the descriptions of existing objects to match their requirements. then maintenance would certainly pertain not only to the OR but also that the code that implements the actual GUI manipulations and verifications. However. damaging irrevocably the ROI on the automation project as a whole. Encapsulation basically means to pack together functionality and data structures that belong together. which is not always available. which are many times also accompanied by even deeper changes – in the database structure. Taking into account the fact that scripts are most of the time maintained. suppose that two automation developers work simultaneously with a shared repository. However.

For example. as well as others like getCustomerAge and getCustomerBalance which would perform a calculation based on the class fields current values and then return the result. It is recognized as one approach that makes the resulting code more entities (like Customer.e. They enable the code developer to determine which fields (also called properties or attributes of the class) and methods will be actually accessible to the world outside the class (public). However in QTP these two last concepts of inheritance and polymorphism cannot be implemented based on the VB Script language which provides very rudimentary support for working with classes. Product. In OO programming languages like C++ and Java. which assign and retrieve the value of the respective field. Inheritance is deeply related to one of the major goals of the OO approach – reusability. firstName. The OO methodology is not new and has been widely put into practice in the software design and development industry. getCustomerId. etc. phoneNo. For instance.) together with functions such assetCustomerId. The difference between a fully featured class and a mere data structure (as in the C programming language) is that the class also wraps the functions available for use with the class data fields. we might need to handle numbers of different types (float. reusability comes into play by means of the ability to device a new class that “inherits” the fields and methods of a previously defined class (also called a base class) and expands on these according to the specific requirements that raised the need for the new class. we would use the same interface in both cases. Hence in our code that uses these functions we would not need to use casting. lastName. and which will remain for internal (private) use of the class members (i. yes. with the correct process ultimately invoked by the runtime environment. we shall see later that this is not a reason to refrain from using classes in testing automation.). extensible and. scalable. maintainable. These are commonly referred to as the classmethods. Polymorphism is yet another powerful concept that enables one to design more than one version of a function (with the same name but different number or types of arguments) to be able to handle transparently different situations within the application context. a typical class for a Customer would pack the data fields that define the customer as a data entity (customerId.. readable. Nevertheless. The public and private notions mentioned above are of great importance with regard to encapsulation and inheritance. also more . etc. the class fields and methods). int) and so instead of having a single function with conditional statements that check for the value type that was passed. we‟ll have several functions with the same name but different signatures (different type of arguments).

Of course. even more so. The task of automating tests should not be treated differently than any other content specific automation task. Put it in other words. Members of the AUT‟s development team do . which should guide the automation developer in the implementation of the required code. Not surprisingly. indeed. or robot. So basically any block of code is a kind of automation device. Testing Automation and Software Development One thing I have witnessed throughout my career is that QA professionals of all levels treat testing automation as just another testing activity. This is because the automation developer faces challenges that are usually not felt by the developers of the AUT. Scripts that carry out operations on GUI objects – such as QTP tests – are not different than any other piece of software. or should approach. computer programs that perform operations instead of humans implement automation. How this relates to the way we approach. First. the automation developer must have an overall view of the AUT. Generally speaking. in fact. it is not rare to find automation professionals that think likewise since many times the role of automation. as the automation scripts may cover a large part of the AUT‟s main functionality. then an automation project should be treated and managed as any other development project and. Sometimes this is even reflected by the job title given to the automation staff: “automatic tester” is one of the absurd titles I have encountered several years ago. If so. this belief is a true misconception of the essence of testing automation. a testing automation project is. making good use of the methodology requires deep analytical skills that enable the code designer to infer correctly from the requirements of the software under construction which are the appropriate entities involved and how they are interrelated. As with any software product. an automation project also has its own SRS (Software Requirements Specifications) document: the STD (Software Test Design) “document” (or tests design in a quality management tool such as HP‟s Quality Center or Orcanos‟ QPack).testable (as huge pieces of functionality are broken down into smaller. self-contained capsules or packages). as I shall explain in what follows. a specific kind of software development project. the testing automation challenge? Let us delve into it below. This reflects a misunderstanding of the role of the Automation Developer and. Some of the main challenges are the following: 1.

approach to do it using the most widely accepted development method – Object Oriented – to attain the best possible results? In what follows I will describe a method to implement automation “scripts” based on an extension to the OR concept – the GUI Layer. But. which is based on solid OO principles. 3. as is the case with third-party and custom controls. especially the GUI Layer concept. with scripts spread all around the place. may be it would be more appropriate to call it the GUI-Business Bridge Layer. In general. why should one fall again and again victim to the fallacy of treating an automation project as a trivial task (does “record-replay” remind you of something?). let us take a look at the concept of developing code in layers.. following the above discussion. I will illustrate below how such a layer can be built. I think we may conclude that an automation project should be definitely managed as a development project. but it is already accustomed among the experts to call it a GUI Layer. as the automation scripts do not possess the flexibility and ingenuity of a human tester during runtime. and what are the benefits gained from adopting such an approach to testing automation.e. In other words. Now. the test objects proper) and the Business or Application Layer. and also the AUT‟s behavior may pose a real technological challenge regarding the identification of the objects by QTP (or other tools). I shall define a GUI Layer as a set of classes that pack (encapsulate) together the interfaces required to manipulate the AUT‟s GUI objects in each application context. In a sense. as the division of labor among the different teams is typically coordinated by the team leaders and a project manager. where the opposite is true? Why not. layers are useful to maximize reusability (recall the previous discussion on OO principles). the automation scripts should be mapped to the test design.not necessarily need this. If this is so. then. Many times solutions that extend the basic capacities of the tools are required. So a developer can focus on the part assigned to him and do it well even without having in depth knowledge of the whole system. quite often. Following the above exposition. 2. Third. to keep it short. The Concept of Layers I hope to have managed so far to make clear why the OR approach. is far from being the optimal approach. Second. of which we shall have more to say later. it is a set of classes that bridge between the AUT‟s GUI (i. Implementing the GUI Layer . as they should emulate the steps done by a human tester. automation developers find out that the test design leaves many open issues that need to be resolved beforehand. the GUI controls used by the development team.

As Login ' 'Owner: ' John Doe ' 'Date: ' dd-MMM-yyyy ' '------------------------------------------------------------------------------Dim objLogin Set objLogin = New Login Set CreateLogin = objLogin '------------------------------------------------------------------------------End Function '------------------------------------------------------------------------------- The second step is. we define a class. Now. obviously.Dictionary to store the references to the test objects contained in the window. which are containers of other GUI objects. the windows (pages in a Web application). .e. For each of these entities. as follows: '------------------------------------------------------------------------------Public Function CreateLogin() '------------------------------------------------------------------------------'Function: CreateLogin 'Creates an instance of the Login class ' 'Remarks: ' 'Arguments: ' N/A ' 'Returns: ' Object . dialogs. it is also required to define the following function that will return an instance of a GUI layer class (a kind of constructor function). to define the members of each class.. Because QTP does not allow for direct instantiation of classes defined in external vbs files with the operator New. a container of other GUI objects. as aforesaid. we shall make use of the Scripting.Encapsulating Test Objects in Classes Let us take a testing automation project on a typical AUT and see how the solution should be designed according to the approach outlined above. and popup messages. since each class is. for example: Class Login End Class Class MainWindow End Class Class CreateCustomer End Class and so on for each of the application contexts. The first step would be to make a simple list of all application GUI contexts – i.

For this purpose. the first member I shall introduce here will be common to all GUI Layer classes. I will define a public method within the class called Init. as follows: '------------------------------------------------------------------------------- . and I will define it as m_htChildObjects. which is what the dictionary really is).Dictionary End Class and so on for each of the application contexts (ht stands for HashTable. The private member m_htChildObjects will be accessed through the class property ChildObjects. This property is defined as follows: '------------------------------------------------------------------------------'Property: ChildObjects 'Get and Set the m_htChildObjects member field ' 'Remarks: ' R/W ' 'Arguments: ' dic ' 'Returns: ' m_htChildObjects As HashTable ' 'Owner: ' John Doe ' 'Date: ' dd-MMM-yyyy ' '------------------------------------------------------------------------------Public Property Get ChildObjects() '------------------------------------------------------------------------------Set ChildObjects = m_htChildObjects '------------------------------------------------------------------------------End Property '------------------------------------------------------------------------------'------------------------------------------------------------------------------Public Property Let ChildObjects(ByRef dic) '------------------------------------------------------------------------------Set m_htChildObjects = dic '------------------------------------------------------------------------------End Property '------------------------------------------------------------------------------- The third step is to define the objects contained within each context. (the Dictionary object has been already extensively discussed in other articles published at AdvancedQTP„s knowledge base).dialog or page. for example: Class Login Private m_htChildObjects 'As Scripting. So.Dictionary End Class Class MainWindow Private m_htChildObjects 'As Scripting.

Add "Submit".WebButton("outertext:=Submit") End With 'IsContextLoaded is a function that iterates through the Dictionary and checks if the GUI objects "exist" Init = IsContextLoaded(ChildObjects) '------------------------------------------------------------------------------End Function '------------------------------------------------------------------------------- The code snippet above shows a typical Init method for a GUI Layer class for a Web application Login page. It is thanks to this encapsulation method that we ensure that GUI objects are always defined at a single place.Public Function Init() '------------------------------------------------------------------------------'Function: Init 'Initializes the context and child objects ' 'Dependencies: ' IsContextLoaded(htContext) ' 'Remarks: ' N/A ' 'Arguments: ' N/A ' 'Returns: ' True/False ' 'Owner: ' John Doe ' 'Date: ' dd-MMM-yyyy ' '------------------------------------------------------------------------------ChildObjects = CreateObject("Scripting.Login") .Add "Browser". Browser("name:=My App") .Add "Page". ChildObjects("Page").WebEdit("html id:=Password") .Add "Username". IsContextLoaded is defined in a separate common library. as follows: .Dictionary") With ChildObjects . ChildObjects("Browser"). ChildObjects("Page").Add "Password".Page("title:=My App \. ChildObjects("Page").WebEdit("html id:=Username") . and their identity is defined using Descriptive Programming (DP). The test objects are added as entries to the ChildObjects Dictionary. The reader can easily infer the analogy to the OR. At the end of the function body you will notice that it returns the result of a call to the function IsContextLoaded which accepts as argument the Dictionary that stores the ChildObjects.

SOLMAR Knowledge Networks Ltd. strDetails. ' 'Date: ' 11-Nov-2008 ' 'See Also: ' '------------------------------------------------------------------------------Dim ix. This function is generic and it is used in the projects I .ReportEvent intStatus." & strAdditionalRemarks Next '--------------------------------------------------------------------------Reporter." End If strDetails = strDetails & " found.Items keys = htContext.Keys For ix = 0 To htContext.As HashTable ' 'Returns: ' True/False ' 'Owner: ' Meir Bar-Tal. strDetails '------------------------------------------------------------------------------End Function '------------------------------------------------------------------------------- And it returns True if all objects defined in the Dictionary are identified.Exist(0) strDetails = strDetails & vbNewLine & "Object #" & ix+1 & ": '" & keys(ix) & "' was" If IsContextLoaded Then intStatus = micPass strDetails = strDetails & "" strAdditionalRemarks = "" Else intStatus = micWarning strDetails = strDetails & " not" strAdditionalRemarks = " Please check the object properties.'------------------------------------------------------------------------------Public Function IsContextLoaded(ByRef htContext) '------------------------------------------------------------------------------'Function: IsContextLoaded 'Checks that the current GUI context is loaded ' 'Iterates through the htContext (HashTable) items and executes the Exist method with 0 (zero) as parameter. or False if at least one object is not found. keys. items. strAdditionalRemarks '--------------------------------------------------------------------------items = htContext. ' 'Remarks: ' N/A ' 'Arguments: ' ByRef htContext .Count-1 IsContextLoaded = IsContextLoaded And items(ix). "IsContextLoaded".

Another benefit of this method is that it points exactly to the object we need to recheck and update. SetPassword and Submit.manage to ensure that QTP does not get stuck while attempting to perform some operation on a non-existing GUI object. For example. These are shown below: '------------------------------------------------------------------------------Public Function SetUsername() '------------------------------------------------------------------------------'Function: SetUsername 'Set the Username field ' 'Dependencies: ' N/A ' 'Remarks: ' N/A ' 'Arguments: ' N/A ' 'Returns: ' N/A ' 'Owner: ' John Doe ' 'Date: ' dd-MMM-yyyy ' '------------------------------------------------------------------------------ChildObjects("Username"). making maintenance much easier. Encapsulating Business Methods in Classes The next step after defining the child objects of the GUI context is to define the operations required to perform the application or business scenarios within the given context. This is easily done by implementing class methods.Set GlobalDictionary("Username") '------------------------------------------------------------------------------End Function '------------------------------------------------------------------------------'------------------------------------------------------------------------------Public Function SetPassword() '------------------------------------------------------------------------------'Function: SetPassword 'Set the Password field ' 'Dependencies: ' N/A ' 'Remarks: . the login class outlined above would need the following methods to begin with: SetUsername.

and the use of the ChildObjects property to retrieve through the test object a reference to the runtime object.Set GlobalDictionary("Password") '------------------------------------------------------------------------------End Function '------------------------------------------------------------------------------'------------------------------------------------------------------------------Public Function Submit() '------------------------------------------------------------------------------'Function: Submit 'Presses the Submit button ' 'Dependencies: ' N/A ' 'Remarks: ' N/A ' 'Arguments: ' N/A ' 'Returns: ' N/A ' 'Owner: ' John Doe ' 'Date: ' dd-MMM-yyyy ' '------------------------------------------------------------------------------ChildObjects("Submit"). .' N/A ' 'Arguments: ' N/A ' 'Returns: ' N/A ' 'Owner: ' John Doe ' 'Date: ' dd-MMM-yyyy ' '------------------------------------------------------------------------------ChildObjects("Password").Click 'TODO: Verify data submission performed successfully '------------------------------------------------------------------------------End Function '------------------------------------------------------------------------------- Notice the use of the GlobalDictionary to retrieve the values required by the functions.

objLogin Set objLogin = CreateLogin() If objLogin.SetUsername() objLogin. which implements an application scenario building on the strong foundations of the GUI Layer.The next step would be to move on to the Business Layer.SetPassword() objLogin. we could wrap it with the following function: '------------------------------------------------------------------------------Public Function do_login() '------------------------------------------------------------------------------'Function: do_login 'Implements the business logic of the do_login Action. as mentioned above.Submit() 'If login succeeds intStatus = micPass Else intStatus = micFail End If do_login = intStatus '------------------------------------------------------------------------------End Function '------------------------------------------------------------------------------- Notice the use the Login class outlined above and of its Init function as a precaution to ensure the GUI context is loaded. the code within the function above is easy to understand. For instance to perform the Login function based on the above example. If changes are made to the GUI objects of a given context. and not get stuck. and is not cluttered with the references to both the OR test objects and data sources as quite often is the case. As you can also see. ' 'Remarks: ' 'Arguments: ' None ' 'Returns: ' Status ' 'Owner: ' John Doe ' 'Date: ' dd-MMM-yyyy ' '------------------------------------------------------------------------------Dim intStatus. then the changes will be concentrated within a single package. both with respect to the object properties and .Init() Then objLogin.

Yet another gain from this method is standardization. For example: 'VB Script Document Option Explicit '------------------------------------------------------------------------------Class do_login '------------------------------------------------------------------------------'Class: do_login 'Encapsulates the do_login the functionality required to manipulate the context‟s child objects. By implementing code this way we achieve a high degree of homogeneity in the code written by different developers. ' 'Remarks: ' 'Owner: ' John Doe ' 'Date: ' dd-MMM-yyyy ' '------------------------------------------------------------------------------'------------------------------------------------------------------------------'Methods '------------------------------------------------------------------------------'------------------------------------------------------------------------------Public Default Function Run() '------------------------------------------------------------------------------'Function: Run 'Implements the business logic of the do_login Action. and thus enhancing the manageability of the automation project. An advanced alternative to the last example is to pack such a Business Layer function using the Command Wrapper Design Pattern. as outlined in my article Function Pointers in VB Script (revised). ' 'Remarks: ' 'Arguments: ' None ' 'Returns: ' Status ' 'Owner: ' John Doe ' 'Date: ' dd-MMM-yyyy ' '------------------------------------------------------------------------------Dim intStatus Set objLogin = CreateLogin() .

Such a controller device was developed by me together with my partners at SOLMAR Knowledge Networks as part of our generic Object Oriented comprehensive automation framework – My System. readability. extensibility and testability.Init() Then objLogin.Submit() 'If login succeeds intStatus = micPass Else intStatus = micFail End If Run = intStatus '------------------------------------------------------------------------------End Function '------------------------------------------------------------------------------'------------------------------------------------------------------------------End Class '------------------------------------------------------------------------------- Adopting this method would enable the implementation of an advanced generic controller that loads its flow from an external data source such as an XML file.SetPassword() objLogin. I tried to convey that logically following this line of thought leads to the conclusion that an automation project must be approached as a software development project par excellence.If objLogin. scalability. Summary This article has reviewed an alternative approach to code implementation in a testing automation project that is based on object-oriented principles. I have shown that automation scripting should not be treated differently than software development. Future articles will expand on this theme and guide the readers into how to gain from the implementation of other design patterns within the framework laid out in this article.SetUsername() objLogin. and suggested an expansion to the OR concept – which was shown as inadequate viz-a-viz the OO paradigm – to encapsulate the interfaces to the GUI objects: the GUI Layer. Moreover. and explained in detail the benefits of adopting this approach to obtain the maximum ROI from an automation project regarding maintainability. The article has provided a practical example of how to implement such a layer and how to invoke it using a Business Layer. .

in our application under test).. etc. nativeclass. QTP creates a corresponding Test Object and stores it in the Object Repository. QTP builds the “all items” property out of the combobox runtime object‟s available items collection. which represent real-world application objects “out there” (i. The QTP Test Object Shell Under their fancy name. The general idea is usually clear enough. So for example. a Window test object contains properties which allow QTP to identify it in the “real world”: text. . By using a window test object with a text property of “Notepad”. application combobox runtime object has no such property. Window. it is derived from it..Differences and Connections between Runtime Objects and Test Objects There is a lot of confusion about how the concepts of Runtime Objects andTest Objects are used in QTP. and explain all the nitpicking involved in all the commands and practices relevant to the matter. Whenever we record a real-world object (also known as a Runtime object). so even though the property does not exist in the runtime object. Test Objects refer to your everyday QTP entities. Test Objects roles Test objects play several roles in QTP. It is important to understand that the test object‟s properties and methods are not really “out there” in the application‟s runtime object.e. the most immediate one is object identification. while the actual . but are only derived from it. sometimes even the experts do not quite know if using the GetROProperty method on a TO will work. For example. Browser – these are all QTP constructed test objects. Click. a SwfComboBox Test Object has the property “all items”. Maximize. but when it comes down to the actual details. This article will guide you through the general concepts. as well as to perform standard operations on it and with it. we tell QTP to look for a runtime window object with text = “Notepad”. it also contains methods to operate it: Close. height. We can easily see these methods and properties via the object spy‟s Test Object tab. on top of these. VBCheckbox. The Test Object contains QTP specific properties and methods which allow us both to identify the relevant runtime object during playback.

This means that unlike the GetTOProperty and GetTOProperties commands. QTP will translate the test object‟s simple commands to the runtime object‟s commands required to perform the task at hand. Every time we maximize a window. Like GetTOProperty.GetTOProperty("text") The GetTOProperty command will retrieve the value as it was originally recorded (or created via DP). ItemSelected. However. GetTOProperty allows us to retrieve the value of a test object property. The test object‟s simple properties and methods act as a bridge. the corresponding SwfComboBox test object provides a much more simpleand standard “Select” method which does the trick for you. and raising several events (SelectionChanged. TextChanged. QTP will touch the . we do it through the QTP test objects. etc. SetTOProperty and GetROProperty. GetTOProperties returns a collection with all the test object properties. GetTOProperties. Working with Test Objects How can we work with test objects in our scripts? The most straight-forward way is to simply use them. GetROProperty allows us to get the current value of a test object property. events and properties. or if that value was updated in “the real world” since the object was recorded. SelectedItem). this command will print out “Notepad”: Msgbox Window("text:=Notepad"). only the test object which represents it. sparing us the need to nitpick our way through the runtime object‟s unknown commands. and perform the relevant action on it.Net combobox usually involves changing several properties (SelectedIndex. While the application runtime objects might be extremely complex. select a value from a VBComboBox or click a WebElement.Another important role is standardization. or create instant test objects via Descriptive Programming. For example. there are 4 special commands which allow us to access the core of QTP‟s test object mechanism: GetTOProperty. the corresponding QTP test objects are standard and very simple in comparison.). the GetTOProperties command has nothing to do with the actual runtime object in our application. For example. It does not matter if the corresponding runtime object exists. We can either use prerecorded test objects from the object repository. Aside from straightforwardly using our test objects to perform actions. QTP will then locate the corresponding “real” runtime object. GetROProperty requires the test object‟s corresponding runtime object to exist. selecting a value in a .

GetROProperty("text") It is important not to be confused by the “RO” in the command name. if the text of the Notepad window changed from when that object was recorded. this command will retrieve the updated value: Msgbox Window("Notepad"). or even when you go in and out of actions. It is important to note that changing a test object‟s properties might cause QTP not to identify its corresponding runtime object. In the following example. Any changes made with SetTOProperty will be reset once the test-run had finished. For example. and retrieve the value of the property from it.GetROProperty("text") Unlike GetTOProperty and GetTOProperties. Msgbox Window("nativeclass:=Notepad"). it does not even matter if the test object originally recorded the relevant property. and it will not find any object matching that description. From Test Objects to Runtime Objects Test objects are the cornerstone of all QTP object operations.runtime object. "incorrect value") Window("Notepad"). our test object has only one property – nativeclass. . some combo-boxes might appear as SwfObjects. Even though it has RO (Runtime Object) in it. There are two situations in which we might prefer working with the actual runtime objects of the application. the test objects it creates do not have the properties or methods that are required to operate the objects (like “all items” and Select). or generic ActiveX controls.GetROProperty("all items") Last but not Least.Net combobox runtime object does not have an “all items” property. as opposed to the QTP test objects: There are some objects (especially . So for example: Call Window("Notepad"). So even though a . and it will print out all the available items: Msgbox SwfWindow("X"). you could still execute the following command. SetTOProperty allows us to change a test object‟s property for the duration of the test-run.Net custom controls). Here it makes no difference if QTP succeeds to correctly recognize the object. which QTP fails to recognize correctly. combo-boxes). the command still retrieves only test object properties.SetTOProperty("nativeclass". Another case is when we are required to perform some non-standard operation with an object. but they are sometimes too limited for the task at hand.Close 'this command will fail The second command will fail as QTP will search for an object with nativeclass = “incorrect value”. but GetROProperty will still be able to retrieve the value of the window‟s text property (where GetTOProperty would return an empty result). For example. As QTP fails to recognize the object for what they are (in this example.SwfCombobox("Y").

these commands will print the same value: Print Browser("X"). WebList ("z").Object property. WebList ("z"). we can find out the color of a WebList‟s items text: Print Browser("X"). A good example for this case is trying to find the font style of a WebElement.SelectedIndex = 1 . If it is a .Color We can even use the runtime object‟s methods. It is important to note that WebList test object does not have a selectedIndex property. So in this case. and perform operations that are otherwise unavailable to us: Print Browser("X").netobject.Object. WebList ("z").Object. it can be done via their . and print its value. we‟ll still be able to select an item from it. WebList ("z").Page("Y"). Of course that in order for this to work the runtime object must exist when we execute the combobox is identified as a SwfObject.Page("Y").SwfObject("Y"). Working with Runtime Objects You can see an object‟s runtime properties and methods in the RO tab of the object spy. regardless of QTP‟s ability to recognize them for what they truly are. you can also use the .selectedIndex Print Browser("X"). This property exposes all the properties and methods of the runtime object “hiding” behind our test object.Object.Object.CurrentStyle.focus By accessing the runtime world. but if they do.Page("Y"). So even if our .GetROProperty("selected item index") The true benefit of working with runtime objects lies with properties and methods that are not available through the QTP test object. So for the corresponding test object will only provide us with a standard set of commands and properties. The WebElement test object simply does not carry the information we need. Not all test objects support working with their corresponding runtime objects.Page("Y").Page("Y"). SwfWindow("X"). and so we have to resort to unusual measures such as working with the WebElement‟s runtime object. by overwriting the runtime property of the selected item‟s index. access its selectedIndex property. only a derived property called “selected item index”. WebList ("z").Net form spy to get a more detailed look of those properties that contain inner complex objects.Object. For example: Print Browser("X").selectedIndex This command will find the runtime object corresponding to the WebList‟s test object. we can perform almost any operation on our objects.

In any language. The only way to get the error message in such cases is by actually performing the code. it is unclear how to operate the object. without one having the slightest clue in its regard. and exactly what properties and methods it has (CurrentStyle. Even when we find the right properties or methods. in contrast to languages such as C/C++. All programming languages suffer from such problems. Adding a Call-Chain Mechanism to QTP Background and motivation A common frustrating experience is having your script pop-up an error dialog in some long-forgotten function. For example. Unlike the standard and simple test objects. it is not long until the calls to functions and object methods become too deeply nested for us humans to grasp. it is important to remember that working directly with runtime objects can have significant downsides. using them “from behind the scenes” may cause application errors and invoke hidden bugs.Color was hard to come by).With all their benefits. that is. and carefully mapping the consequences of changing runtime properties. whereas in C++ it would trigger a compilation error. in which compilation at least guarantees that the function calls are syntactically correct. calling the wrapping function. a faulty call to a function (wrong function name or number of parameters) would pass unnoticed in VB Script when part of a function. such as exploring custom controls. or by testing the inner function call on a standalone basis. This is because in VB Script compilation is done on the basis of a line-after line interpretation during run-time. but nonetheless. but in late bound languages like VB Script this problem is really challenging. we must always be aware of them. What usually follows is a series of trial-and-error breakpoint runs to determine which action the script was actually trying to perform when executing the function call that triggered the error. . There are ways to overcome these shortcomings.

Developed by our people at SOLMAR‟s R&D Division. I thought that I could share some of my techniques and thoughts on the subject. this will render your report cluttered and hence difficult to grasp. and so on up to the root of the call hierarchy.Having said that. the answer is no. it is possible to implement a call-chain in QTP with intensive reporting – just by sending a line to the report from any function as you enter and exit it. stay tuned!). . though it‟s not trivial. Possible Implementations Now. They manage to do so via a dedicated mechanism: the call-chain (sometimes referred to as the call-stack). even when bugs and error occur within extremely nested function calls. Is the inevitable conclusion that there is no way to implement a call-chain in QTP effectively? Well. which function called that function. There is a way. However. indeed. Figure 1: A Sample Visual Studio Error Call-Stack Just imagine how many debug runs you could have saved just by knowing the exact order of calls which lead you to the current function. The call-chain shows us exactly which function called the currently executing function. Please notice that it shows both the functions and code lines that precipitated the error. This allows us to analyze the error‟s path. and that is exactly why the call-chain data is crucial. Moreover. My SystemTM brings the latest advances to boost ROI on testing automation (We shall have much more to say on that in future posts. Meanwhile. programmers do debug their code. how valuable would it been to know which parameters were sent into those function calls. QTP reports are inaccessible during the run-session. Or. An example of a Visual Studio call-stack for an error can be viewed in Figure 1 below. A call-chain mechanism is just one of the rich features provided by SOLMAR‟s flagship product: My SystemTM. and see where things started to go wrong (usually 2-3 function calls before the function we are currently in).

A place to store the call-chain data. and an easy to use storage for the call chain. A mechanism for viewing the stored data mid-run (we won‟t get into this one – it is basically just a simple window to peek at the stored data) If you have a robust mechanism for updating the call-chain when you are exiting and entering contexts. A stack can store data (i. Here is an example of how the stack mechanism would work: Let‟s say our code went though these functions: Function Func1 Call Func2 End Function Function Func2 Call Func3 End Function Function Func3 Dim x Call Func 4 x = 1/0 End Function . the names of the contexts you happen to enter during the flow) in a FILO manner – First-In Last-Out. 3. sub or action). I do believe they can point you in the right direction for developing robust solutions of your own.e. then implementing the call-chain will be quite straightforward. A mechanism for updating the call-chain when you enter a context (by context I mean a function. Storing the Call-Chain Data An excellent mechanism for storing call-chain data is a stack. This will make sure your call chain contains all the relevant data needed to understand what got you until this point. The Concept Developing an effective call-chain requires four basic components: 1. 4.Though the examples given here are not meant to be used or to be an out-of-the-box solution. 2.. A mechanism for updating the call-chain when you exit a context. and nothing else.

and take a look at our stack. as the stack mechanism always know to remove the top level item. “Func2”. So it should look something like this (assuming our data is stored in an oChainData stack storage. once the code will exist Func4. If you‟d like to know exactly how to implement a stack. where we could debug. At this point.Function Func4 'Ended End Function If we call Func1.. as shown in the following example: Function Func1 'Add to call chain oChainData. Line 14 will result is an error. you can take a look at Dani Vainstein‟s excellent article on the matter – here.Remove End Function Notice that we don‟t have to specify the function name for our Remove command. “Func3”.. with add and remove commands): Function Func1 'Add to call chain oChainData. The naive approach would be to simply perform an add command once we enter a function. Now Func4 will end. which would hold just enough data to understand how we got into Func3. and no irrelevant data (for example. and a removecommand every time we exit it... our call-chain stack would look like this: (“Func1”. it will call Func2. ' Function body ' . make it: (“Func1”. returning the control to Func3. it will remove the last item from our stack. “Func3”). we better start recording it.Add "Func1" . but usually our code is more complex than this – usually our functions have multiple exit gates. A Naive Approach to Updating the Call-Chain Data on the Run Well. and it would call Func4. Problems with the Naive Approach That is all fine and well. Since our call chain is a Stack. which would call Func3.] 'Remove from stack oChainData. “Func4”).Add "Func1" '[. after we got our own storing mechanism for the call-chain data. the fact the we have entered and exited Func4). “Func2”.

oChainData. we still run the risk of a mid-function error that will throw us out..Remove Exit Function 'More Code. anything we write within the Class_Terminate sub of the class will be executed when the class object is destroyed.Remove End Function When our function has multiple exit gates. oChainData. but we can do the exit part quite easily.. What these examples show is that we need an automatic component that will “listen” to our function. but perhaps we can overcome this with more complex scripting. we could use the termination event of an object. oChainData. Implementing the whole package (monitor both entering and exiting a function) might be hard.. before letting us update the call-chain data... So. for example: Class KillSwitch Sub Class_Terminate Msgbox "Object terminated" End Sub End Class Set oKill = New KillSwitch Set oKill = Nothing .Remove Exit Function 'Now the regular exit gate: oChainData. and that would just make our whole stack misleading and useless. 'If structures etc.... And even if our code is perfect (and it never is). But such errors are exactly our motivation to be willing to put an effort in maintaining a call-chain mechanism in the first place! A More Robust Solution We have seen that our naive solution fails at some basic everyday cases.Remove Exit Function 'More Code.'Code. When we write a class.. In order to achieve that.. it is just a matter of time before we forget to update the call-chain... 'If structures etc. 'If structures etc. and tell us (or rather the call-chain) when we enter and exit it.

Add "Func1" 'Update the chain-data Set oUpdater = New ChainUpdater 'Create an instance of the kill switch 'Now. Since the object will be destroyed whenever we exit the function (either purposefully. The main concept explained how we can keep track of the chain-data. it builds upon the same basic principles demonstrated in this article. We can use this to our advantage – instead of popping up a message box. While it is much more detailed and effective. Although the article did not provide a detailed example of a call-chain. and if you happen to dare and design. As aforementioned. or due to an error). SOLMAR Knowledge Networks has developed an automation framework with a built-in call-chain mechanism. As a closing word. the object “knows” when it is destroyed. about this article. we don‟t have to worry about “forgetting” to update the call-chain. to share with the community your own call-chain mechanism! . We examined an alternative approach by which call-chain update is achieved automatically through an object‟s kill-switch mechanism. It could look something like this: 'The blueprint for the updater Class ChainUpdater Sub Class_Terminate oChainData.Remove End Sub End Class Function Func1 Dim oUpdater 'This will hold the exit kill-switch oChainData.'Now the message box will appear As you can see. I hope that it has successfully outlined how to build the main components that are required in order to implement such a mechanism. let me encourage you to share your thoughts and comments about the call-chain concept. let us make our object update the call-chain. We have seen that the naive approach (manually update on entering and exiting a context) is impractical. no matter when we exit the function. the kill switch will be activated 'And the chain-data will be updated End Function Summary This article introduced the concept of a call-chain and provided substantial reasons for its centrality in the automation development effort.