This section discusses about how to identify an error that has occurred during script execution?

Sometimes, scripts may abort automatically during execution, if errors are encountered. Let us say for example, the eGTest script has encountered such errors. To identify the errors for further debugging, do the following:

  1. Click on the eGTest- 1 script executable from the Exe tree of the Recorder window. The context sensitive right panel will display the properties associated with this script. By default, the On_Error option available under the Behavior section will be Kill_End. Double clicking the Kill_End option will enable a drop down list. Select the Learning option from this list and then click on the Start button (see Figure 1).

    Figure 1 : Setting the OnError option to Learning through the Recorder window

  2. Alternately, you can right click on the eGTest- 1 in the Exe tree and select the Load option. The Player window will then appear with the Script Properties. From here too, you can change the OnError option from Kill_End to Learning and click the Start button (see Figure 2).


    Figure 2 : Setting the OnError option to Learning through the Player window

  3. The script will now be played back and if it encounters any errors, a pop up window will appear displaying the details of the error.  The exact location of the error in the VB script i.e., the line at which the error has occurred can be identified from the Action Line field of Figure 2. Likewise, there may be errors related to the captured images and the actionable events i.e., the associated mouse clicks. In such cases, the pop up window will display the exact error location.


    Figure 3 : The Error pop up window

  4. Clicking on the Ok button in Figure 3 will return you back to the Player window, which reports ExecutionError in the Status text box (see Figure 4).

    Figure 4 : The Player window with the error status message

This way, you can identify the errors that were encountered during script execution.