Difference between revisions of "Studio:Debugging Helps"

From STRIDE Wiki
Jump to: navigation, search
m
m
Line 39: Line 39:
 
Note that the single argument to the '''PrintMessage()''' function will accept any expression that perl can interpret as a string. Shown below is output from the sample script.
 
Note that the single argument to the '''PrintMessage()''' function will accept any expression that perl can interpret as a string. Shown below is output from the sample script.
  
 
+
<center>
 
[[Image:PrintMessageOutput.jpg]]
 
[[Image:PrintMessageOutput.jpg]]
 +
</center>
  
 
=== MessageBox() ===
 
=== MessageBox() ===
Line 64: Line 65:
 
The displayed message box can be customized in several ways; see online help and autosense for details. Shown below is output from the sample script.
 
The displayed message box can be customized in several ways; see online help and autosense for details. Shown below is output from the sample script.
  
 +
<center>
 
[[Image:MessageBoxOutput.jpg]]
 
[[Image:MessageBoxOutput.jpg]]
 +
</center>
  
 
= Exception Messages =
 
= Exception Messages =
 
Most calls to STRIDE scripting objects will throw an exception to indicate that an error has occured. The descriptions that accompany these exceptions can be very helpful in identifying the source of the error and correcting it.
 
Most calls to STRIDE scripting objects will throw an exception to indicate that an error has occured. The descriptions that accompany these exceptions can be very helpful in identifying the source of the error and correcting it.
  
 
+
<center>
 
[[Image:ExceptionDialogExample.jpg]]
 
[[Image:ExceptionDialogExample.jpg]]
 +
</center>
  
 
To ensure that these errors are seen by your perl script, be sure to follow the  [[How_do_I_get_Perl_scripts_to_emit_fatal_errors_when_a_COM_error_occurs%3F|recommendation here]].
 
To ensure that these errors are seen by your perl script, be sure to follow the  [[How_do_I_get_Perl_scripts_to_emit_fatal_errors_when_a_COM_error_occurs%3F|recommendation here]].

Revision as of 17:41, 4 February 2008

Script Debugging Techniques

Listed here are some simple debugging techniques that will aid in understanding and troubleshooting scripts that drive STRIDE tests.

As you work through the training scripts, you may find it helpful to insert one or more of the following debugging helps as an aid in understanding the flow of execution or to investigate the value of variables and expressions as the script runs.

PrintMessage()

The studio object provides a way to perform printf-style debugging of scripts running within STRIDE Studio.

PrintMessage allows you to log messages from running scripts and view the values of variables during script execution.

perl example

Here's an example of its use in a perl script:

my $funcs = $main::ascript->Functions;

# loop through each captured function
foreach (0..($funcs->Count - 1)) {
   my $f = $funcs->Item($_);
   # send output to Studio Messages window
   $main::studio->Output->PrintMessage("function item ".$_." ".$f->Name);
}

JScript example

Here's and example of its use in JScript:

var funcs = ascript.Functions;

for (var i = 0; i < funcs.Count; i++)
{
    var f = funcs.Item(i);
    studio.Output.PrintMessage("function item " + i + " " + f.Name);
}

Note that the single argument to the PrintMessage() function will accept any expression that perl can interpret as a string. Shown below is output from the sample script.

PrintMessageOutput.jpg

MessageBox()

The ascript object provides a way to interrupt script execution and display a modal message box containing a message you specify.

Here's an example of its use in a perl script:

my $funcs = $main::ascript->Functions;

# loop through each captured function
foreach (0..($funcs->Count - 1)) {
   my $f = $funcs->Item($_);
   # send output to Studio Messages window
   $main::ascript->MessageBox("function item ".$_." ".$f->Name,
                              "Debug Output");
}


Here's an example of its use in JScript:

The displayed message box can be customized in several ways; see online help and autosense for details. Shown below is output from the sample script.

MessageBoxOutput.jpg

Exception Messages

Most calls to STRIDE scripting objects will throw an exception to indicate that an error has occured. The descriptions that accompany these exceptions can be very helpful in identifying the source of the error and correcting it.

ExceptionDialogExample.jpg

To ensure that these errors are seen by your perl script, be sure to follow the recommendation here.