Test Intro Sample - Revision history

Ivailop: /* s2_testintro_parameters */

2012-02-10T00:51:46Z

s2_testintro_parameters

← Older revision		Revision as of 00:51, 10 February 2012
Line 96:		Line 96:
	: Verifies that the calculated number of spaces in a string matches the expected value		: Verifies that the calculated number of spaces in a string matches the expected value

	A common use of this type of test is to call it repeatedly with different values in order to provide coverage or to exercise boundary conditions of the function(s) under test. For example, the following might submitted as <tt>--run</tt> arguments to [[STRIDE Runner\|stride]]. (These would typically be put into an options file and submitted to the stride command line using the <tt>-O</tt> option.)		A common use of this type of test is to call it repeatedly with different values in order to provide coverage or to exercise boundary conditions of the function(s) under test. For example, the following might submitted as <tt>--run</tt> arguments to [[STRIDE Runner\|stride]]. (These would typically be put into an options file and submitted to the stride command line using the <tt>--options_file</tt> option.)
	<pre>		<pre>
	--run "/{s2_testintro_parameters(\" \", 1, 1)}"		--run "/{s2_testintro_parameters(\" \", 1, 1)}"

Marku: /* Introduction */

2011-06-07T17:37:02Z

Introduction

← Older revision		Revision as of 17:37, 7 June 2011
Line 4:		Line 4:

	Furthermore, since this example has no external dependencies, it is a viable candidate for use as an initial set of tests integrated with your target device. In this capacity, this sample can be used to quickly get a feel for the end-to-end integration and execution of STRIDE Test Units on your device.		Furthermore, since this example has no external dependencies, it is a viable candidate for use as an initial set of tests integrated with your target device. In this capacity, this sample can be used to quickly get a feel for the end-to-end integration and execution of STRIDE Test Units on your device.

	~~For instructions on adding this sample, see [[Running and Publishing the TestIntro Sample]].~~

	== Tests Description ==		== Tests Description ==

Marku: /* s2_testintro_cclass */

2011-05-27T15:31:37Z

s2_testintro_cclass

