Skip to main content

Error Handling in QTP

As we have 3 types of error handling methods in pure VB or VBA language, we can easily handle our errors like Try/Catch functionality. They are,
On Error Resume Next
On Error GoTo 0
On Error GoTo <LABEL>
But VBScript supports only 2. They are

On Error Resume Next
On Error GoTo 0
So here we are going to talk about these  2 handlers.


1. On Error Resume Next
This enables the vb error handler and whenever dynamic run time error occurs, it will collect the error information and continue with the next immediate statement. This won't stop the script execution when error occurs.
  1. On Error Resume Next
  2. Dim a
  3. a = 5 / 0   'this will give run time error - Divide by zero error
  4. msgbox "Script not stopped."
  5. msgbox Err.Description
So here 2 msgbox lines got executed. At the same time we are able to get the error information like I did in line 5. So you can check the error numbers and you can control your scripts in better way like,
  1. On Error Resume Next
  2. Dim a
  3. a = 5 / 0   'this will give run time error - Divide by zero error
  4. If Err Then
  5.     msgbox "Error occurs: " + Err.Number + "; " + Err.Message + "; " + Err.Description
  6. End If
Here is the list of Error codes
http://www.csidata.com/custserv/onlinehelp/vbsdocs/vbs241.htm
Also we will get negative error numbers also.


2. On Error GoTo 0
This is the default handler in VB. This will disables the handler and collects the error information and throw the error in msgbox. Mostly no one will use this.


Then, You can raise your custom error like,
  1. On Error Resume Next
  2. Err.Clear  'Use this to clear previously stored error info
  3. Dim a
  4. a = 5 / 0   'this will give run time error - Divide by zero error
  5. If Err.Number <> 0 Then
  6.   'Err.Raise code, message, description
  7.  Err.Raise 100"Please change the value""Division by Zero error occurs"
  8. End If
Don't forget to put Err.Clear as your error object may contain previously stored error info.

Comments

Popular posts from this blog

Change IE Browser ZOOM settings

Lot of UI automation testers could have faced this problem as we could change the zoom settings while operating manually for our convenience and forgot to reset to 100%.
But our QTP and some other related tools would operate the browser perfectly if browser zoom is 100%. So wee need to change the zoom before start to run the scripts. Its better to have a code snippet in our framework to change this zoom setting right?
Here we go...

1. We can simply change the Registry values before Invoking IE
Function ChangeRegistry Dim objShell Set objShell = CreateObject("WScript.Shell")  objShell.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Zoom\ZoomFactor", "100000", "REG_DWORD" Set objShell = Nothing EndFunction This option is very useful. But in real time, lot of customers could have restricted write access to windows registry. So we can try other options.

2. Use IE COM object and Change Settings
Function ChangeIEZoom Dim intZoomLevel, objIE  intZoo…

QTP - Object Identification - Prerequesties

While starting a new project or proof of concept or after new QTP installation, we would face the issue in identifying objects as QTP built objects like WinList, WebEdit, etc.; instead everything will be identified as WinObject.

Here are some steps to ensure you did the environment setup RIGHT before start automating.
Did you enabled required Add-ins only while launchingDid you selected "Record >> Record and Run Settings" - This should be based on what type of application you are working with
Windows app - Windows >> Record and run test on any windows applications. Web app - Web >> Record and run test on any open browser.
Did you tried to launch UFT/QTP and then AUT.If its web, ensure browser zoom level set to 100%Try disabling the protected mode in IE for web.Launch UFT and AUT using RUN AS ADMINISTRATORAlso see the Object Identification Methods if you are interested.

Run JavaScript from QTP

Yeah, You can run your pure JavaScript from QTP using RunScript method. Lot of times, we are in need of firing events or simulating actions on web page which is not supported by QTP. At that time, you can use your direct DOM methods and directly execute your script on the web page from QTP like,
Dim MyPage, SearchBox Set MyPage = Browser("title:=Google").Page("title:=Google") Set SearchBox = MyPage.RunScript("document.getElementsByName('q')(0);") SearchBox.Value="testing"
'if objects available in frames, Set SearchBox = MyPage.RunScript("document.frames(4).document.getElementsByName('q')(0);")
'OR
Set objFrame = Browser("title:=Google").Page("title:=Google").Frame("title:=something")
objFrame.RunScript("document.getElementsByName('q')(0);") Also, you can execute by obtaining actual browser window object if you have IE app like, Dim IEApp Set IEApp = CreateObject("Internet…