Training Fixturing - Revision history

Jeffs: /* Run and Publish Results */

2013-01-31T21:25:32Z

Run and Publish Results

← Older revision		Revision as of 21:25, 31 January 2013
Line 70:		Line 70:
	=== 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 (myoptions.txt) ~~with the following if not already done:~~		When you have completed the Exercise(s) publish your results to Test Space (--space TestFixture). 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 TestFixture --space TestFixture --upload		> stride --options_file myoptions.txt --run TestFixture --space TestFixture --upload

Jeffs: /* Implement Exercise */

2013-01-29T17:33:32Z

Implement Exercise

← Older revision		Revision as of 17:33, 29 January 2013
Line 43:		Line 43:
	** Add a ''NOTE'' that will display the ''name'' of the test.		** Add a ''NOTE'' that will display the ''name'' of the test.
	** Validate that '''Sequence2''' is stored when starting the Thread by checking that "Sequence2" equals MyString[0].		** Validate that '''Sequence2''' is stored when starting the Thread by checking that "Sequence2" equals MyString[0].
	** ~~NOTE~~: The method to focus on in SUT is DoSequencing()		*** ''HINT'': The method to focus on in SUT is DoSequencing()
	** ~~NOTE~~: m_sequence is incremented as each method goes through Teardown.		*** ''HINT'': m_sequence is incremented as each method goes through Teardown.

	* '''TestFixture::Exercise2'''		* '''TestFixture::Exercise2'''

Jeffs: /* Build and Run TestApp */

2013-01-28T18:51:14Z

Build and Run TestApp

