Studio:Debugging Helps - Revision history

Timd at 23:36, 20 August 2009

2009-08-20T23:36:15Z

← Older revision		Revision as of 23:36, 20 August 2009
Line 96:		Line 96:
	''This is not the case in '''perl'''''. 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]].		''This is not the case in '''perl'''''. 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]].

	[[Category:Studio:Troubleshooting~~/Debugging~~]]		[[Category:Studio:Troubleshooting]]

Timd: Text replace - 'Category:Troubleshooting' to 'Category:Studio:Troubleshooting'

2009-08-20T23:33:39Z

Text replace - 'Category:Troubleshooting' to 'Category:Studio:Troubleshooting'

← Older revision		Revision as of 23:33, 20 August 2009
Line 96:		Line 96:
	''This is not the case in '''perl'''''. 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]].		''This is not the case in '''perl'''''. 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]].

	[[Category:Troubleshooting/Debugging]]		[[Category:Studio:Troubleshooting/Debugging]]

Timd: Debugging Helps moved to Studio:Debugging Helps

2009-08-18T22:08:35Z

Debugging Helps moved to Studio:Debugging Helps

← Older revision	Revision as of 22:08, 18 August 2009
(No difference)

Ivailop: /* PrintMessage() */

2009-02-12T17:53:24Z

PrintMessage()

← Older revision		Revision as of 17:53, 12 February 2009
Line 4:		Line 4:
	== PrintMessage() ==		== PrintMessage() ==

	The '''studio''' object provides a way to perform printf-style debugging of scripts running within STRIDE Studio.		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.		PrintMessage allows you to log messages from running scripts and view the values of variables during script execution.
Line 42:		Line 42:

	[[Image:PrintMessageOutput.jpg\|frame\|none\|Sample PrintMessage() Output]]		[[Image:PrintMessageOutput.jpg\|frame\|none\|Sample PrintMessage() Output]]


	== MessageBox() ==		== MessageBox() ==

Ivailop: /* Sample Output */

2008-10-15T00:27:22Z

Sample Output

← Older revision		Revision as of 00:27, 15 October 2008
Line 79:		Line 79:

	=== Sample Output ===		=== Sample Output ===
	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 [[AutoScript]] for details. Shown below is output from the sample script.


	[[Image:MessageBoxOutput.jpg\|frame\|none\|Sample MessageBox() Output]]		[[Image:MessageBoxOutput.jpg\|frame\|none\|Sample MessageBox() Output]]


	= Exception Messages =		= Exception Messages =

Timd at 23:52, 4 March 2008

2008-03-04T23:52:14Z

← Older revision		Revision as of 23:52, 4 March 2008
Line 11:		Line 11:
	Here's an example of its use in a perl script:		Here's an example of its use in a perl script:

	<~~pre~~>		<source lang="perl">
	my $funcs = $main::ascript->Functions;		my $funcs = $main::ascript->Functions;

Line 20:		Line 20:
	$main::studio->Output->PrintMessage("function item ".$_." ".$f->Name);		$main::studio->Output->PrintMessage("function item ".$_." ".$f->Name);
	}		}
	</~~pre~~>		</source>

	=== JScript example ===		=== JScript example ===
	Here's and example of its use in JScript:		Here's and example of its use in JScript:

	<~~pre~~>		<source lang="javascript">
	var funcs = ascript.Functions;		var funcs = ascript.Functions;

			// loop through each captured function
	for (var i = 0; i < funcs.Count; i++)		for (var i = 0; i < funcs.Count; i++)
	{		{
	var f = funcs.Item(i);		var f = funcs.Item(i);
			// send output to Studio Messages window
	studio.Output.PrintMessage("function item " + i + " " + f.Name);		studio.Output.PrintMessage("function item " + i + " " + f.Name);
	}		}
	</~~pre~~>		</source>

	=== Sample Output ===		=== Sample Output ===
Line 48:		Line 50:
	Here's an example of its use in a perl script:		Here's an example of its use in a perl script:

	<~~pre~~>		<source lang="perl">
	my $funcs = $main::ascript->Functions;		my $funcs = $main::ascript->Functions;

Line 58:		Line 60:
	"Debug Output");		"Debug Output");
	}		}
	</~~pre~~>		</source>

	=== JScript example ===		=== JScript example ===
	Here's an example of its use in JScript:		Here's an example of its use in JScript:

	<~~pre~~>		<source lang="javascript">
	var funcs = ascript.Functions;		var funcs = ascript.Functions;

			// loop through each captured function
	for (var i = 0; i < funcs.Count; i++)		for (var i = 0; i < funcs.Count; i++)
	{		{
	var f = funcs.Item(i);		var f = funcs.Item(i);
			// send output to the Studio Messages window
	ascript.MessageBox("function item " + i + " " + f.Name,		ascript.MessageBox("function item " + i + " " + f.Name,
	"Debugging output");		"Debugging output");
	}		}
	</~~pre~~>		</source>

	=== Sample Output ===		=== Sample Output ===

Timd at 17:02, 29 February 2008

2008-02-29T17:02:07Z

← Older revision		Revision as of 17:02, 29 February 2008
Line 94:		Line 94:
	''This is not the case in '''perl'''''. 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]].		''This is not the case in '''perl'''''. 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]].

	[[Category:~~Scripting~~]]		[[Category:Troubleshooting/Debugging]]

Timd at 00:57, 8 February 2008

2008-02-08T00:57:44Z

← Older revision		Revision as of 00:57, 8 February 2008
Line 1:		Line 1:
	= Script Debugging Helps =		= Script Debugging Helps =
	Listed here are some simple debugging techniques that will aid in understanding and troubleshooting scripts that drive STRIDE tests.		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() ==		== PrintMessage() ==

Timd at 00:56, 8 February 2008

2008-02-08T00:56:26Z

← Older revision		Revision as of 00:56, 8 February 2008
Line 96:		Line 96:
	''This is not the case in '''perl'''''. 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]].		''This is not the case in '''perl'''''. 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]].

	[[Category:~~Training~~]]		[[Category:Scripting]]

Timd: TestScripts DebuggingTechniques moved to Debugging Helps

2008-02-08T00:50:58Z

TestScripts DebuggingTechniques moved to Debugging Helps

← Older revision	Revision as of 00:50, 8 February 2008
(No difference)