Test Units - Revision history

Ivailop: /* MyTest.c */

2014-08-01T22:59:46Z

MyTest.c

← Older revision		Revision as of 22:59, 1 August 2014
Line 196:		Line 196:
	self->ExpectPass = ExpectPass;		self->ExpectPass = ExpectPass;
	self->ExpectFail = ExpectFail;		self->ExpectFail = ExpectFail;
	~~self->ChangeMyName = ChangeMyName;~~
	~~self->ChangeMyDescription = ChangeMyDescription;~~
	}		}
	</source>		</source>

Ivailop: /* Simple Test Unit Examples */

2014-08-01T22:59:20Z

Simple Test Unit Examples

@@ Line 148: / Line 148: @@
      srNOTE_INFO("this test should fail");
      srEXPECT_GT(2 * 3, 7);
+   }
 };
@@ Line 179: / Line 167: @@
      void (*ExpectPass)(struct MyTest* self);
      void (*ExpectFail)(struct MyTest* self);
 } MyTest;
@@ Line 205: / Line 191: @@
      srNOTE_INFO("this test should fail");
      srEXPECT_GT(2 * 3, 7);
+}
 void MyTest_Init(MyTest* self)
@@ Line 233: / Line 207: @@
 void ExpectPass();
 void ExpectFail();
 #ifdef _SCL
@@ Line 256: / Line 228: @@
      srNOTE_INFO("this test should fail");
      srEXPECT_GT(2 * 3, 7);
+}
 </source>

Timd at 22:01, 5 June 2013

2013-06-05T22:01:02Z

