Studio:Using Scripts to Simulate Missing Software Units - Revision history

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

2009-08-20T23:46:13Z

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

2009-08-18T22:10:09Z

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

2009-03-24T19:09:57Z

Notes on the Examples

← Older revision		Revision as of 19:09, 24 March 2009
Line 12:		Line 12:
	* the generated target IM code for the function must contain a ''proxy'' (which enables calls from the target to the host).		* the generated target IM code for the function must contain a ''proxy'' (which enables calls from the target to the host).

	Further, if the function's IM code contains a ''dynamic delegate'', a test script can dynamically switch ownership of the function implementation between the target and the host while running. The script implementing the mock function does not have to change regardless of the location of its caller.		Further, if the function's IM code contains a ''remote interceptor'' (formal ''dynamic delegate''), a test script can dynamically switch ownership of the function implementation between the target and the host while running. The script implementing the mock function does not have to change regardless of the location of its caller.

	=Perl=		=Perl=

2009-02-12T17:57:52Z

← Older revision		Revision as of 17:57, 12 February 2009
Line 1:		Line 1:
	This note describes how to simulate (mock) a function using a script in ~~Stride STUDIO~~. This technique is useful when a target-based function you are testing has a dependency on another function that has not been written yet, makes use of unavailable hardware resources, or can't be used for some other reason.		This note describes how to simulate (mock) a function using a script in [[STRIDE Studio]]. This technique is useful when a target-based function you are testing has a dependency on another function that has not been written yet, makes use of unavailable hardware resources, or can't be used for some other reason.

	Example code is given in both Perl and JScript demonstrating how the mock script is set up by the test script and how the script receives function calls from the STRIDE runtime.		Example code is given in both Perl and JScript demonstrating how the mock script is set up by the test script and how the script receives function calls from the STRIDE runtime.

2008-03-18T16:29:09Z

LeapYearMock.pl

← Older revision		Revision as of 16:29, 18 March 2008
Line 407:		Line 407:

	==LeapYearMock.js==		==LeapYearMock.js==
	~~==LeapYearMock.pl==~~
	LeapYearMock.js is an implementation of the function we are mocking. The mock function's implementation can be found in '''IsLeapYear()'''; the rest of the script handles housekeeping for the STRIDE runtime.		LeapYearMock.js is an implementation of the function we are mocking. The mock function's implementation can be found in '''IsLeapYear()'''; the rest of the script handles housekeeping for the STRIDE runtime.

2008-03-11T16:09:28Z

← Older revision		Revision as of 16:09, 11 March 2008
Line 2:		Line 2:

	Example code is given in both Perl and JScript demonstrating how the mock script is set up by the test script and how the script receives function calls from the STRIDE runtime.		Example code is given in both Perl and JScript demonstrating how the mock script is set up by the test script and how the script receives function calls from the STRIDE runtime.

			; Note: An alternative to the synchronization technique shown here is given in the article [[How to synchronize scripts]].

	=Notes on the Examples=		=Notes on the Examples=

2008-03-10T21:06:05Z

TestScript.pl

← Older revision		Revision as of 21:06, 10 March 2008
Line 126:		Line 126:
	do {		do {
	$main::ascript->Sleep(100);		$main::ascript->Sleep(100);
	} while (!$f->IsRegistered && time - $startTime < 2);		} while (!$f->IsRegistered && (time - $startTime) < 2);
	}		}

2008-03-07T17:02:46Z

@@ Line 1: / Line 1: @@
-==Perl==
+This note describes how to simulate (mock) a function using a script in Stride STUDIO. This technique is useful when a target-based function you are testing has a dependency on another function that has not been written yet, makes use of unavailable hardware resources, or can't be used for some other reason.
-===TestScript.pl===
+Example code is given in both Perl and JScript demonstrating how the mock script is set up by the test script and how the script receives function calls from the STRIDE runtime.
 <source lang="perl">
@@ Line 128: / Line 146: @@
 </source>
-===LeapYearMock.pl===
+==LeapYearMock.pl==
 <source lang="perl">
@@ Line 249: / Line 273: @@
 </source>
-==JScript==
+=JScript=
 <source lang="javascript">
@@ Line 374: / Line 404: @@
 </source>
-===LeapYearMock.js===
+==LeapYearMock.js==
 <source lang="javascript">
 // get the owner instance of the function

2008-03-06T22:31:32Z

2008-03-06T22:30:54Z