Test Intro Cpp Sample - Revision history

Marku at 15:48, 27 May 2011

2011-05-27T15:48:55Z

← Older revision		Revision as of 15:48, 27 May 2011
Line 11:		Line 11:
	* [[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]]

	;Pass		;Pass
Line 80:		Line 81:
	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>-O</tt> option.)
	<pre>		<pre>
	--run "/{~~s2_testintro~~::Parameters(\" \", 1, 1)}"		--run "/{s2_testintrocpp::Parameters(\" \", 1, 1)}"
	--run "/{~~s2_testintro~~::Parameters(\"m\", 1, 0)}"		--run "/{s2_testintrocpp::Parameters(\"m\", 1, 0)}"
	--run "/{~~s2_testintro~~::Parameters(\"my \", 2, 1)}"		--run "/{s2_testintrocpp::Parameters(\"my \", 2, 1)}"
	--run "/{~~s2_testintro~~::Parameters(\"my string\", 9, 1)}"		--run "/{s2_testintrocpp::Parameters(\"my string\", 9, 1)}"
	</pre>		</pre>

Ivailop: /* TestPoints */

2010-06-09T22:15:18Z

TestPoints

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

			* [[Test_Point\|test points]]

	* event verification		* event verification

Ivailop: /* TestDoubles */

2010-06-09T22:12:38Z

TestDoubles

← Older revision		Revision as of 22:12, 9 June 2010
Line 25:		Line 25:
	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]

Marku: /* TestClass */

2010-06-02T23:11:41Z

TestClass

← Older revision		Revision as of 23:11, 2 June 2010
Line 10:		Line 10:
	* [[Scl test class\|test_class test units]]		* [[Scl test class\|test_class 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]]

	;Pass		;Pass

Ivailop: /* TestClass */

2010-02-13T01:27:17Z

TestClass

← Older revision		Revision as of 01:27, 13 February 2010
Line 18:		Line 18:
	: Calls a simple FUT (function under test) and uses srEXPECT macros to validate the return value. All assertions fail for this test case.		: Calls a simple FUT (function under test) 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 an <tt>~~srLOG~~</tt> 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 an <tt>srNOTE</tt> message, which can be seen in the test results report.

	Note that the test cases are executed in the order in which they appear in the C++ class.		Note that the test cases are executed in the order in which they appear in the C++ class.

Timd at 17:38, 30 September 2009

2009-09-30T17:38:37Z

← Older revision		Revision as of 17:38, 30 September 2009
Line 86:		Line 86:
	<references/>		<references/>

	[[Category:~~Sandbox & Training~~]]		[[Category:Samples]]

Timd at 17:36, 30 September 2009

2009-09-30T17:36:26Z

← Older revision		Revision as of 17:36, 30 September 2009
Line 85:		Line 85:
	== Notes ==		== Notes ==
	<references/>		<references/>

			[[Category:Sandbox & Training]]

Timd: /* Introduction */

2009-09-22T23:20:23Z

Introduction

← Older revision		Revision as of 23:20, 22 September 2009
Line 1:		Line 1:
	== Introduction ==		== Introduction ==
	These examples provide an overview of STRIDE features and techniques used in a C++ environment. (For an overview from a C perspective, please see [[Test Intro Sample]].)		These examples provide an overview of STRIDE features and techniques used in a C++ environment. (For an overview from a C perspective, please see [[Test Intro Sample]].)

			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.

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

Timd at 23:17, 22 September 2009

2009-09-22T23:17:54Z

@@ Line 1: / Line 1: @@
 == Introduction ==
 == Tests Description ==
 === TestClass ===
 === TestDoubles ===
 === TestPoints ===
 === Parameters ===

Timd: Created page with '== Introduction == == Tests Description == === TestClass === === TestDoubles === === TestPoints === === Parameters ==='

2009-09-22T22:07:59Z

Created page with '== Introduction == == Tests Description == === TestClass === === TestDoubles === === TestPoints === === Parameters ==='

New page

== Introduction ==

== Tests Description ==

=== TestClass ===

=== TestDoubles ===

=== TestPoints ===

=== Parameters ===