← Older revision		Revision as of 22:01, 5 June 2013
Line 175:		Line 175:


	~~typdef~~ struct MyTest		typedef struct MyTest
	{		{
	void (ExpectPass)(struct MyTest self);		void (ExpectPass)(struct MyTest self);

Timd: /* Pass/Fail */

2012-02-08T22:59:16Z

Pass/Fail

← Older revision		Revision as of 22:59, 8 February 2012
Line 100:		Line 100:
	Typically, you will set Test Case attributes via STRIDE Macros that simplify the interaction with the Test Case, the most common of these are [[Test Code Macros]] - to set the Test Case status.		Typically, you will set Test Case attributes via STRIDE Macros that simplify the interaction with the Test Case, the most common of these are [[Test Code Macros]] - to set the Test Case status.

	====Pass/Fail====		====Specifying Pass/Fail====
	[[Indicating Pass/Fail in a Test Method]]		There are several ways to indicate pass/fail status in a test method. The most common is to use a Stride test macro, but other options are available. See [[Indicating Pass/Fail in a Test Method]] for more details.

	===Test Units===		===Test Units===

Timd: /* Test Methods */

2012-02-07T22:39:42Z

Test Methods

← Older revision		Revision as of 22:39, 7 February 2012
Line 99:		Line 99:

	Typically, you will set Test Case attributes via STRIDE Macros that simplify the interaction with the Test Case, the most common of these are [[Test Code Macros]] - to set the Test Case status.		Typically, you will set Test Case attributes via STRIDE Macros that simplify the interaction with the Test Case, the most common of these are [[Test Code Macros]] - to set the Test Case status.

			====Pass/Fail====
			[[Indicating Pass/Fail in a Test Method]]

	===Test Units===		===Test Units===

Ivailop: /* Running Target-Based Tests */

2011-09-12T19:47:35Z

Running Target-Based Tests

← Older revision		Revision as of 19:47, 12 September 2011
Line 285:		Line 285:

	== Running Target-Based Tests ==		== Running Target-Based Tests ==
	After configuring TCP/IP or ~~COM~~ port communication parameters, tests are controlled and run from a [[Running Test Units\|remote host computer]]. See [[Stride Runner]] for details.		After configuring TCP/IP or Serial port communication parameters, tests are controlled and run from a [[Running Test Units\|remote host computer]]. See [[Stride Runner]] for details.



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

Marku at 21:27, 27 June 2011

2011-06-27T21:27:25Z

← Older revision		Revision as of 21:27, 27 June 2011
Line 119:		Line 119:

	For more on the internal reporting model, [[Reporting Model\|see here]]		For more on the internal reporting model, [[Reporting Model\|see here]]

			== Parameterized Test Units ==
			You can pass parameters to Test Units using a command line option of the [[STRIDE_Runner \| Runner]]. This allows you to provide input to a test during runtime.

			For more on passing parameters to Test Units, [[Parameterized Test Units \| see here]]

	== Simple Test Unit Examples ==		== Simple Test Unit Examples ==
	Following are a few short examples. In each example, a single test unit with the name "MyTest" is identified to the [[s2scompile\|STRIDE compiler]] via a custom [[Test Unit Pragmas\|special test pragma]].		Following are a few short examples. In each example, a single test unit with the name "MyTest" is identified to the [[s2scompile\|STRIDE compiler]] via a custom [[Test Unit Pragmas\|special test pragma]].


	=== Test Unit as C++ Class ===		=== Test Unit as C++ Class ===
Line 283:		Line 287:
	After configuring TCP/IP or COM port communication parameters, tests are controlled and run from a [[Running Test Units\|remote host computer]]. See [[Stride Runner]] for details.		After configuring TCP/IP or COM port communication parameters, tests are controlled and run from a [[Running Test Units\|remote host computer]]. See [[Stride Runner]] for details.

	~~== Parameterized Test Units ==~~
	* [[Parameterized Test Units]]


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

Marku: /* Test Units */

2011-06-27T21:17:36Z

Test Units

← Older revision		Revision as of 21:17, 27 June 2011
Line 33:		Line 33:
	* Can be used with target code that is all C, all C++, or a mix		* Can be used with target code that is all C, all C++, or a mix
	* Test utility methods can be encapsulated as test class members or members of a parent class		* Test utility methods can be encapsulated as test class members or members of a parent class
	* Could be parametrized via constructor arguments		* Could be [[Parameterized_Test_Units \| parametrized]] via constructor arguments
	* Provides convenient syntax for augmenting report annotation (operator <tt><<</tt>)		* Provides convenient syntax for augmenting report annotation (operator <tt><<</tt>)
	\|		\|
Line 48:		Line 48:
	* Provides encapsulation of test methods		* Provides encapsulation of test methods
	* Provides encapsulation of state via member variables		* Provides encapsulation of state via member variables
	* Could be parametrized via init-function arguments		* Could be [[Parameterized_Test_Units \|parametrized]] via init-function arguments
	\|		\|
	* Requires initialization code for structure function pointer setup		* Requires initialization code for structure function pointer setup

Timd at 17:44, 27 June 2011

2011-06-27T17:44:13Z

← Older revision		Revision as of 17:44, 27 June 2011
Line 282:		Line 282:
	== Running Target-Based Tests ==		== Running Target-Based Tests ==
	After configuring TCP/IP or COM port communication parameters, tests are controlled and run from a [[Running Test Units\|remote host computer]]. See [[Stride Runner]] for details.		After configuring TCP/IP or COM port communication parameters, tests are controlled and run from a [[Running Test Units\|remote host computer]]. See [[Stride Runner]] for details.

			== Parameterized Test Units ==
			* [[Parameterized Test Units]]


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

Ivailop: /* Simple Test Unit Examples */

2011-06-15T03:52:16Z

Simple Test Unit Examples

← Older revision		Revision as of 03:52, 15 June 2011
Line 129:		Line 129:
	#include <srtest.h>		#include <srtest.h>

	class MyTest : public stride::srTest		class MyTest : public stride::srTest
	{		{
	public:		public:
	void ExpectPass()		void ExpectPass()
	{		{
	srNOTE_INFO("this test should pass");		srNOTE_INFO("this test should pass");
	srEXPECT_EQ(2 + 2, 4);		srEXPECT_EQ(2 + 2, 4);
	}		}
	void ExpectFail()		void ExpectFail()
	{		{
	srNOTE_INFO("this test should fail");		srNOTE_INFO("this test should fail");
	srEXPECT_GT(2 * 3, 7);		srEXPECT_GT(2 * 3, 7);
	}		}
	int ChangeMyName()		int ChangeMyName()
	{		{
	srNOTE_INFO("this test should have name = MyChangedName");		srNOTE_INFO("this test should have name = MyChangedName");
	testCase.SetName("MyChangedName");		testCase.SetName("MyChangedName");
	return 0;		return 0;
Line 150:		Line 150:
	int ChangeMyDescription()		int ChangeMyDescription()
	{		{
	srNOTE_INFO("this test should have a description set");		srNOTE_INFO("this test should have a description set");
	testCase.SetDescription("this is my new description");		testCase.SetDescription("this is my new description");
	return 0;		return 0;
	}		}
Line 168:		Line 168:


	typdef struct MyTest		typdef struct MyTest
	{		{
	void (ExpectPass)(struct MyTest self);		void (ExpectPass)(struct MyTest self);
	void (ExpectFail)(struct MyTest self);		void (ExpectFail)(struct MyTest self);
	int (ChangeMyName)(struct MyTest self);		int (ChangeMyName)(struct MyTest self);
	int (ChangeMyDescription)(struct MyTest self);		int (ChangeMyDescription)(struct MyTest self);
	} MyTest;		} MyTest;

	void MyTest_Init(MyTest* self);		void MyTest_Init(MyTest* self);

	#ifdef _SCL		#ifdef _SCL
Line 182:		Line 182:
	// Extra instrumentation code will be generated to call MyTest_Init() before		// Extra instrumentation code will be generated to call MyTest_Init() before
	// tests are run.		// tests are run.
	#pragma scl_test_cclass(MyTest, MyTest_Init)		#pragma scl_test_cclass(MyTest, MyTest_Init)
	#endif		#endif
	</source>		</source>
Line 192:		Line 192:
	{		{
	srNOTE_INFO("this test should pass");		srNOTE_INFO("this test should pass");
	srEXPECT_EQ(2 + 2, 4);		srEXPECT_EQ(2 + 2, 4);
	}		}
	static void ExpectFail(MyTest* self)		static void ExpectFail(MyTest* self)
	{		{
	srNOTE_INFO("this test should fail");		srNOTE_INFO("this test should fail");
	srEXPECT_GT(2 * 3, 7);		srEXPECT_GT(2 * 3, 7);
	}		}
	static int ChangeMyName(MyTest* self)		static int ChangeMyName(MyTest* self)
	{		{
	srNOTE_INFO("this test should have name = MyChangedName");		srNOTE_INFO("this test should have name = MyChangedName");
	srTestCaseSetName(srTEST_CASE_DEFAULT, "MyChangedName");		srTestCaseSetName(srTEST_CASE_DEFAULT, "MyChangedName");
	return 0;		return 0;
	}		}
	static int ChangeMyDescription(MyTest* self)		static int ChangeMyDescription(MyTest* self)
	{		{
	srNOTE_INFO("this test should have a description set");		srNOTE_INFO("this test should have a description set");
	srTestCaseSetDescription(srTEST_CASE_DEFAULT, "this is my new description");		srTestCaseSetDescription(srTEST_CASE_DEFAULT, "this is my new description");
	return 0;		return 0;
	}		}
	void MyTest_Init(MyTest* self)		void MyTest_Init(MyTest* self)
	{		{
	self->ExpectPass = ExpectPass;		self->ExpectPass = ExpectPass;
	self->ExpectFail = ExpectFail;		self->ExpectFail = ExpectFail;
	self->ChangeMyName = ChangeMyName;		self->ChangeMyName = ChangeMyName;
	self->ChangeMyDescription = ChangeMyDescription;		self->ChangeMyDescription = ChangeMyDescription;
	}		}
	</source>		</source>
Line 222:		Line 222:
	=== Test Unit as Group of Free Functions ===		=== Test Unit as Group of Free Functions ===
	====MyTest.h====		====MyTest.h====
	<source lang=c>		<source lang=c>
	#include <srtest.h>		#include <srtest.h>
	void ExpectPass();		void ExpectPass();
	void ExpectFail();		void ExpectFail();
	int ChangeMyName();		int ChangeMyName();
	int ChangeMyDescription();		int ChangeMyDescription();

Line 232:		Line 232:
	// this pragma identifies MyTest as a test unit to the STRIDE compiler, specifying		// this pragma identifies MyTest as a test unit to the STRIDE compiler, specifying
	// the four functions as members of the test unit		// the four functions as members of the test unit
	#pragma scl_test_flist("MyTest", ExpectPass, ExpectFail, ChangeMyName, ChangeMyDescription)		#pragma scl_test_flist("MyTest", ExpectPass, ExpectFail, ChangeMyName, ChangeMyDescription)
	#endif		#endif
	</source>		</source>

	====MyTest.c====		====MyTest.c====
	<source lang='c'>		<source lang='c'>
	#include "MyTest.h"		#include "MyTest.h"

	void ExpectPass()		void ExpectPass()
	{		{
	srNOTE_INFO("this test should pass");		srNOTE_INFO("this test should pass");
	srEXPECT_EQ(2 + 2, 4);		srEXPECT_EQ(2 + 2, 4);
	}		}
	void ExpectFail()		void ExpectFail()
	{		{
	srNOTE_INFO("this test should fail");		srNOTE_INFO("this test should fail");
	srEXPECT_GT(2 * 3, 7);		srEXPECT_GT(2 * 3, 7);
	}		}
	int ChangeMyName()		int ChangeMyName()
	{		{
	srNOTE_INFO("this test should have name = MyChangedName");		srNOTE_INFO("this test should have name = MyChangedName");
	srTestCaseSetName(srTEST_CASE_DEFAULT, "MyChangedName");		srTestCaseSetName(srTEST_CASE_DEFAULT, "MyChangedName");
	return 0;		return 0;
	}		}
	int ChangeMyDescription()		int ChangeMyDescription()
	{		{
	srNOTE_INFO("this test should have a description set");		srNOTE_INFO("this test should have a description set");
	srTestCaseSetDescription(srTEST_CASE_DEFAULT, "this is my new description");		srTestCaseSetDescription(srTEST_CASE_DEFAULT, "this is my new description");
	return 0;		return 0;
	}		}