← Older revision		Revision as of 15:31, 27 May 2011
Line 16:		Line 16:
	* [[Test_Unit_Pragmas#Fixturing_Pragmas\|fixturing]]		* [[Test_Unit_Pragmas#Fixturing_Pragmas\|fixturing]]
	* [[Test Macros\|pass/fail macros]]		* [[Test Macros\|pass/fail macros]]
			* [[Test_Macros#Note_Macros \| Note Macros]]

	This demonstrates the declaration and use of a C-class test unit -- a structure with function pointer members and optional member data. The test unit contains the following test cases:		This demonstrates the declaration and use of a C-class test unit -- a structure with function pointer members and optional member data. The test unit contains the following test cases:

Ivailop: /* s2_testintro_testpoints */

2010-06-09T22:15:37Z

s2_testintro_testpoints

← Older revision		Revision as of 22:15, 9 June 2010
Line 64:		Line 64:
	This example covers the following topics:		This example covers the following topics:

			* [[Test_Point\|test points]]
	* event verification		* event verification
	* state verification		* state verification

Ivailop: /* s2_testintro_testdoubles */

2010-06-09T21:33:56Z

s2_testintro_testdoubles

← Older revision		Revision as of 21:33, 9 June 2010
Line 44:		Line 44:
	This example covers the following topics:		This example covers the following topics:

			* [[Using Test Doubles \| test double]]
	* [http://xunitpatterns.com/Mock%20Object.html mock functions]<ref>[http://xunitpatterns.com/Mocks,%20Fakes,%20Stubs%20and%20Dummies.html mocks, fakes, and stubs]</ref>		* [http://xunitpatterns.com/Mock%20Object.html mock functions]<ref>[http://xunitpatterns.com/Mocks,%20Fakes,%20Stubs%20and%20Dummies.html mocks, fakes, and stubs]</ref>
	* [http://xunitpatterns.com/Fake%20Object.html fake functions]		* [http://xunitpatterns.com/Fake%20Object.html fake functions]
	* [[Test Macros \|pass/fail macros]]		* [[Test Macros \|pass/fail macros]]

	This example demonstrates the use of STRIDE's ~~[[Using Test Doubles \|~~ test double]] technique to implement mocks and fakes. The function being tested for these examples is ''s2CopyString'' (in s2_testintro_source.c) and depends on ''s2MoveString'' - the target of our doubling. The example includes the following test cases:		This example demonstrates the use of STRIDE's test double technique to implement mocks and fakes. The function being tested for these examples is ''s2CopyString'' (in s2_testintro_source.c) and depends on ''s2MoveString'' - the target of our doubling. The example includes the following test cases:

	;testDoubles_Normal		;testDoubles_Normal

Ivailop: /* s2_testintro_testdoubles */

2010-06-09T21:04:40Z

s2_testintro_testdoubles

← Older revision		Revision as of 21:04, 9 June 2010
Line 48:		Line 48:
	* [[Test Macros \|pass/fail macros]]		* [[Test Macros \|pass/fail macros]]

	This example demonstrates the use of STRIDE's test double technique to implement mocks and fakes. The function being ~~doubled~~ for these examples is ''s2CopyString'' (in s2_testintro_source.c). The example includes the following test cases:		This example demonstrates the use of STRIDE's [[Using Test Doubles \| test double]] technique to implement mocks and fakes. The function being tested for these examples is ''s2CopyString'' (in s2_testintro_source.c) and depends on ''s2MoveString'' - the target of our doubling. The example includes the following test cases:

	;testDoubles_Normal		;testDoubles_Normal
	: calls s2CopyString function as part of its testing. s2CopyString, as part of its implementation, calls s2MoveString. ~~s2MoveString will be the target of our~~ doubling~~; we will be able to test the behavior of s2CopyString while dynamically substituting different implementations of s2MoveString~~.		: calls s2CopyString function as part of its testing. s2CopyString, as part of its implementation, calls s2MoveString. This test case does not do anything special - there is no doubling.

	;testDoubles_Mock		;testDoubles_Mock

Marku at 23:07, 2 June 2010

2010-06-02T23:07:04Z

← Older revision		Revision as of 23:07, 2 June 2010
Line 15:		Line 15:
	* [[scl_test_cclass\|test_cclass test units]]		* [[scl_test_cclass\|test_cclass test units]]
	* [[Test_Unit_Pragmas#Fixturing_Pragmas\|fixturing]]		* [[Test_Unit_Pragmas#Fixturing_Pragmas\|fixturing]]
	* [[~~Pass/Fail~~ Macros\|pass/fail macros]]		* [[Test Macros\|pass/fail macros]]

	This demonstrates the declaration and use of a C-class test unit -- a structure with function pointer members and optional member data. The test unit contains the following test cases:		This demonstrates the declaration and use of a C-class test unit -- a structure with function pointer members and optional member data. The test unit contains the following test cases:

	; testBasics_PASS		; testBasics_PASS
	: calls a simple FUT (function under test) and uses [[~~Pass/Fail~~ Macros\|srEXPECT]] macros to validate the return value. All assertions pass for this test case.		: calls a simple FUT (function under test) and uses [[Test Macros \|srEXPECT]] macros to validate the return value. All assertions pass for this test case.
	; testBasics_FAIL		; testBasics_FAIL
	: calls the same FUT and uses srEXPECT macros to validate the return value. All assertions fail for this test case.		: calls the same FUT and uses srEXPECT macros to validate the return value. All assertions fail for this test case.
Line 33:		Line 33:

	* [[scl_test_flist\|test_flist test units]]		* [[scl_test_flist\|test_flist test units]]
	* [[~~Pass/Fail~~ Macros\|pass/fail macros]]		* [[Test Macros \|pass/fail macros]]
	* asynchronous code validation		* asynchronous code validation

Line 46:		Line 46:
	* [http://xunitpatterns.com/Mock%20Object.html mock functions]<ref>[http://xunitpatterns.com/Mocks,%20Fakes,%20Stubs%20and%20Dummies.html mocks, fakes, and stubs]</ref>		* [http://xunitpatterns.com/Mock%20Object.html mock functions]<ref>[http://xunitpatterns.com/Mocks,%20Fakes,%20Stubs%20and%20Dummies.html mocks, fakes, and stubs]</ref>
	* [http://xunitpatterns.com/Fake%20Object.html fake functions]		* [http://xunitpatterns.com/Fake%20Object.html fake functions]
	* [[~~Pass/Fail~~ Macros\|pass/fail macros]]		* [[Test Macros \|pass/fail macros]]

	This example demonstrates the use of STRIDE's test double technique to implement mocks and fakes. The function being doubled for these examples is ''s2CopyString'' (in s2_testintro_source.c). The example includes the following test cases:		This example demonstrates the use of STRIDE's test double technique to implement mocks and fakes. The function being doubled for these examples is ''s2CopyString'' (in s2_testintro_source.c). The example includes the following test cases:

Ivailop: /* References */

2010-05-17T22:07:28Z

References

← Older revision		Revision as of 22:07, 17 May 2010
Line 106:		Line 106:
	<references/>		<references/>

	~~[[Category:The Sandbox]]~~
	[[Category:Samples]]		[[Category:Samples]]

Ivailop: /* Introduction */

2010-04-19T23:20:11Z

Introduction

← Older revision		Revision as of 23:20, 19 April 2010
Line 5:		Line 5:
	Furthermore, since this example has no external dependencies, it is a viable candidate for use as an initial set of tests integrated with your target device. In this capacity, this sample can be used to quickly get a feel for the end-to-end integration and execution of STRIDE Test Units on your device.		Furthermore, since this example has no external dependencies, it is a viable candidate for use as an initial set of tests integrated with your target device. In this capacity, this sample can be used to quickly get a feel for the end-to-end integration and execution of STRIDE Test Units on your device.

	For instructions on adding this sample, see [[Running and Publishing the TestIntro Sample~~]] and [[Test_Execution#Adding_the_TestIntro_Tests_to_the_Target_Build\|Test Execution~~]].		For instructions on adding this sample, see [[Running and Publishing the TestIntro Sample]].

	== Tests Description ==		== Tests Description ==

Ivailop: /* s2_testintro_cclass */

2010-02-13T01:18:58Z

s2_testintro_cclass

← Older revision		Revision as of 01:18, 13 February 2010
Line 24:		Line 24:
	: calls the same FUT and uses srEXPECT macros to validate the return value. All assertions fail for this test case.		: calls the same FUT and uses srEXPECT macros to validate the return value. All assertions fail for this test case.

	This example also demonstrates the use of fixturing functions that are automatically called by the STRIDE framework to surround each test case call with setup/teardown functionality. Here, the fixturing simply writes a ~~srLOG~~ message, which can be seen in the test results report.		This example also demonstrates the use of fixturing functions that are automatically called by the STRIDE framework to surround each test case call with setup/teardown functionality. Here, the fixturing simply writes a srNOTE message, which can be seen in the test results report.

	As with all STRIDE test units, the test cases are executed in the order that they appear in the "C Class".		As with all STRIDE test units, the test cases are executed in the order that they appear in the "C Class".