← Older revision		Revision as of 18:51, 28 January 2013
Line 19:		Line 19:
	* [[Building_an_Off-Target_Test_App#Build_Steps \| Build TestApp]] using SDK makefile		* [[Building_an_Off-Target_Test_App#Build_Steps \| Build TestApp]] using SDK makefile
	* Startup TestApp		* Startup TestApp
	* If not ~~already done~~, ~~create an~~ [[~~Stride_Runner~~#~~Options~~ \| ~~option file~~]] ~~(myoptions.txt) using the following content (Windows example)~~		* If you have not created an option file, please refer to [[Training_Getting_Started#Run_Training_Tests\| setup]]

	~~##### Command Line Options ######~~
	~~--device "TCP:localhost:8000"~~
	~~--database "%STRIDE_DIR%\SDK\Windows\out\TestApp.sidb"~~
	~~--output "%STRIDE_DIR%\SDK\Windows\sample_src\TestApp.xml"~~
	~~--log_level all~~

	* Execute ''Test Fixture'' Test Unit only		* Execute ''Test Fixture'' Test Unit only

Jeffs: /* Implement Exercise */

2013-01-25T00:52:22Z

Implement Exercise

← Older revision		Revision as of 00:52, 25 January 2013
Line 49:		Line 49:
	** Add a ''NOTE'' that will display the ''name'' of the test.		** Add a ''NOTE'' that will display the ''name'' of the test.
	** Validate that '''Sequence2''' is stored when starting the Thread by checking that "Sequence2" equals MyString[0].		** Validate that '''Sequence2''' is stored when starting the Thread by checking that "Sequence2" equals MyString[0].
	** ~~Note that~~ m_sequence is incremented as each method goes through Teardown.		** NOTE: The method to focus on in SUT is DoSequencing()
			** NOTE: m_sequence is incremented as each method goes through Teardown.

	* '''TestFixture::Exercise2'''		* '''TestFixture::Exercise2'''

Marku: /* Implement Exercise */

2013-01-25T00:41:17Z

Implement Exercise

← Older revision		Revision as of 00:41, 25 January 2013
Line 48:		Line 48:
	* '''TestFixture::Exercise1'''		* '''TestFixture::Exercise1'''
	** Add a ''NOTE'' that will display the ''name'' of the test.		** Add a ''NOTE'' that will display the ''name'' of the test.
	** Validate that '''Sequence2''' is ~~persisted~~ when starting the Thread by checking that "Sequence2" equals MyString[0].		** Validate that '''Sequence2''' is stored when starting the Thread by checking that "Sequence2" equals MyString[0].
	** Note that m_sequence is incremented as each method goes through Teardown.		** Note that m_sequence is incremented as each method goes through Teardown.

Jeffs: /* Implement Exercise */

2013-01-24T21:05:08Z

Implement Exercise

← Older revision		Revision as of 21:05, 24 January 2013
Line 47:		Line 47:

	* '''TestFixture::Exercise1'''		* '''TestFixture::Exercise1'''
	** Add a ''NOTE'' that will display the ''name'' of the test		** Add a ''NOTE'' that will display the ''name'' of the test.
	** Validate that '''Sequence2''' is persisted when starting the Thread		** Validate that '''Sequence2''' is persisted when starting the Thread by checking that "Sequence2" equals MyString[0].
	** Note that m_sequence is incremented as each method goes through Teardown.		** Note that m_sequence is incremented as each method goes through Teardown.

Jeffs: /* Implement Exercise */

2013-01-23T23:54:50Z

Implement Exercise

← Older revision		Revision as of 23:54, 23 January 2013
Line 49:		Line 49:
	** Add a ''NOTE'' that will display the ''name'' of the test		** Add a ''NOTE'' that will display the ''name'' of the test
	** Validate that '''Sequence2''' is persisted when starting the Thread		** Validate that '''Sequence2''' is persisted when starting the Thread
			** Note that m_sequence is incremented as each method goes through Teardown.

	* '''TestFixture::Exercise2'''		* '''TestFixture::Exercise2'''

Marku: /* Build and Run TestApp */

2012-02-17T01:49:16Z

Build and Run TestApp

← Older revision		Revision as of 01:49, 17 February 2012
Line 17:		Line 17:
	=== Build and Run TestApp ===		=== Build and Run TestApp ===

	* Build TestApp using SDK makefile		* [[Building_an_Off-Target_Test_App#Build_Steps \| Build TestApp]] using SDK makefile
	* Startup TestApp		* Startup TestApp
	* If not already done, create an [[Stride_Runner#Options \| option file]] (myoptions.txt) using the following content (Windows example)		* If not already done, create an [[Stride_Runner#Options \| option file]] (myoptions.txt) using the following content (Windows example)
Line 42:		Line 42:
	Saving result file...		Saving result file...

	* Review the details of the test results using a Browser. Open ~~'''~~TestApp.xml~~'''~~ which can be found in the ''sample_src'' directory (based on the ''output'' option). By opening the xml file in a web browser the xsl is automatically applied to create html.		* Review the details of the test results using a Browser. Open [[Building_an_Off-Target_Test_App#Interpreting_Results \| TestApp.xml ]] which can be found in the ''sample_src'' directory (based on the ''output'' option). By opening the xml file in a web browser the xsl is automatically applied to create html.

	=== Implement Exercise ===		=== Implement Exercise ===

Ivailop: /* Instructions */

2012-02-10T00:55:46Z

Instructions

← Older revision		Revision as of 00:55, 10 February 2012
Line 59:		Line 59:
	* Execute only ''TestFixture''		* Execute only ''TestFixture''

	> stride -O myoptions.txt --run TestFixture		> stride --options_file myoptions.txt --run TestFixture

	Loading database...		Loading database...
Line 82:		Line 82:
	--name YOURNAME		--name YOURNAME

	> stride -O myoptions.txt --run TestFixture --space TestFixture --upload		> stride --options_file myoptions.txt --run TestFixture --space TestFixture --upload

	Note: This space has been set up with a Baseline of [[Training_Getting_Started#Test_Space_Access \| ''expected test results'']] that you can use to validate your results.		Note: This space has been set up with a Baseline of [[Training_Getting_Started#Test_Space_Access \| ''expected test results'']] that you can use to validate your results.

Timd: /* Build and Run TestApp */

2011-12-09T23:20:13Z

Build and Run TestApp

← Older revision		Revision as of 23:20, 9 December 2011
Line 29:		Line 29:
	* Execute ''Test Fixture'' Test Unit only		* Execute ''Test Fixture'' Test Unit only

	> stride -O myoptions.txt --run TestFixture		> stride -options_file myoptions.txt --run TestFixture

	Loading database...		Loading database...