Test Unit Pragmas - Revision history

Marku: /* Fixturing Pragmas */

2011-06-10T23:00:24Z

Fixturing Pragmas

← Older revision		Revision as of 23:00, 10 June 2011
Line 17:		Line 17:

	=== Fixturing Pragmas ===		=== Fixturing Pragmas ===
	These pragmas specify optional [~~http:~~/~~/en.wikipedia.org/wiki/Test_fixture~~ test fixturing] functions/methods that are called immediately before and after each test method in the specified STRIDE [[Test Units\|Test Unit]].		These pragmas specify optional [[Test_Fixturing_in_C/C%2B%2B \| test fixturing]] functions/methods that are called immediately before and after each test method in the specified STRIDE [[Test Units\|Test Unit]].

	; [[scl_test_setup]]		; [[scl_test_setup]]

Ivailop: /* Test Double Pragma */

2010-11-05T15:40:21Z

Test Double Pragma

← Older revision		Revision as of 15:40, 5 November 2010
Line 24:		Line 24:
	: Used to specify a function or method as a teardown fixture for a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM code]] to be generated that will call the fixture immediately after the execution of each test within the specified test unit.		: Used to specify a function or method as a teardown fixture for a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM code]] to be generated that will call the fixture immediately after the execution of each test within the specified test unit.

	=== ~~Test Double~~ Pragma ===		=== Function Pragma ===
	Any function that is to be [[~~Using Test Doubles~~\|~~doubled~~]] requires explicit declaration to the [[S2scompile\|STRIDE Compiler]].		Any function that is to be [[Function_Capturing#Remoting \| remoted]] or [[Function_Capturing#Interception \| intercepted]] requires explicit declaration to the [[S2scompile\|STRIDE Compiler]].

	; [[scl_function]]		; [[scl_function]]
	: Used to specify a function for instrumentation to the [[S2scompile\|STRIDE Compiler]]~~. When used with optional arguments, the generated~~ [[Intercept Module\|IM code]] ~~will include~~ call interception~~, thus enabling run-time [[Using Test Doubles\|doubling]]~~.		: Used to specify a function for instrumentation. Based on the setup the [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM code]] to be generated for either external exposure or call interception.

	<hr/>		<hr/>
	'''Notes'''		'''Notes'''

Marku: /* Test Double Pragma */

2010-05-28T17:30:20Z

Test Double Pragma

← Older revision		Revision as of 17:30, 28 May 2010
Line 35:		Line 35:
	[[Category:Test Units]]		[[Category:Test Units]]
	[[Category:SCL]]		[[Category:SCL]]
	~~[[Category:Testing]]~~

Timd: Text replace - 'Category:For Developers...' to 'Category:Testing'

2009-09-30T17:12:56Z

Text replace - 'Category:For Developers...' to 'Category:Testing'

← Older revision		Revision as of 17:12, 30 September 2009
Line 35:		Line 35:
	[[Category:Test Units]]		[[Category:Test Units]]
	[[Category:SCL]]		[[Category:SCL]]
	[[Category:~~For Developers...~~]]		[[Category:Testing]]

Timd: Added tag: 'For Developers...'

2009-08-20T22:13:17Z

Added tag: 'For Developers...'

← Older revision		Revision as of 22:13, 20 August 2009
Line 35:		Line 35:
	[[Category:Test Units]]		[[Category:Test Units]]
	[[Category:SCL]]		[[Category:SCL]]
			[[Category:For Developers...]]

Timd at 18:58, 8 April 2009

2009-04-08T18:58:04Z

← Older revision		Revision as of 18:58, 8 April 2009
Line 4:		Line 4:
	[[SCL Pragmas]] have wide application in remoting of interfaces within the STRIDE runtime environment; the pragmas that are relevant to [[Test Units\|Test Unit]] testing are highlighted here.		[[SCL Pragmas]] have wide application in remoting of interfaces within the STRIDE runtime environment; the pragmas that are relevant to [[Test Units\|Test Unit]] testing are highlighted here.

	== Test Unit Pragmas ==		=== Test Unit Pragmas ===
	These pragmas specify [[Test Units]] to the [[S2scompile\|STRIDE Compiler]] and--by extension--to the subsequent [[Build Tools]], thus generating [[Intercept Module\|IM source code]] that provides [http://en.wikipedia.org/wiki/Test_harness harnessing] for the tests.		These pragmas specify [[Test Units]] to the [[S2scompile\|STRIDE Compiler]] and--by extension--to the subsequent [[Build Tools]], thus generating [[Intercept Module\|IM source code]] that provides [http://en.wikipedia.org/wiki/Test_harness harnessing] for the tests.

Line 24:		Line 24:
	: Used to specify a function or method as a teardown fixture for a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM code]] to be generated that will call the fixture immediately after the execution of each test within the specified test unit.		: Used to specify a function or method as a teardown fixture for a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM code]] to be generated that will call the fixture immediately after the execution of each test within the specified test unit.

			=== Test Double Pragma ===
			Any function that is to be [[Using Test Doubles\|doubled]] requires explicit declaration to the [[S2scompile\|STRIDE Compiler]].

			; [[scl_function]]
			: Used to specify a function for instrumentation to the [[S2scompile\|STRIDE Compiler]]. When used with optional arguments, the generated [[Intercept Module\|IM code]] will include call interception, thus enabling run-time [[Using Test Doubles\|doubling]].
	<hr/>		<hr/>
	~~===~~Notes~~===~~		'''Notes'''
	<references/>		<references/>

			[[Category:Test Units]]
			[[Category:SCL]]

Timd: /* SCL Pragmas */

2009-04-08T18:45:58Z

