Function Capturing - Revision history

Timd at 20:07, 1 June 2010

2010-06-01T20:07:56Z

← Older revision		Revision as of 20:07, 1 June 2010
Line 22:		Line 22:

	== Remoting ==		== Remoting ==
	The simplest form of capturing (using [[scl_function]] with no additional arguments) would make a function exposed for external to the target use (remote calling). Such ~~exposer allows~~ number of uses, ~~as one of~~ them is [[Perl_Script_Snippets#Invoking_a_function_on_the_target\|fuxturing a test script]].		The simplest form of capturing (using [[scl_function]] with no additional arguments) would make a function exposed for external to the target use (remote calling). Such exposure provides a number of uses, among them is [[Perl_Script_Snippets#Invoking_a_function_on_the_target\|fuxturing a test script]].

	== Interception ==		== Interception ==

Ivailop: /* Remoting */

2010-05-12T05:23:15Z

Remoting

← Older revision		Revision as of 05:23, 12 May 2010
Line 22:		Line 22:

	== Remoting ==		== Remoting ==
	The simplest form of capturing (using [[scl_function]] with no additional arguments) would make a function exposed for external on the target use (remote calling). Such exposer allows number of uses, as one of them is [[Perl_Script_Snippets#Invoking_a_function_on_the_target\|fuxturing a test script]].		The simplest form of capturing (using [[scl_function]] with no additional arguments) would make a function exposed for external to the target use (remote calling). Such exposer allows number of uses, as one of them is [[Perl_Script_Snippets#Invoking_a_function_on_the_target\|fuxturing a test script]].

	== Interception ==		== Interception ==

Ivailop at 19:02, 15 March 2010

2010-03-15T19:02:50Z

← Older revision		Revision as of 19:02, 15 March 2010
Line 20:		Line 20:

	By simply passing the new header file to the [[Build Tools\|STRIDE Build Tools]] the captured function would become part of the [[Intercept Module]].		By simply passing the new header file to the [[Build Tools\|STRIDE Build Tools]] the captured function would become part of the [[Intercept Module]].

			== Remoting ==
			The simplest form of capturing (using [[scl_function]] with no additional arguments) would make a function exposed for external on the target use (remote calling). Such exposer allows number of uses, as one of them is [[Perl_Script_Snippets#Invoking_a_function_on_the_target\|fuxturing a test script]].

	== Interception ==		== Interception ==
	~~Once captured a~~ function could be intercepted ~~and~~ dynamically substituted to implement on-the-fly mocks, stubs, and doubles. The [[Using Test Doubles\|Test Double]] article provides more details on the topic.		A function could be captured for the purpose of interception. When intercepted it could be dynamically substituted to implement on-the-fly mocks, stubs, and doubles. The [[Using Test Doubles\|Test Double]] article provides more details on the topic.

	~~== Remoting ==~~

	[[Category: Source Instrumentation]]		[[Category: Source Instrumentation]]

Ivailop: /* Interception */

2010-03-15T18:49:23Z

Interception

← Older revision		Revision as of 18:49, 15 March 2010
Line 22:		Line 22:

	== Interception ==		== Interception ==
			Once captured a function could be intercepted and dynamically substituted to implement on-the-fly mocks, stubs, and doubles. The [[Using Test Doubles\|Test Double]] article provides more details on the topic.

	== Remoting ==		== Remoting ==

	[[Category: Source Instrumentation]]		[[Category: Source Instrumentation]]

Ivailop: /* Specification */

2010-03-15T18:38:38Z

Specification

← Older revision		Revision as of 18:38, 15 March 2010
Line 2:		Line 2:

	== Specification ==		== Specification ==
	By using the STRIDE special [[scl_function]] pragma any global function could be captured. For example to capture ~~the following function~~:		By using the STRIDE special [[scl_function]] pragma any global function could be captured. For example to capture:
	<source lang="c">		<source lang="c">
	/* foo.h */		/* foo.h */
Line 19:		Line 19:
	</source>		</source>

	~~Once captured it could be instrumented by~~ simply passing the new header file to the [[Build Tools\|STRIDE Build Tools]].		By simply passing the new header file to the [[Build Tools\|STRIDE Build Tools]] the captured function would become part of the [[Intercept Module]].


	== Interception ==		== Interception ==

Ivailop: /* Specification */

2010-03-13T01:34:20Z

Specification

← Older revision		Revision as of 01:34, 13 March 2010
Line 19:		Line 19:
	</source>		</source>

	Once captured it could be instrumented by simply passing the new header file to the [[STRIDE Build Tools]].		Once captured it could be instrumented by simply passing the new header file to the [[Build Tools\|STRIDE Build Tools]].


			== Interception ==

			== Remoting ==

	[[Category: Source Instrumentation]]		[[Category: Source Instrumentation]]

Ivailop: Created page with 'For a user function to be exposed to the STRIDE Test System it needs to be captured. Once made available it could be remoted or doubled. == Specification == By using the STRIDE …'

2010-03-13T01:31:00Z

Created page with 'For a user function to be exposed to the STRIDE Test System it needs to be captured. Once made available it could be remoted or doubled. == Specification == By using the STRIDE …'

New page

For a user function to be exposed to the STRIDE Test System it needs to be captured. Once made available it could be remoted or doubled.

== Specification ==
By using the STRIDE special [[scl_function]] pragma any global function could be captured. For example to capture the following function:
<source lang="c">
/* foo.h */
int foo(void);
</source>

create a new header file and add the following pragma statement:

<source lang="c">
/* foo_SCL.h */
#include "foo.h"

#ifdef _SCL
#pragma scl_function(foo)
#endif
</source>

Once captured it could be instrumented by simply passing the new header file to the [[STRIDE Build Tools]].

[[Category: Source Instrumentation]]