Running and Publishing the TestIntro Sample - Revision history

Ivailop: /* Running Test Intro Samples and Publishing Results to Test Space */

2013-02-20T20:52:02Z

Running Test Intro Samples and Publishing Results to Test Space

← Older revision		Revision as of 20:52, 20 February 2013
Line 20:		Line 20:
	--device TCP:localhost:8000		--device TCP:localhost:8000
	--upload		--upload
	--testspace ~~https://~~USER:PASS@mycompany.stridetestspace.com		--testspace USER:PASS@mycompany.stridetestspace.com
	--project Training		--project Training
	--space TestIntro		--space TestIntro

Marku: /* Building Instrumented Source Under Test */

2011-06-14T21:53:15Z

Building Instrumented Source Under Test

← Older revision		Revision as of 21:53, 14 June 2011
Line 4:		Line 4:
	To begin, be sure that TestApp is not running, then copy the <tt>.c</tt> and <tt>.h</tt> files found in <tt>Samples/test_in_c_cpp/TestIntro</tt> to <tt>SDK/Windows/sample_src</tt> (or <tt>SDK/Posix/sample_src</tt> for Linux).		To begin, be sure that TestApp is not running, then copy the <tt>.c</tt> and <tt>.h</tt> files found in <tt>Samples/test_in_c_cpp/TestIntro</tt> to <tt>SDK/Windows/sample_src</tt> (or <tt>SDK/Posix/sample_src</tt> for Linux).

	Once the files have been copied to <tt>sample_src</tt>, simply build TestApp as described in [[~~Off~~-~~Target Test App~~ \| here]].		Once the files have been copied to <tt>sample_src</tt>, simply build TestApp as described in [[Building_an_Off-Target_Test_App \| here]].

	== Running Test Intro Samples and Publishing Results to Test Space ==		== Running Test Intro Samples and Publishing Results to Test Space ==

Ivailop at 17:30, 9 June 2011

2011-06-09T17:30:33Z

← Older revision		Revision as of 17:30, 9 June 2011
Line 2:		Line 2:
	In this step, will will add a set of sample tests that provide an overview of STRIDE testing techniques. The [[Test Intro Sample]] tests are described in the linked article.		In this step, will will add a set of sample tests that provide an overview of STRIDE testing techniques. The [[Test Intro Sample]] tests are described in the linked article.

	To begin, be sure that TestApp is not running, then copy the <tt>.c</tt> and <tt>.h</tt> files found in <tt>Samples/test_in_c_cpp/TestIntro</tt> to <tt>SDK/Windows/sample_src</tt> (or <tt>SDK/Posix/sample_src</tt> for ~~Posix~~).		To begin, be sure that TestApp is not running, then copy the <tt>.c</tt> and <tt>.h</tt> files found in <tt>Samples/test_in_c_cpp/TestIntro</tt> to <tt>SDK/Windows/sample_src</tt> (or <tt>SDK/Posix/sample_src</tt> for Linux).

	Once the files have been copied to <tt>sample_src</tt>, simply build TestApp as described in [[Off-Target Test App \| here]].		Once the files have been copied to <tt>sample_src</tt>, simply build TestApp as described in [[Off-Target Test App \| here]].
