Training Test Macros - Revision history

Marku: Marku moved page Training Basics to Training Test Macros

2014-11-22T14:50:31Z

Marku moved page Training Basics to Training Test Macros

← Older revision	Revision as of 14:50, 22 November 2014
(No difference)

Jeffs: /* Run and Publish Results */

2013-02-01T19:04:48Z

Run and Publish Results

← Older revision		Revision as of 19:04, 1 February 2013
Line 73:		Line 73:
	=== Run and Publish Results ===		=== Run and Publish Results ===

	When you have completed the Exercise(s) publish your results to Test Space(--space TestBasic). If you have not added test space options to your options file (<tt>myoptions.txt</tt>) please see [[Training_Getting_Started#Test_Space_Access\| testspace access]]		When you have completed the Exercise(s) publish your results to Test Space(--space TestBasic). If you have not added test space options to your options file (<tt>myoptions.txt</tt>) please see [[Training_Getting_Started#Test_Space_Access\| testspace access]].

	> stride --options_file myoptions.txt --run TestBasic --space TestBasic --upload		> stride --options_file myoptions.txt --run TestBasic --space TestBasic --upload

Jeffs at 21:19, 31 January 2013

2013-01-31T21:19:56Z

← Older revision		Revision as of 21:19, 31 January 2013
Line 73:		Line 73:
	=== Run and Publish Results ===		=== Run and Publish Results ===

	When you have completed the Exercise(s) publish your results to Test Space. ~~To make it easier for now we recommend that~~ you ~~update~~ your ~~existing option~~ file (<tt>myoptions.txt</tt>) ~~with the following:~~		When you have completed the Exercise(s) publish your results to Test Space(--space TestBasic). If you have not added test space options to your options file (<tt>myoptions.txt</tt>) please see [[Training_Getting_Started#Test_Space_Access\| testspace access]]

	~~#### Test Space options (partial) #####~~
	~~#### Note - make sure to change username, etc.~~ #~~###~~
	--testspace ~~<nowiki>https://username:password@yourcompany.stridetestspace.com</nowiki>~~
	~~--project Training~~
	~~--name YOURNAME~~

	> stride --options_file myoptions.txt --run TestBasic --space TestBasic --upload		> stride --options_file myoptions.txt --run TestBasic --space TestBasic --upload

Jeffs: /* Implement Exercises */

2013-01-31T21:04:56Z

Implement Exercises

← Older revision		Revision as of 21:04, 31 January 2013
Line 44:		Line 44:
	* '''Assignment 1:''' Add an ''srNOTE'' to <tt>Exercise()</tt> that will add a simple message to the test report (e.g. "Exercise ...")		* '''Assignment 1:''' Add an ''srNOTE'' to <tt>Exercise()</tt> that will add a simple message to the test report (e.g. "Exercise ...")
	** ''Hint:'' You will probably want to read about [[Test Macros]]		** ''Hint:'' You will probably want to read about [[Test Macros]]
			** ''Hint:'' srTestCaseSetStatus(srTEST_CASE_DEFAULT, srTEST_NOTINUSE, 0) is a placeholder to be removed when you add your test code.
	* '''Assignment 2:''' Within <tt>Exercise()</tt> validate that <tt>sut_mult(1,1)</tt> does NOT equal <tt>sut_add(1,1)</tt>		* '''Assignment 2:''' Within <tt>Exercise()</tt> validate that <tt>sut_mult(1,1)</tt> does NOT equal <tt>sut_add(1,1)</tt>
	** ''Hint:'' You will use a [[Test Macros \| Test Macro]].		** ''Hint:'' You will use a [[Test Macros \| Test Macro]].

Jeffs: /* Build and Run TestApp */

2013-01-28T18:47:47Z

Build and Run TestApp

@@ Line 19: / Line 19: @@
 * [[Building_an_Off-Target_Test_App#Build_Steps | Build TestApp]] using the SDK makefile
 * Invoke TestApp found in the ''/out/bin'' directory
-* Create an [[Stride_Runner#Options | option file]] (<tt>myoptions.txt</tt>) that includes the following content in either (SDK\Windows or SDK/Posix).
+* If you have not created an option file, please refer to [[Training_Getting_Started#Run_Training_Tests| setup]]
 * Execute the ''Test Basic'' Test Units

Marku: /* Samples */

2013-01-25T00:37:25Z

Samples

← Older revision		Revision as of 00:37, 25 January 2013
Line 131:		Line 131:
	=== Samples ===		=== Samples ===

	* [[~~Test_Function_List_Sample~~\|Test ~~Function List~~ Sample]] - Specifically the [[~~Test_Function_List_Sample~~#~~basic_simple~~\|Basic Simple]] Test Unit		* [[Test_Class_Sample\|Test Class Sample]] - Specifically the [[Test_Class_Sample#Basic\|Basic Simple]] Test Unit
	* [[Test_Macros_Sample\|Test Macro Sample]] - This sample covers simple uses of each of the Test Macros.		* [[Test_Macros_Sample\|Test Macro Sample]] - This sample covers simple uses of each of the Test Macros.

	Note - Other Test Unit Samples related to packaging that are useful are the following:		Note - Other Test Unit Samples related to packaging that are useful are the following:
	* [[Test_Class_Sample\|Test Class Sample]]
	* [[Test_CClass_Sample\|Test C Class Sample]]		* [[Test_CClass_Sample\|Test C Class Sample]]
			* [[Test_Function_List_Sample\|Test Function List Sample]]

	[[Category: Training]]		[[Category: Training]]

Jeffs: /* Implement Exercises */

2013-01-24T23:25:44Z

Implement Exercises

← Older revision		Revision as of 23:25, 24 January 2013
Line 55:		Line 55:
	Now edit the training source code to complete the following exercises:		Now edit the training source code to complete the following exercises:

	;~~TestExercise~~()		;Exercise()
	* '''Assignment 1:''' Add an ''srNOTE'' to <tt>~~TestExercise~~()</tt> that will add a simple message to the test report (e.g. "~~Test~~ Exercise ...")		* '''Assignment 1:''' Add an ''srNOTE'' to <tt>Exercise()</tt> that will add a simple message to the test report (e.g. "Exercise ...")
	** ''Hint:'' You will probably want to read about [[Test Macros]]		** ''Hint:'' You will probably want to read about [[Test Macros]]

	* '''Assignment 2:''' Within <tt>~~TestExercise~~()</tt> validate that <tt>sut_mult(1,1)</tt> does NOT equal <tt>sut_add(1,1)</tt>		* '''Assignment 2:''' Within <tt>Exercise()</tt> validate that <tt>sut_mult(1,1)</tt> does NOT equal <tt>sut_add(1,1)</tt>
	** ''Hint:'' You will use a [[Test Macros \| Test Macro]].		** ''Hint:'' You will use a [[Test Macros \| Test Macro]].

Jeffs at 23:23, 24 January 2013

2013-01-24T23:23:19Z

← Older revision		Revision as of 23:23, 24 January 2013
Line 2:		Line 2:

	This Training Module focuses on the basics of writing and executing tests. It covers the following topics:		This Training Module focuses on the basics of writing and executing tests. It covers the following topics:
	* The ~~different~~ [[Test_Units \| Test Unit packaging]] ~~options~~		* The C++ class [[Test_Units \| Test Unit packaging]] option
	* How to leverage [[Test_Macros \| Test Macros]]		* How to leverage [[Test_Macros \| Test Macros]]
	* Using [[Test_Macros#Notes \| Notes]] and [[Test_Log \| Test Logs]], what is the difference?		* Using [[Test_Macros#Notes \| Notes]] and [[Test_Log \| Test Logs]], what is the difference?
Line 9:		Line 9:


	~~This training module comprises three separate Test Units, each of which demonstrates an available packaging option~~:		The test unit is implemented in two source files: '''TestBasic.cpp''' and '''TestBasic.h'''. The comments and descriptions are contained in '''TestBasic.h'''.
	~~;TestBasic_FList~~
	~~: Packages a group of free functions into a Test Unit~~
	~~;TestBasic_CClass~~
	~~: Uses a C structure as a Test Unit container~~
	~~;TestBasic_Class~~
	~~: Uses a C++ class as a Test Unit container~~

	~~These test units are implemented in two source files: '''TestBasic.cpp''' and '''TestBasic.h'''. The comments and descriptions are contained in '''TestBasic.h'''.~~		The Test Unit has test cases already implemented (used for reference) and has a test method that you are required to implement (called '''Exercise'''). Currently this method is empty and returns a ''NOT IN USE'' status.

	The Test Unit has test cases already implemented (used for reference) and has a test method that you are required to implement (called '''~~TestExercise~~'''). Currently this method is empty and returns a ''NOT IN USE'' status.

	'''IMPORTANT NOTE''' - As you look at this module's source code, you will note that the test methods (cases) within each Test Unit are '''exactly''' the same, regardless of packaging. (In fact the ''CClass'' and ''Class'' Test Units just call the ''C-based'' test functions used by the ''FList'' Test Unit.) The only difference is in the packaging of the test methods into each Test Unit.

	== Instructions ==		== Instructions ==
Line 47:		Line 37:
	* Execute the ''Test Basic'' Test Units		* Execute the ''Test Basic'' Test Units

	> stride --options_file myoptions.txt --run ~~TestBasic_FList --run TestBasic_CClass --run TestBasic_Class~~		> stride --options_file myoptions.txt --run TestBasic

	Loading database...		Loading database...
	Connecting to device...		Connecting to device...
	Executing...		Executing...
	test unit "~~TestBasic_FList~~"		test unit "TestBasic"
	> 3 passed~~, 2 failed, 0 in progress~~, 1 ~~not in use.~~		> 3 passed, 1 failed, 0 in progress, 1 not in use.
	~~test unit "TestBasic_CClass"~~
	~~> 3 passed, 2 failed, 0 in progress, 1 not in use.~~
	~~test unit "TestBasic_Class"~~
	~~> 3 passed, 2~~ failed, 0 in progress, 1 not in use.
	--------------------------------------------------------------		--------------------------------------------------------------
	Summary: 9 passed, 6 failed, 0 in progress, 3 not in use.		Summary: 3 passed, 1 failed, 0 in progress, 1 not in use.

	Disconnecting from device...		Disconnecting from device...
Line 69:		Line 54:

	Now edit the training source code to complete the following exercises:		Now edit the training source code to complete the following exercises:

	~~;TestBadFailure()~~
	*''' Your assignment:''' The test macro currently used in the test method <tt>TestBadFailure()</tt> can prevent subsequent test methods in the Test Unit from executing. This is sometimes useful, but here we want to change the Test Macro type that's used such that subsequent test methods will execute.
	** ''Hint:'' This function can be found in <tt>TestBasic.cpp</tt> in the <tt>sample_src</tt> directory.
	** ''Hint:'' You will probably want to read about [[Test Macros]]
	** ''Hint:'' Reading about [[Test Units]] is a good idea too

	;TestExercise()		;TestExercise()
Line 83:		Line 62:
	** ''Hint:'' You will use a [[Test Macros \| Test Macro]].		** ''Hint:'' You will use a [[Test Macros \| Test Macro]].

	===~~=Checking~~ Results====		=== Check Results ===

	* Before you rebuild <tt>TestApp.exe</tt>, you will need to shut it down by entering 'q' in its console window or closing the window directly.		* Before you rebuild <tt>TestApp.exe</tt>, you will need to shut it down by entering 'q' in its console window or closing the window directly.
Line 89:		Line 68:
	* After rebuilding, invoke <tt>TestApp.exe</tt> once again.		* After rebuilding, invoke <tt>TestApp.exe</tt> once again.

	* Execute only ''~~TestBasic_FList~~'' using the stride runner:		* Execute only ''TestBasic'' using the stride runner:

	> stride --options_file myoptions.txt --run ~~TestBasic_FList~~		> stride --options_file myoptions.txt --run TestBasic

	Loading database...		Loading database...
	Connecting to device...		Connecting to device...
	Executing...		Executing...
	test unit "~~TestBasic_FList~~"		test unit "TestBasic"
	> 4 passed, 2 failed, 0 in progress, 0 not in use.		> 4 passed, 1 failed, 0 in progress, 0 not in use.
	--------------------------------------------------------------		--------------------------------------------------------------
	Summary: 4 passed, 2 failed, 0 in progress, 0 not in use.		Summary: 4 passed, 1 failed, 0 in progress, 0 not in use.

	Disconnecting from device...		Disconnecting from device...
Line 116:		Line 95:
	--name YOURNAME		--name YOURNAME

	> stride --options_file myoptions.txt --run ~~TestBasic_FList --run TestBasic_CClass --run TestBasic_Class~~ --space TestBasic --upload		> stride --options_file myoptions.txt --run TestBasic --space TestBasic --upload

	Loading database...		Loading database...
	Connecting to device...		Connecting to device...
	Executing...		Executing...
	test unit "~~TestBasic_FList~~"		test unit "TestBasic"
	> 4 passed, ~~2 failed, 0 in progress, 0 not in use.~~		> 4 passed, 1 failed, 0 in progress, 0 not in use.
	~~test unit "TestBasic_CClass"~~
	~~> 4 passed, 2 failed, 0 in progress, 0 not in use.~~
	~~test unit "TestBasic_Class"~~
	~~> 4 passed, 2~~ failed, 0 in progress, 0 not in use.
	------------------------------------------------------------		------------------------------------------------------------
	Summary: 12 passed, 6 failed, 0 in progress, 0 not in use.		Summary: 4 passed, 1 failed, 0 in progress, 0 not in use.

	Disconnecting from device...		Disconnecting from device...

Jeffs: /* Objectives */

2013-01-23T22:46:38Z

Objectives

← Older revision		Revision as of 22:46, 23 January 2013
Line 19:		Line 19:
	These test units are implemented in two source files: '''TestBasic.cpp''' and '''TestBasic.h'''. The comments and descriptions are contained in '''TestBasic.h'''.		These test units are implemented in two source files: '''TestBasic.cpp''' and '''TestBasic.h'''. The comments and descriptions are contained in '''TestBasic.h'''.

	The Test Unit has test cases already implemented (used for reference) and has test ~~methods~~ that you are required to implement (called '''TestExercise'''). ~~This~~ method ~~simply sets~~ a ''NOT IN USE'' status ~~for the test method~~.		The Test Unit has test cases already implemented (used for reference) and has a test method that you are required to implement (called '''TestExercise'''). Currently this method is empty and returns a ''NOT IN USE'' status.

	'''IMPORTANT NOTE''' - As you look at this module's source code, you will note that the test methods (cases) within each Test Unit are '''exactly''' the same, regardless of packaging. (In fact the ''CClass'' and ''Class'' Test Units just call the ''C-based'' test functions used by the ''FList'' Test Unit.) The only difference is in the packaging of the test methods into each Test Unit.		'''IMPORTANT NOTE''' - As you look at this module's source code, you will note that the test methods (cases) within each Test Unit are '''exactly''' the same, regardless of packaging. (In fact the ''CClass'' and ''Class'' Test Units just call the ''C-based'' test functions used by the ''FList'' Test Unit.) The only difference is in the packaging of the test methods into each Test Unit.

Jeffs: /* Objectives */

2013-01-23T22:25:02Z

Objectives

← Older revision		Revision as of 22:25, 23 January 2013
Line 19:		Line 19:
	These test units are implemented in two source files: '''TestBasic.cpp''' and '''TestBasic.h'''. The comments and descriptions are contained in '''TestBasic.h'''.		These test units are implemented in two source files: '''TestBasic.cpp''' and '''TestBasic.h'''. The comments and descriptions are contained in '''TestBasic.h'''.

	The Test Unit has test cases already implemented (used for reference) and has ~~one~~ test ~~method~~ that you are required to implement (called '''TestExercise'''). ~~Currently this~~ method ~~is empty and returns~~ a ''NOT IN USE'' status.		The Test Unit has test cases already implemented (used for reference) and has test methods that you are required to implement (called '''TestExercise'''). This method simply sets a ''NOT IN USE'' status for the test method.

	'''IMPORTANT NOTE''' - As you look at this module's source code, you will note that the test methods (cases) within each Test Unit are '''exactly''' the same, regardless of packaging. (In fact the ''CClass'' and ''Class'' Test Units just call the ''C-based'' test functions used by the ''FList'' Test Unit.) The only difference is in the packaging of the test methods into each Test Unit.		'''IMPORTANT NOTE''' - As you look at this module's source code, you will note that the test methods (cases) within each Test Unit are '''exactly''' the same, regardless of packaging. (In fact the ''CClass'' and ''Class'' Test Units just call the ''C-based'' test functions used by the ''FList'' Test Unit.) The only difference is in the packaging of the test methods into each Test Unit.