Training File IO - Revision history

Jeffs: /* Run and Publish Results */

2013-02-01T19:02:35Z

Run and Publish Results

← Older revision		Revision as of 19:02, 1 February 2013
Line 64:		Line 64:
	=== 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. 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 TestFile --space TestFile --upload		> stride --options_file myoptions.txt --run TestFile --space TestFile --upload

Jeffs: /* Implement Exercise */

2013-02-01T17:30:37Z

Implement Exercise

← Older revision		Revision as of 17:30, 1 February 2013
Line 40:		Line 40:

	* Read data content ''TestFileInput.dat'' file created from the previous test method (SDK\Windows or SDK/Posix).		* Read data content ''TestFileInput.dat'' file created from the previous test method (SDK\Windows or SDK/Posix).
			** ''Hint:'' You will probably want to read about [[File Transfer Services]]
	* Make sure to Exit the test if an error occurs when opening file(s) (i.e. use '''srEXIT_XX''')		* Make sure to Exit the test if an error occurs when opening file(s) (i.e. use '''srEXIT_XX''')
	* Take a summation of the data content using ''sut_add()''		* Take a summation of the data content using ''sut_add()''

Jeffs: /* Build and Run TestApp */

2013-01-28T18:52:42Z

Build and Run TestApp

← Older revision		Revision as of 18:52, 28 January 2013
Line 18:		Line 18:
	* [[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 File'' Test Unit only		* Execute ''Test File'' Test Unit only

Jeffs: /* Implement Exercise */

2013-01-24T00:02:19Z

Implement Exercise

← Older revision		Revision as of 00:02, 24 January 2013
Line 45:		Line 45:
	=== Implement Exercise ===		=== Implement Exercise ===

	* Read data content ''TestFileInput.dat'' file created from the previous test method		* Read data content ''TestFileInput.dat'' file created from the previous test method (SDK\Windows or SDK/Posix).
	* Make sure to Exit the test if an error occurs when opening file(s) (i.e. use '''srEXIT_XX''')		* Make sure to Exit the test if an error occurs when opening file(s) (i.e. use '''srEXIT_XX''')
	* Take a summation of the data content using ''sut_add()''		* Take a summation of the data content using ''sut_add()''

Marku: /* Build and Run TestApp */

2012-02-17T01:52:14Z

Build and Run TestApp

← Older revision		Revision as of 01:52, 17 February 2012
Line 16:		Line 16:
	=== 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 41:		Line 41:
	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:26Z

Instructions

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

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

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

	> stride -O myoptions.txt --run TestFile --space TestFile --upload		> stride --options_file myoptions.txt --run TestFile --space TestFile --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:22:13Z

Build and Run TestApp

← Older revision		Revision as of 23:22, 9 December 2011
Line 28:		Line 28:
	* Execute ''Test File'' Test Unit only		* Execute ''Test File'' Test Unit only

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

	Loading database...		Loading database...

Ivailop: /* Instructions */

2011-11-29T00:37:20Z

Instructions

← Older revision		Revision as of 00:37, 29 November 2011
Line 22:		Line 22:
	##### Command Line Options ######		##### Command Line Options ######
	--device "TCP:localhost:8000"		--device "TCP:localhost:8000"
	--database %STRIDE_DIR%\SDK\Windows\out\TestApp.sidb		--database "%STRIDE_DIR%\SDK\Windows\out\TestApp.sidb"
	--output %STRIDE_DIR%\SDK\Windows\sample_src\TestApp.xml		--output "%STRIDE_DIR%\SDK\Windows\sample_src\TestApp.xml"
	--log_level all		--log_level all

Ivailop at 22:24, 31 August 2011

2011-08-31T22:24:55Z

← Older revision		Revision as of 22:24, 31 August 2011
Line 1:		Line 1:
	= Objectives =		== Objectives ==

	This Training Module is focused on leveraging [[File_Transfer_Services \| File IO]] from the context of a Test Unit executing on a target. The module covers the following:		This Training Module is focused on leveraging [[File_Transfer_Services \| File IO]] from the context of a Test Unit executing on a target. The module covers the following:
Line 12:		Line 12:
	The Test Unit has test cases already implemented (used for reference) and has one 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 one test method that you are required to implement (called '''Exercise'''). Currently this method is empty and returns a ''NOT IN USE'' status.

	= Instructions =		== Instructions ==

	== Build and Run TestApp ==		=== Build and Run TestApp ===

	* Build TestApp using SDK makefile		* Build TestApp using SDK makefile
Line 43:		Line 43:
	* 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 '''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 ===

	* Read data content ''TestFileInput.dat'' file created from the previous test method		* Read data content ''TestFileInput.dat'' file created from the previous test method
Line 67:		Line 67:
	Saving result file...		Saving result file...

	== 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. To make it easier for now we recommend that you update your existing option file (myoptions.txt) with the following if not already done:
Line 81:		Line 81:
	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.

	= Reference =		== Reference ==
	The following reference information is related to passing parameters to Test Units.		The following reference information is related to passing parameters to Test Units.

	== Wiki ==		=== Wiki ===
	* [[File_Transfer_Services \| File Transfer Services]] - important information for using file operations on host file from test code executing on the target		* [[File_Transfer_Services \| File Transfer Services]] - important information for using file operations on host file from test code executing on the target
	** Review ''srFileOpen()'' and ''srFileClose()''		** Review ''srFileOpen()'' and ''srFileClose()''
Line 90:		Line 90:
	** Other references as needed		** Other references as needed

	== Samples ==		=== Samples ===
	* [[File_Services_Sample \| File Services Sample]] - presents a few basic examples of how to use the File Transfer Services API to interact with the host file system.		* [[File_Services_Sample \| File Services Sample]] - presents a few basic examples of how to use the File Transfer Services API to interact with the host file system.

Timd at 00:02, 27 August 2011

2011-08-27T00:02:46Z

← Older revision		Revision as of 00:02, 27 August 2011
Line 1:		Line 1:
	= Objectives =		= Objectives =

	This Training Module is focused on leveraging [[File_Transfer_Services \| File IO]] from the context of a Test Unit executing on a target. The module ~~focuses on~~ the following:		This Training Module is focused on leveraging [[File_Transfer_Services \| File IO]] from the context of a Test Unit executing on a target. The module covers the following:
	* Accessing host based files		* Accessing host based files
	* Read and Writing content to / from host files		* Read and Writing content to / from host files


	There are two test files used -- '''TestFile.cpp & TestFile.h''' -- that ~~contains~~ one Test Unit:		There are two test files used -- '''TestFile.cpp & TestFile.h''' -- that implement one Test Unit:
	* '''TestFile'''		* '''TestFile'''


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

	= Instructions =		= Instructions =
Line 18:		Line 18:
	* Build TestApp using SDK makefile		* Build TestApp using SDK makefile
	* Startup TestApp		* Startup TestApp
	* ~~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)

	##### Command Line Options ######		##### Command Line Options ######
Line 45:		Line 45:
	== Implement Exercise ==		== Implement Exercise ==

	* Read data content ''TestFileInput.dat'' file created from previous test method		* Read data content ''TestFileInput.dat'' file created from the previous test method
	* Make sure to Exit test if error occurs when opening file(s) (i.e. use '''srEXIT_XX''')		* Make sure to Exit the test if an error occurs when opening file(s) (i.e. use '''srEXIT_XX''')
	* Take a summation of the data content using ''sut_add()''		* Take a summation of the data content using ''sut_add()''
	* Validate summation with content in ''TestFileSum.dat'' file		* Validate summation with content in ''TestFileSum.dat'' file
	* Add a ''NOTE"" capturing important information such as ''bytes read'', ''summation'', etc. _		* Add a ''NOTE'' capturing important information such as ''bytes read'', ''summation'', etc. _


Line 69:		Line 69:
	== 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:		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:

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