Line 31:		Line 31:
	* If you setup [[STRIDE_Runner#Environment_Variables \| environment variables]] for the '''project''' and / or '''space''' they are not required in the option file. Note: Command line options override environment variables.		* If you setup [[STRIDE_Runner#Environment_Variables \| environment variables]] for the '''project''' and / or '''space''' they are not required in the option file. Note: Command line options override environment variables.

	The command line is very long, so we'll want to create a text file named ''RunTestIntro.txt'' in the <tt>SDK\Windows</tt> (or <tt>SDK/Posix</tt> for ~~Posix~~) directory as an option file to submit to <tt>stride</tt>.		The command line is very long, so we'll want to create a text file named ''RunTestIntro.txt'' in the <tt>SDK\Windows</tt> (or <tt>SDK/Posix</tt> for Linux) directory as an option file to submit to <tt>stride</tt>.

	If you haven't done so already, start <tt>TestApp</tt> running in a separate console window.		If you haven't done so already, start <tt>TestApp</tt> running in a separate console window.

Ivailop at 17:11, 9 June 2011

2011-06-09T17:11:31Z

← Older revision		Revision as of 17:11, 9 June 2011
Line 2:		Line 2:
	In this step, will will add a set of sample tests that provide an overview of STRIDE testing techniques. The [[Test Intro Sample]] tests are described in the linked article.		In this step, will will add a set of sample tests that provide an overview of STRIDE testing techniques. The [[Test Intro Sample]] tests are described in the linked article.

	To begin, be sure that TestApp is not running, then copy the <tt>.c</tt> and <tt>.h</tt> files found in <tt>Samples/test_in_c_cpp/TestIntro</tt> to <tt>SDK/Windows/sample_src</tt> (or <tt>SDK/~~Linux~~/sample_src</tt> for ~~Linux~~).		To begin, be sure that TestApp is not running, then copy the <tt>.c</tt> and <tt>.h</tt> files found in <tt>Samples/test_in_c_cpp/TestIntro</tt> to <tt>SDK/Windows/sample_src</tt> (or <tt>SDK/Posix/sample_src</tt> for Posix).

	Once the files have been copied to <tt>sample_src</tt>, simply build TestApp as described in [[Off-Target Test App \| here]].		Once the files have been copied to <tt>sample_src</tt>, simply build TestApp as described in [[Off-Target Test App \| here]].
Line 31:		Line 31:
	* If you setup [[STRIDE_Runner#Environment_Variables \| environment variables]] for the '''project''' and / or '''space''' they are not required in the option file. Note: Command line options override environment variables.		* If you setup [[STRIDE_Runner#Environment_Variables \| environment variables]] for the '''project''' and / or '''space''' they are not required in the option file. Note: Command line options override environment variables.

	The command line is very long, so we'll want to create a text file named ''RunTestIntro.txt'' in the <tt>SDK\Windows</tt> (or <tt>SDK/~~Linux~~</tt> for ~~Linux~~) directory as an option file to submit to <tt>stride</tt>.		The command line is very long, so we'll want to create a text file named ''RunTestIntro.txt'' in the <tt>SDK\Windows</tt> (or <tt>SDK/Posix</tt> for Posix) directory as an option file to submit to <tt>stride</tt>.

	If you haven't done so already, start <tt>TestApp</tt> running in a separate console window.		If you haven't done so already, start <tt>TestApp</tt> running in a separate console window.

	Now run stride as follows (starting from the <tt>SDK\Windows</tt> or <tt>SDK/~~Linux~~</tt> directory):		Now run stride as follows (starting from the <tt>SDK\Windows</tt> or <tt>SDK/Posix</tt> directory):

	<source lang="bash">		<source lang="bash">

Marku: /* Running Test Intro Samples and Publishing Results to Test Space */

2011-05-27T15:39:12Z

Running Test Intro Samples and Publishing Results to Test Space

← Older revision		Revision as of 15:39, 27 May 2011
Line 46:		Line 46:
	Connecting to device...		Connecting to device...
	Executing...		Executing...
	test ~~units~~ "s2_testintro_cclass"		test unit "s2_testintro_flist"
			> 2 passed, 1 failed, 0 in progress, 0 not in use.
			test unit "s2_testintro_cclass"
	> 1 passed, 1 failed, 0 in progress, 0 not in use.		> 1 passed, 1 failed, 0 in progress, 0 not in use.
	test ~~units "s2_testintro_flist"~~		test unit "s2_testintro_testdoubles"
	~~> 2 passed, 1 failed, 0 in progress, 0 not in use.~~
	~~test units~~ "s2_testintro_testdoubles"
	> 3 passed, 0 failed, 0 in progress, 0 not in use.		> 3 passed, 0 failed, 0 in progress, 0 not in use.
	test ~~units~~ "s2_testintro_testpoints"		test unit "s2_testintro_testpoints"
	> 3 passed, 0 failed, 0 in progress, 0 not in use.		> 3 passed, 0 failed, 0 in progress, 0 not in use.
			test unit "s2_testintro_parameters"
			> 2 passed, 0 failed, 0 in progress, 0 not in use.
	---------------------------------------------------------------------		---------------------------------------------------------------------
	Summary: 9 passed, 2 failed, 0 in progress, 0 not in use.		Summary: 11 passed, 2 failed, 0 in progress, 0 not in use.

	Disconnecting from device...		Disconnecting from device...
	Saving result file...		Saving result file...
	~~Uploading to test space...~~
	</pre>		</pre>

Marku: /* Running Test Intro Samples and Publishing Results to Test Space */

2011-02-23T23:53:45Z

Running Test Intro Samples and Publishing Results to Test Space

← Older revision		Revision as of 23:53, 23 February 2011
Line 21:		Line 21:
	--upload		--upload
	--testspace https://USER:PASS@mycompany.stridetestspace.com		--testspace https://USER:PASS@mycompany.stridetestspace.com
	--project ~~Sandbox~~		--project Training
	--space TestIntro		--space TestIntro
	</pre>		</pre>
Line 28:		Line 28:
	* You will have to replace ''USER:PASS'' with your S2-assigned TestSpace user name and password		* You will have to replace ''USER:PASS'' with your S2-assigned TestSpace user name and password
	* You will have to replace ''mycompany'' with your S2-assigned subdomain name		* You will have to replace ''mycompany'' with your S2-assigned subdomain name
	* The project "~~Sandbox~~" and TestSpace "TestIntro" have been pre-created within your company STRIDE TestSpace		* The project "Training" and TestSpace "TestIntro" have been pre-created within your company STRIDE TestSpace
			* If you setup [[STRIDE_Runner#Environment_Variables \| environment variables]] for the '''project''' and / or '''space''' they are not required in the option file. Note: Command line options override environment variables.

	The command line is very long, so we'll want to create a text file named ''RunTestIntro.txt'' in the <tt>SDK\Windows</tt> (or <tt>SDK/Linux</tt> for Linux) directory as an option file to submit to <tt>stride</tt>.		The command line is very long, so we'll want to create a text file named ''RunTestIntro.txt'' in the <tt>SDK\Windows</tt> (or <tt>SDK/Linux</tt> for Linux) directory as an option file to submit to <tt>stride</tt>.
Line 64:		Line 65:
	First navigate to the S2-provided TestSpace with your browser. The URL has the form: <nowiki>https://companyname.stridetestspace.com</nowiki>. On the page that is presented, enter your login credentials.		First navigate to the S2-provided TestSpace with your browser. The URL has the form: <nowiki>https://companyname.stridetestspace.com</nowiki>. On the page that is presented, enter your login credentials.

	At the top of the next page, click on the All Projects link to view the status of existing projects. Here you should see the ~~Sandbox~~ project listed, with its contained TestSpace ''TestIntro'' shown.		At the top of the next page, click on the All Projects link to view the status of existing projects. Here you should see the Training project listed, with its contained TestSpace ''TestIntro'' shown.

	Clicking the ''TestIntro'' link will present you with the ''TestIntro'' TestSpace page. From the top-line results at the bottom of the page you can drill down into the Sequence_1 results to see the test details.		Clicking the ''TestIntro'' link will present you with the ''TestIntro'' TestSpace page. From the top-line results at the bottom of the page you can drill down into the Sequence_1 results to see the test details.

Marku: /* Analyzing the Results */

2010-06-02T16:29:53Z

Analyzing the Results

← Older revision		Revision as of 16:29, 2 June 2010
Line 83:		Line 83:
	<references/>		<references/>

	[[Category:~~The Sandbox]]~~		[[Category:Installation]]
	~~[[Category:Samples~~]]

Ivailop: /* Running Test Intro Samples and Publishing Results to Test Space */

2010-05-17T22:06:56Z

Running Test Intro Samples and Publishing Results to Test Space

← Older revision		Revision as of 22:06, 17 May 2010
Line 11:		Line 11:
	Here we will run all tests in the <tt>TestApp.sidb</tt> database.<ref>Note that the S2 diagnostic tests are treated separately, and are not run unless the <tt>--diagnostics</tt> option is specified to <tt>stride</tt>.</ref>		Here we will run all tests in the <tt>TestApp.sidb</tt> database.<ref>Note that the S2 diagnostic tests are treated separately, and are not run unless the <tt>--diagnostics</tt> option is specified to <tt>stride</tt>.</ref>

	# Run TestApp in a console window ~~as in earlier steps~~.		# Run the build above TestApp in a console window.
	# Invoke <tt>stride</tt> in a separate console window (different from the running TestApp) -- as shown below and verify Summary results.		# Invoke <tt>stride</tt> in a separate console window (different from the running TestApp) -- as shown below and verify Summary results.

Ivailop: /* Running Test Intro Samples and Publishing Results to Test Space */

2010-05-15T00:16:41Z

Running Test Intro Samples and Publishing Results to Test Space

← Older revision		Revision as of 00:16, 15 May 2010
Line 30:		Line 30:
	* The project "Sandbox" and TestSpace "TestIntro" have been pre-created within your company STRIDE TestSpace		* The project "Sandbox" and TestSpace "TestIntro" have been pre-created within your company STRIDE TestSpace

	The command line is very long, so we'll want to create a text file named ''RunTestIntro.txt'' in the <tt>SDK~~/Linux~~</tt> (or <tt>SDK/~~Windows~~</tt> for ~~Windows~~) directory as an option file to submit to <tt>stride</tt>.		The command line is very long, so we'll want to create a text file named ''RunTestIntro.txt'' in the <tt>SDK\Windows</tt> (or <tt>SDK/Linux</tt> for Linux) directory as an option file to submit to <tt>stride</tt>.

	If you haven't done so already, start <tt>TestApp</tt> running in a separate console window.		If you haven't done so already, start <tt>TestApp</tt> running in a separate console window.

	Now run stride as follows (starting from the <tt>SDK~~/Linux~~</tt> or <tt>SDK~~\Windows~~</tt> directory):		Now run stride as follows (starting from the <tt>SDK\Windows</tt> or <tt>SDK/Linux</tt> directory):

	<source lang="bash">		<source lang="bash">

Ivailop: /* Building Instrumented Source Under Test */

2010-05-15T00:14:50Z

Building Instrumented Source Under Test

← Older revision		Revision as of 00:14, 15 May 2010
Line 2:		Line 2:
	In this step, will will add a set of sample tests that provide an overview of STRIDE testing techniques. The [[Test Intro Sample]] tests are described in the linked article.		In this step, will will add a set of sample tests that provide an overview of STRIDE testing techniques. The [[Test Intro Sample]] tests are described in the linked article.

	To begin, be sure that TestApp is not running, then copy the <tt>.c</tt> and <tt>.h</tt> files found in <tt>Samples/test_in_c_cpp/TestIntro</tt> to <tt>SDK/Windows/sample_src</tt> (or <tt>SDK/Linux/sample_src</tt>).		To begin, be sure that TestApp is not running, then copy the <tt>.c</tt> and <tt>.h</tt> files found in <tt>Samples/test_in_c_cpp/TestIntro</tt> to <tt>SDK/Windows/sample_src</tt> (or <tt>SDK/Linux/sample_src</tt> for Linux).

	Once the files have been copied to <tt>sample_src</tt>, simply build TestApp as described in [[Off-Target Test App \| here]].		Once the files have been copied to <tt>sample_src</tt>, simply build TestApp as described in [[Off-Target Test App \| here]].