SilkTest Workbench: Why am I unable to debug .Net scripts immediately after runtime error?

SilkTest Workbench: Why am I unable to debug .Net scripts immediately after runtime error?

If a run-time error occurs during playback of a Workbench .Net Script and assuming you have not defined an error handler in your script, the test will be terminated and the following error dialog will be displayed:


If you click 'Debug' on this dialog, the script will be opened and the code that threw the error will be highlighted as shown in the following screenshot:

Although it may appear that Debug mode has been entered, it will not be possible to use any debugging functions such as 'Step Into', 'Run to Cursor' or 'Set Run Pointer/Next Statement'. Any action that you take at this point will result in the immediate termination of the .Net script.

This is the expected behavior when running Workbench .Net Script, as unlike Visual Basic it is not possible to continue debugging a .Net script immediately after a run-time error. You therefore have to stop the script before you can enter debugging mode proper, at which time all of relevant functions should be available.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2014-10-10 19:24
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.