SCL Pragmas

← Older revision		Revision as of 18:45, 8 April 2009
Line 2:		Line 2:
	[[SCL Pragmas]] <ref>SCL is an acronym for STRIDE Communication Language</ref> comprise a set of compiler directives that allow annotations within C and C++ source files that are meaningful to the [[S2scompile\|STRIDE Compiler]] but ignored by standard language compilers.		[[SCL Pragmas]] <ref>SCL is an acronym for STRIDE Communication Language</ref> comprise a set of compiler directives that allow annotations within C and C++ source files that are meaningful to the [[S2scompile\|STRIDE Compiler]] but ignored by standard language compilers.

	[[SCL Pragmas]] have wide application in remoting of interfaces within the STRIDE runtime environment; the ~~five~~ pragmas that are relevant to [[Test Units\|Test Unit]] testing are highlighted here.		[[SCL Pragmas]] have wide application in remoting of interfaces within the STRIDE runtime environment; the pragmas that are relevant to [[Test Units\|Test Unit]] testing are highlighted here.

	== Test Unit Pragmas ==		== Test Unit Pragmas ==

Timd: /* Notes */

2009-04-07T17:55:32Z

Notes

← Older revision		Revision as of 17:55, 7 April 2009
Line 24:		Line 24:
	: Used to specify a function or method as a teardown fixture for a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM code]] to be generated that will call the fixture immediately after the execution of each test within the specified test unit.		: Used to specify a function or method as a teardown fixture for a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM code]] to be generated that will call the fixture immediately after the execution of each test within the specified test unit.

			<hr/>
	===Notes===		===Notes===
	<references/>		<references/>

Timd at 17:53, 7 April 2009

2009-04-07T17:53:07Z

← Older revision		Revision as of 17:53, 7 April 2009
Line 1:		Line 1:
	==SCL Pragmas==		==SCL Pragmas==
	[[SCL Pragmas]] <ref>SCL ~~stands~~ for STRIDE Communication Language</ref> comprise a set of compiler directives that allow annotations within C and C++ source files that are meaningful to the [[STRIDE Compiler]] but ignored by standard language compilers.		[[SCL Pragmas]] <ref>SCL is an acronym for STRIDE Communication Language</ref> comprise a set of compiler directives that allow annotations within C and C++ source files that are meaningful to the [[S2scompile\|STRIDE Compiler]] but ignored by standard language compilers.

	[[SCL Pragmas]] have wide application in remoting of interfaces within the STRIDE environment; the five pragmas that are relevant to [[Test Units\|Test Unit]] testing are highlighted here.		[[SCL Pragmas]] have wide application in remoting of interfaces within the STRIDE runtime environment; the five pragmas that are relevant to [[Test Units\|Test Unit]] testing are highlighted here.

	== Test Unit Pragmas ==		== Test Unit Pragmas ==
			These pragmas specify [[Test Units]] to the [[S2scompile\|STRIDE Compiler]] and--by extension--to the subsequent [[Build Tools]], thus generating [[Intercept Module\|IM source code]] that provides [http://en.wikipedia.org/wiki/Test_harness harnessing] for the tests.

	* [[scl_test_class]]		For additional information and examples, see the linked articles.
	* [[scl_test_cclass]]
	* [[scl_test_flist]]		;[[scl_test_class]]
	* [[scl_test_setup]]		: Used to specify a C++ class as a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM]] code to be generated that can instantiate an instance of this class and execute its test methods.
	* [[scl_test_teardown]]		; [[scl_test_cclass]]
			: Used to specify a C class (structure containing member pointers to test methods) as a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM code]] to be generated that can instantiate an instance of this class and execute its test methods.
			; [[scl_test_flist]]
			: Used to specify a list of free functions as a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM]] code to be generated that can execute each test function.

			=== Fixturing Pragmas ===
			These pragmas specify optional [http://en.wikipedia.org/wiki/Test_fixture test fixturing] functions/methods that are called immediately before and after each test method in the specified STRIDE [[Test Units\|Test Unit]].

			; [[scl_test_setup]]
			: Used to specify a function or method as a setup fixture for a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM code]] to be generated that will call the fixture immediately before the execution of each test within the specified test unit.
			; [[scl_test_teardown]]
			: Used to specify a function or method as a teardown fixture for a STRIDE [[Test Units\|Test Unit]]. The [[S2scompile\|STRIDE Compiler]] will cause [[Intercept Module\|IM code]] to be generated that will call the fixture immediately after the execution of each test within the specified test unit.

	===Notes===		===Notes===
	<references/>		<references/>

Timd: New page: ==SCL Pragmas== SCL Pragmas SCL stands for STRIDE Communication Language comprise a set of compiler directives that allow annotations within C and C++ source files that are ...

2009-04-07T00:17:03Z

New page: ==SCL Pragmas== SCL Pragmas <ref>SCL stands for STRIDE Communication Language</ref> comprise a set of compiler directives that allow annotations within C and C++ source files that are ...

New page

==SCL Pragmas==
[[SCL Pragmas]] <ref>SCL stands for STRIDE Communication Language</ref> comprise a set of compiler directives that allow annotations within C and C++ source files that are meaningful to the [[STRIDE Compiler]] but ignored by standard language compilers.

[[SCL Pragmas]] have wide application in remoting of interfaces within the STRIDE environment; the five pragmas that are relevant to [[Test Units|Test Unit]] testing are highlighted here.

== Test Unit Pragmas ==

* [[scl_test_class]]
* [[scl_test_cclass]]
* [[scl_test_flist]]
* [[scl_test_setup]]
* [[scl_test_teardown]]

===Notes===
<references/>