Training Runtime API - Revision history

Ivailop: /* Objectives */

2014-08-05T19:43:07Z

Objectives

← Older revision		Revision as of 19:43, 5 August 2014
Line 3:		Line 3:
	This Training Module is focused leveraging the [[Runtime_Test_Services \| Runtime APIs]] in the context of writing a test. The module covers the following topics:		This Training Module is focused leveraging the [[Runtime_Test_Services \| Runtime APIs]] in the context of writing a test. The module covers the following topics:
	* How to set [[Runtime_Test_Services#srTestCaseSetStatus \| test status]]		* How to set [[Runtime_Test_Services#srTestCaseSetStatus \| test status]]
	* Adding [[Runtime_Test_Services#srTestCaseAddAnnotation \| test ~~annotation~~]] and attaching [[Runtime_Test_Services#srTestAnnotationAddComment \| comments]] to it		* Adding [[Runtime_Test_Services#srTestCaseAddAnnotation \| test annotations]] and attaching [[Runtime_Test_Services#srTestAnnotationAddComment \| comments]] to them
	* Dynamically creating [[Runtime_Test_Services#srTestSuiteAddCase \| test cases]]		* Dynamically creating [[Runtime_Test_Services#srTestSuiteAddCase \| test cases]]

Ivailop: /* Objectives */

2014-08-05T19:42:44Z

Objectives

← Older revision		Revision as of 19:42, 5 August 2014
Line 3:		Line 3:
	This Training Module is focused leveraging the [[Runtime_Test_Services \| Runtime APIs]] in the context of writing a test. The module covers the following topics:		This Training Module is focused leveraging the [[Runtime_Test_Services \| Runtime APIs]] in the context of writing a test. The module covers the following topics:
	* How to set [[Runtime_Test_Services#srTestCaseSetStatus \| test status]]		* How to set [[Runtime_Test_Services#srTestCaseSetStatus \| test status]]
	* ~~Setting~~ [[Runtime_Test_Services#~~srTestCaseSetName~~ \| test ~~case name~~]] and [[Runtime_Test_Services#~~srTestCaseSetDescription~~ \| ~~description~~]] ~~directly via the API~~		* Adding [[Runtime_Test_Services#srTestCaseAddAnnotation \| test annotation]] and attaching [[Runtime_Test_Services#srTestAnnotationAddComment \| comments]] to it
	* Setting [[Runtime_Test_Services#srTestSuiteSetName \| test suite name]] and [[Runtime_Test_Services#srTestSuiteSetDescription \| description]] directly via the API		* Dynamically creating [[Runtime_Test_Services#srTestSuiteAddCase \| test cases]]
	* Dynamically creating ~~[[Runtime_Test_Services#srTestSuiteAddSuite \| test suites]] and~~ [[Runtime_Test_Services#srTestSuiteAddCase \| test cases]]

Ivailop: /* Wiki */

2014-08-05T19:36:30Z

Wiki

← Older revision		Revision as of 19:36, 5 August 2014
Line 97:		Line 97:

	* [[Runtime_Test_Services#C_Test_Functions \| Runtime Test Services]] with special attention to the following:		* [[Runtime_Test_Services#C_Test_Functions \| Runtime Test Services]] with special attention to the following:
	** Review srTestCaseSetDescription()
	** Review srTestCaseSetStatus()		** Review srTestCaseSetStatus()
	** Review ~~srTestCaseSetName~~()		** Review srTestCaseAddAnnotation()
	** Review ~~srTestCaseAddComment~~()		** Review srTestAnnotationAddComment()
	** Review srTestSuiteAddCase()		** Review srTestSuiteAddCase()
	** Review srTestSuiteAddSuite()
	** Review srTestSuiteSetDescription()
	** Review srTestSuiteSetName()


	=== Samples ===		=== Samples ===

Jeffs: /* Run and Publish Results */

2013-02-01T19:03:34Z

Run and Publish Results

← Older revision		Revision as of 19:03, 1 February 2013
Line 86:		Line 86:

	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]].		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]].


	> stride --options_file myoptions.txt --run TestRuntime_Static --run TestRuntime_Dynamic --space TestRuntime --upload		> stride --options_file myoptions.txt --run TestRuntime_Static --run TestRuntime_Dynamic --space TestRuntime --upload

Jeffs: /* Run and Publish Results */

2013-02-01T19:03:21Z

Run and Publish Results

← Older revision		Revision as of 19:03, 1 February 2013
Line 85:		Line 85:
	=== 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 TestRuntime_Static --run TestRuntime_Dynamic --space TestRuntime --upload		> stride --options_file myoptions.txt --run TestRuntime_Static --run TestRuntime_Dynamic --space TestRuntime --upload

Jeffs: /* Implement Exercise */

2013-02-01T18:46:38Z

Implement Exercise

← Older revision		Revision as of 18:46, 1 February 2013
Line 46:		Line 46:
	* '''TestRuntime_Static::Exercise'''		* '''TestRuntime_Static::Exercise'''
	** Validate the ''sut_mult()'' routine using some simple data input		** Validate the ''sut_mult()'' routine using some simple data input
			*** ''Hint:'' You will probably want to read about [[Runtime Test Services]]
	** Set the ''test method'' name to '''Mult'''		** Set the ''test method'' name to '''Mult'''
	** Use direct Runtime APIs to:		** Use direct Runtime APIs to:

Jeffs: /* Build and Run TestApp */

2013-01-28T18:52:07Z

Build and Run TestApp

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

Jeffs: /* Implement Exercise */

2013-01-23T23:57:33Z

Implement Exercise

← Older revision		Revision as of 23:57, 23 January 2013
Line 63:		Line 63:
	** Add a new Test Suite using '''Exercise''' for the name		** Add a new Test Suite using '''Exercise''' for the name
	** Write a loop generating a dynamic test case using ''NumberOfTestCases''		** Write a loop generating a dynamic test case using ''NumberOfTestCases''
	*** Test Case name shall be '''Test_n''' where "n" is the loop count		*** Test Case name shall be '''Test_n''' where "n" is the loop count as each case must have a unique name.
	*** Add a description for each test case		*** Add a description for each test case
	*** Validate ''sut_foo()'' using the loop count		*** Validate ''sut_foo()'' using the loop count
Line 87:		Line 87:
	Disconnecting from device...		Disconnecting from device...
	Saving result file...		Saving result file...


	=== Run and Publish Results ===		=== Run and Publish Results ===

Marku: /* Build and Run TestApp */

2012-02-17T01:51:20Z

Build and Run TestApp

← Older revision		Revision as of 01:51, 17 February 2012
Line 19:		Line 19:
	=== 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 46:		Line 46:
	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:56:58Z

Instructions

← Older revision		Revision as of 00:56, 10 February 2012
Line 73:		Line 73:
	* Execute ''Test Runtime API'' Test Units only (NOTE - requires passing parameter)		* Execute ''Test Runtime API'' Test Units only (NOTE - requires passing parameter)

	> stride -O myoptions.txt --run TestRuntime_Static --run TestRuntime_Dynamic(5)		> stride --options_file myoptions.txt --run TestRuntime_Static --run TestRuntime_Dynamic(5)

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

	> stride -O myoptions.txt --run TestRuntime_Static --run TestRuntime_Dynamic --space TestRuntime --upload		> stride --options_file myoptions.txt --run TestRuntime_Static --run TestRuntime_Dynamic --space TestRuntime --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.

← Older revision		Revision as of 19:43, 5 August 2014
Line 3:		Line 3:
	This Training Module is focused leveraging the [[Runtime_Test_Services \| Runtime APIs]] in the context of writing a test. The module covers the following topics:		This Training Module is focused leveraging the [[Runtime_Test_Services \| Runtime APIs]] in the context of writing a test. The module covers the following topics:
	* How to set [[Runtime_Test_Services#srTestCaseSetStatus \| test status]]		* How to set [[Runtime_Test_Services#srTestCaseSetStatus \| test status]]
	* Adding [[Runtime_Test_Services#srTestCaseAddAnnotation \| test ~~annotation~~]] and attaching [[Runtime_Test_Services#srTestAnnotationAddComment \| comments]] to it		* Adding [[Runtime_Test_Services#srTestCaseAddAnnotation \| test annotations]] and attaching [[Runtime_Test_Services#srTestAnnotationAddComment \| comments]] to them
	* Dynamically creating [[Runtime_Test_Services#srTestSuiteAddCase \| test cases]]		* Dynamically creating [[Runtime_Test_Services#srTestSuiteAddCase \| test cases]]

← Older revision		Revision as of 19:42, 5 August 2014
Line 3:		Line 3:
	This Training Module is focused leveraging the [[Runtime_Test_Services \| Runtime APIs]] in the context of writing a test. The module covers the following topics:		This Training Module is focused leveraging the [[Runtime_Test_Services \| Runtime APIs]] in the context of writing a test. The module covers the following topics:
	* How to set [[Runtime_Test_Services#srTestCaseSetStatus \| test status]]		* How to set [[Runtime_Test_Services#srTestCaseSetStatus \| test status]]
	* ~~Setting~~ [[Runtime_Test_Services#~~srTestCaseSetName~~ \| test ~~case name~~]] and [[Runtime_Test_Services#~~srTestCaseSetDescription~~ \| ~~description~~]] ~~directly via the API~~		* Adding [[Runtime_Test_Services#srTestCaseAddAnnotation \| test annotation]] and attaching [[Runtime_Test_Services#srTestAnnotationAddComment \| comments]] to it
	* Setting [[Runtime_Test_Services#srTestSuiteSetName \| test suite name]] and [[Runtime_Test_Services#srTestSuiteSetDescription \| description]] directly via the API		* Dynamically creating [[Runtime_Test_Services#srTestSuiteAddCase \| test cases]]
	* Dynamically creating ~~[[Runtime_Test_Services#srTestSuiteAddSuite \| test suites]] and~~ [[Runtime_Test_Services#srTestSuiteAddCase \| test cases]]