HP QTP Utility Statements : UnregisterUserFunc Statement
September 10, 2018
HP QTP Utility Statements : UnregisterUserFunc Statement
Welcome to this post! – ” HP QTP Utility Statements :UnregisterUserFunc Statement”.
If you are looking for HP UFT, QTP utility statements and their usages, then you are at right place. This post “HP QTP Utility Statements : UnregisterUserFunc Statement” consists of concept discussion and usage discussion. Go ahead and enjoy reading…
This discussion will help you prepare well if you are going for the interview and can help you if you need the function to be used in your project test suite.
UnregisterUserFunc Statement
Abstract
The UnregisterUserFunc statement is used to de-register the previously registered function or method. This method could have been used for some special requirement. The statement in itself falls under the category of utility statements and not utility objects.
Remember there is a difference between utility statements and utility objects.
Before we dig down deep into the usage let’s quickly visit some general questions.
In the interview usually, you might be questioned in different ways like:
- How to unset custom method for any control class?
- Can you use the UnregisterUserFunc statement by calling some other methods in external function file?
- What are the objects and parameters of UnregisterUserFunc statement?
- Is UnregisterUserFunc an object or statement?
Discussion
This is the most used and discussed statement in QTP. The UnregisterUserFunc statement instructs QTP or UFT to stop using the current registration of the method. If the unregistered method is a defined test method for the object, the functionality of the method returns to the standard QTP functionality.
Point to Note here:
- If you register a function within a reusable action, it is recommended that you de-register the method at the end of the action.
Syntax
UnRegisterUserFunc TOClass, MethodName
Let’s see the parameters and their usage description for this statement:
Argument | Type | Description |
TOClass | String | The test object class for which you want to unregister the method. |
MethodName | String | The method you want to unregister. |
Example
Suppose that the Web page contained a Country edit box, and by default, the box contained the value USA. The following example registers the Set method to use the MyCustomSet function in order to report the default value of the edit box to the run results before the new value is entered. After using the registered method in a WebEdit.Set statement for the Country edit box, the UnRegisterUserFunc method is used to return the Set method to the standard QuickTest functionality.
'UnRegisterUserFunc example Function MyCustomSet (obj, x) dim y y = obj.GetROProperty("value") Reporter.ReportEvent micDone, "previous value", y MyCustomSet=obj.Set(x) End Function RegisterUserFunc "WebEdit", "Set", "MyCustomSet" Browser("MercuryTours").Page("FindFlights").WebEdit("Country").Set "Africa" UnRegisterUserFunc "WebEdit", "Set"
This brings us to the end of our discussion on “HP QTP Utility Statements : UnregisterUserFunc Statement”.
I really hope you have enjoyed reading this short post. If you have any doubt on this please feel free to add your comment below.
And if you like to read more on UFT or QTP Technical Interview Questions please follow below links:
UFT Technical Interview Questions – Set 1
UFT Technical Interview Questions – Set 2
How to Download Resource From QC\ALM?
How to Upload Resource To QC\ALM?
Or if you prefer General Interview Questions please follow below links:
UFT General Interview Questions – Part 1
UFT General Interview Questions – Part 2
If you would like to keep track of further articles on UFT (QTP). I recommend you to SUBSCRIBE by Email and have new UFT articles sent directly to your inbox.