photo credit: larryzou@

Automated tests are created mainly to be run unattended, and this raises a few concerns for automation developers. Assume a situation where you initiated your test-suite while leaving your office to be run over-night. However, because of unforeseen errors, your test stops at a point and disrupts your results. When you return to your desk the next day, only to find that your tests aren’t completely executed. This can be quite frustrating, and its crucial to be proactive and handle such errors before they impact your work.

This article discusses a way of creating a Recovery Scenario for an instance where an item in the list item or menu is not found.

In this example, we will define a Function Call and use that Function Call to handle the error. The default syntax for the Recovery Scenario Function is:

Function fnRecovery(Object, Method, Arguments, retVal)
        'Error Handling Code
End Function

Explanation of each argument to fnRecovery is given below:

Object as Object: The object of the current step.
Method as String: The method of the current step.
Arguments as Array: The actual method's arguments.
Result as Integer: The actual method's result.

To handle this scenario, we will use the function below:

Function Recovery_ListItemIsNotFound(Object, Method, Arguments, retVal)
     Dim sAllItems, arrAllItems, intItem
 
     With Object
          'Retrieve all items from the Listbox
          sAllItems = .GetROProperty("all items")
          'Split 'all items' using a delimiter ";" into an array
          arrAllItems = Split(sAllItems, ";")
 
          'Select a random number
          intItem = RandomNumber.Value(LBound(arrAllItems), UBound(arrAllItems))
          .Select "#" & intItem
 
          Reporter.ReportEvent micInfo, "ListItemIsNotFound", "Item: " & .GetROProperty("value")
     End With
End Function

Recovery_ListItemIsNotFound, as the same suggests, executes the Recovery Operation if the list item that we supplied to our target WebList does not exist. This is quite common in Web applications, and Items in a WebList can change depending upon the input(s) provided.

To start, Click Resources -> Recovery Scenario Manager. You should see a window like this:

Recovery Scenario Wizard

In the window, click the following button:

Doing so will invoke the Recovery Scenario Wizard:

Recovery Scenario Wizard - Welcome

When the window above opens:

1. Click Next
2. Select Test Run Error as the Trigger Event
   
   
3. Click Next
4. Select ‘Test Run Error: Item in list or menu not found in the Error Listbox
   
   
5. Click Next twice and navigate to Recovery Operation
   
   
6. Select Function Call and Click Next
   
   
7. Select a library which will store our Recovery Function.
   
   
8. Select ‘Define New Function’ and in the TextArea, paste the function Recovery_ListItemIsNotFound
   
   
   

   Define New Function

9. Click Next
10. Make sure ‘Add Another Recovery Scenario’ Checkbox is not selected and click Next again.
    
    
11. Under Post-Recovery Test Run Options, select proceed to next step.
    
    
12. Give your scenario a name and Click Next
    
    
13. And finally, Check the following option: Add Scenario to current test and Click Finish. Save Changes before closing.

We will use the WebList below to select a value that does not exist in it; so, let’s write a code to select Rational Robot. If you view the items present in the listbox, you will notice that Rational Robot indeed doesn’t exist, but our Recovery Scenario will handle the error when we select it. Instead, it will select a random value from the list.

QuickTest ProLoadRunnerFunctional TesterSelenium

Browser("title:=.*Recovery Scenario.*").Page("micclass:=Page")_
    .WebList("name:=testTools").Select "Rational Robot"
 
MsgBox "Item Selected: " & Browser("title:=.*Recovery Scenario.*").Page("micclass:=Page")_
	.WebList("name:=testTools").GetROProperty("value")

When the code above executes, you will notice that, instead of throwing a Test Run Error, a random value from the list box was selected. You will know that the Recovery Scenario was triggered and ran successfully when you view the Test Results:

Recovery Scenario Executed

There are plenty of other scenarios as well, and I will try to cover some of the important ones. If you have any suggestions, or a scenario that you would like me to cover first, please use the comments section of this post to share your ideas/thoughts with me. Thanks! :)

If you have any questions, please ask them in the comments section. If your query is confidential, please use the Contact Form to send me an e-mail instead.

Tagged as: Function Call, Item in list not found, Item in menu not found, Iten in list or menu not found, QTP Recovery Scenario, QTP Test Run Error, Recovery Scenario, Test Run Error