Studio:Scripting Overview - Revision history

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

2009-08-20T23:45:35Z

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

← Older revision		Revision as of 23:45, 20 August 2009
Line 108:		Line 108:
	<div class="references-small"><references/></div>		<div class="references-small"><references/></div>

	[[Category:Scripting]]		[[Category:Studio:Scripting]]

2009-08-18T22:11:49Z

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

2009-02-12T17:55:39Z

The Role of Scripting in STRIDE Studio

← Older revision		Revision as of 17:55, 12 February 2009
Line 1:		Line 1:
	=The Role of Scripting in STRIDE Studio=		=The Role of Scripting in STRIDE Studio=

	Scripting (running programs implemented in a supported scripting language) is fundamental to performing tests within STRIDE Studio.		Scripting (running programs implemented in a supported scripting language) is fundamental to performing tests within [[STRIDE Studio]].

	STRIDE makes it possible to use scripts written in either JScript or Perl<ref>S2 Technologies provides full support for Microsoft JScript and Active State Perl, however, other languages that support COM Automation have been used successfully. Contact S2 Technologies for more information.</ref>, to perform test-related tasks.		STRIDE makes it possible to use scripts written in either JScript or Perl<ref>S2 Technologies provides full support for Microsoft JScript and Active State Perl, however, other languages that support COM Automation have been used successfully. Contact S2 Technologies for more information.</ref>, to perform test-related tasks.

2008-10-15T00:31:15Z

The Role of Scripting in STRIDE Studio

← Older revision		Revision as of 00:31, 15 October 2008
Line 19:		Line 19:
	! Injected Object !! Perl Variable Name !! JScript Variable Name		! Injected Object !! Perl Variable Name !! JScript Variable Name
	\|-		\|-
	\| '''studio''' \|\| <code>$main::studio</code> \|\| <code>studio</code>		\| '''[[STRIDE_Studio\|studio]]''' \|\| <code>$main::studio</code> \|\| <code>studio</code>
	\|-		\|-
	\| '''ascript''' \|\| <code>$main::ascript</code> \|\| <code>ascript</code>		\| '''[[AutoScript\|ascript]]''' \|\| <code>$main::ascript</code> \|\| <code>ascript</code>
	\|-		\|-
	\| '''testSuite''' \|\| <code>$main::testSuite</code> \|\| <code>testSuite</code>		\| '''[[Reporter#reporter.Suites.Item\|testSuite]]''' \|\| <code>$main::testSuite</code> \|\| <code>testSuite</code>
	\|-		\|-
	\| '''reporter'''<br><div style="font-size:80%">(rarely used directly in STRIDE Studio)</div>\|\|<code>$main::reporter</code> \|\| <code>reporter</code>		\| '''[[Reporter\|reporter]]'''<br><div style="font-size:80%">(rarely used directly in STRIDE Studio)</div>\|\|<code>$main::reporter</code> \|\| <code>reporter</code>
	\|}		\|}

	Each object presents an object model through which you can perform needed operations and get/set desired properties. For details of each object model, ~~see '''Online Help''' installed with STRIDE Studio~~.		Each object presents an object model through which you can perform needed operations and get/set desired properties. For details of each object model, click on the links above.

	=Controling STRIDE Studio from a Script=		=Controling STRIDE Studio from a Script=

2008-03-07T17:06:57Z

← Older revision		Revision as of 17:06, 7 March 2008
Line 22:		Line 22:
	\|-		\|-
	\| '''ascript''' \|\| <code>$main::ascript</code> \|\| <code>ascript</code>		\| '''ascript''' \|\| <code>$main::ascript</code> \|\| <code>ascript</code>
			\|-
			\| '''testSuite''' \|\| <code>$main::testSuite</code> \|\| <code>testSuite</code>
	\|-		\|-
	\| '''reporter'''<br><div style="font-size:80%">(rarely used directly in STRIDE Studio)</div>\|\|<code>$main::reporter</code> \|\| <code>reporter</code>		\| '''reporter'''<br><div style="font-size:80%">(rarely used directly in STRIDE Studio)</div>\|\|<code>$main::reporter</code> \|\| <code>reporter</code>
	\|-
	~~\| '''testSuite''' \|\| <code>$main::testSuite</code> \|\| <code>testSuite</code>~~
	\|}		\|}

2008-03-07T17:06:22Z

← Older revision		Revision as of 17:06, 7 March 2008
Line 77:		Line 77:
	Script syntax is available for navigating complex payloads comprising structures, unions, arrays and pointers.		Script syntax is available for navigating complex payloads comprising structures, unions, arrays and pointers.

	For additional details, see [[Using Scripts to Automate Software Testing]].		For additional details and example scripts, see '''[[Using Scripts to Automate Software Testing]]'''.

	=Reporting from a Script=		=Reporting from a Script=
Line 103:		Line 103:
	It is also possible to switch between your target function implementation and your script implementation at runtime.		It is also possible to switch between your target function implementation and your script implementation at runtime.

	For additional details, see '''[[Using Scripts to Simulate Missing Software Units]]'''.		For additional details and example scripts, see '''[[Using Scripts to Simulate Missing Software Units]]'''.

	=Notes=		=Notes=

2008-03-05T23:21:28Z

Mocking Target C Functions Using a Script

← Older revision		Revision as of 23:21, 5 March 2008
Line 102:		Line 102:

	It is also possible to switch between your target function implementation and your script implementation at runtime.		It is also possible to switch between your target function implementation and your script implementation at runtime.

			For additional details, see '''[[Using Scripts to Simulate Missing Software Units]]'''.

	=Notes=		=Notes=

2008-03-05T23:09:34Z

A Typical Scenario

← Older revision		Revision as of 23:09, 5 March 2008
Line 77:		Line 77:
	Script syntax is available for navigating complex payloads comprising structures, unions, arrays and pointers.		Script syntax is available for navigating complex payloads comprising structures, unions, arrays and pointers.

	For additional details, see [[Using ~~Script~~ to Automate Software Testing]].		For additional details, see [[Using Scripts to Automate Software Testing]].

	=Reporting from a Script=		=Reporting from a Script=

2008-03-05T23:09:15Z

A Typical Scenario

← Older revision		Revision as of 23:09, 5 March 2008
Line 76:		Line 76:

	Script syntax is available for navigating complex payloads comprising structures, unions, arrays and pointers.		Script syntax is available for navigating complex payloads comprising structures, unions, arrays and pointers.

			For additional details, see [[Using Script to Automate Software Testing]].

	=Reporting from a Script=		=Reporting from a Script=

2008-03-04T20:01:51Z

← Older revision		Revision as of 20:01, 4 March 2008
Line 91:		Line 91:
	An overall report is created automatically by STRIDE Studio after all scripts in the workspace have run. The report's native format is XML, which is commonly transformed to locally-viewable HTML using an XSL script when test are run interactively, or uploaded to a server and aggregated when test are run unattended.		An overall report is created automatically by STRIDE Studio after all scripts in the workspace have run. The report's native format is XML, which is commonly transformed to locally-viewable HTML using an XSL script when test are run interactively, or uploaded to a server and aggregated when test are run unattended.

	=Mocking ~~target~~ C Functions Using a Script=		=Mocking Target C Functions Using a Script=
			Mocking (simulating) a target C function comprises two steps:

			# Implement the required functionality in a script
			# Register the script as the function's ''Owner''

			Registering as the function ''Owner'' causes the STRIDE runtime to route all calls to the function to the script implementation.

			It is also possible to switch between your target function implementation and your script implementation at runtime.

	=Notes=		=Notes=