Running and Publishing the Expectations Sample - Revision history

Ivailop: /* Publishing Results to Test Space */

2013-02-20T20:53:36Z

Publishing Results to Test Space

← Older revision		Revision as of 20:53, 20 February 2013
Line 52:		Line 52:
	<pre>		<pre>
	--upload		--upload
	--testspace ~~https://~~USER:PASS@mycompany.stridetestspace.com		--testspace USER:PASS@mycompany.stridetestspace.com
	--project Sandbox		--project Sandbox
	--space Samples		--space Samples

Marku: /* Building Instrumented Source Under Test */

2011-06-14T21:53:43Z

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_scrips/Expectations</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_scrips/Expectations</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 Expectations Sample ==		== Running Expectations Sample ==

Ivailop at 17:29, 9 June 2011

2011-06-09T17:29:55Z

← Older revision		Revision as of 17:29, 9 June 2011
Line 2:		Line 2:
	In this step, we will add pre-instrumented example source that provide an overview of STRIDE instrumentation techniques. The [[Expectations Sample]] sources are described in the linked article.		In this step, we will add pre-instrumented example source that provide an overview of STRIDE instrumentation techniques. The [[Expectations Sample]] sources 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_scrips/Expectations</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_scrips/Expectations</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 21:		Line 21:
	</pre>		</pre>

	The command line arguments are very long, so we'll want to create a text file named ''RunSample.txt'' (for example) 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 arguments are very long, so we'll want to create a text file named ''RunSample.txt'' (for example) 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.

	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: /* Publishing Results to Test Space */

2010-12-08T21:15:45Z

Publishing Results to Test Space

← Older revision		Revision as of 21:15, 8 December 2010
Line 85:		Line 85:
	* 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 "Expectations" ~~have been pre-~~created within your company STRIDE TestSpace		* The project "Sandbox" and TestSpace "Expectations" should already be created within your company STRIDE TestSpace


Line 93:		Line 93:
	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 ''Expectations'' 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 Sandbox project listed, with its contained TestSpace ''Expectations'' shown.

	Clicking the ''Expectations'' link will present you with the ''Expectations'' 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 ''Expectations'' link will present you with the ''Expectations'' TestSpace page. From the top-line results at the bottom of the page you can drill down into the Sequence_1 (assuming this is the first time publishing) results to see the test details.

	=== Analyzing the Results ===		=== Analyzing the Results ===

Marku: /* Publishing Results to Test Space */

2010-12-08T21:12:11Z

Publishing Results to Test Space

← Older revision		Revision as of 21:12, 8 December 2010
Line 71:		Line 71:
	Executing...		Executing...
	test module "C:\stride\Samples\test_in_script\Expectations\s2_expectations_testmodule.pm"...		test module "C:\stride\Samples\test_in_script\Expectations\s2_expectations_testmodule.pm"...
	> 3 passed, 1 failed, 0 in progress, 0 not in use.		> 12 passed, 2 failed, 0 in progress, 0 not in use.
	---------------------------------------------------------------------		---------------------------------------------------------------------
	Summary: 3 passed, 1 failed, 0 in progress, 0 not in use.		Summary: 12 passed, 2 failed, 0 in progress, 0 not in use.

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

Marku: /* Running Expectation Sample */

2010-12-08T21:10:34Z

Running Expectation Sample

← Older revision		Revision as of 21:10, 8 December 2010
Line 6:		Line 6:
	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]].

	== Running ~~Expectation~~ Sample ==		== Running Expectations Sample ==

	Here we will run the test module that is provided in this example .		Here we will run the test module that is provided in this example .
Line 21:		Line 21:
	</pre>		</pre>

	The command line arguments are very long, so we'll want to create a text file named ''RunSample.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 arguments are very long, so we'll want to create a text file named ''RunSample.txt'' (for example) 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.
Line 38:		Line 38:
	Executing...		Executing...
	test module "C:\stride\Samples\test_in_script\Expectations\s2_expectations_testmodule.pm"...		test module "C:\stride\Samples\test_in_script\Expectations\s2_expectations_testmodule.pm"...
	> 3 passed, 1 failed, 0 in progress, 0 not in use.		> 12 passed, 2 failed, 0 in progress, 0 not in use.
	---------------------------------------------------------------------		---------------------------------------------------------------------
	Summary: 3 passed, 1 failed, 0 in progress, 0 not in use.		Summary: 12 passed, 2 failed, 0 in progress, 0 not in use.

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

Marku: /* Analyzing the Results */

2010-06-02T16:24:56Z

Analyzing the Results

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

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

Ivailop: /* Running Expectation Sample */

2010-05-17T22:06:45Z

Running Expectation Sample

← Older revision		Revision as of 22:06, 17 May 2010
Line 10:		Line 10:
	Here we will run the test module that is provided in this example .		Here we will run the test module that is provided in this example .

	# Run TestApp in a console window ~~as in [[Off-Target Test App \| 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 Expectation Sample */

2010-05-15T00:16:37Z

Running Expectation Sample

← Older revision		Revision as of 00:16, 15 May 2010
Line 21:		Line 21:
	</pre>		</pre>

	The command line arguments are very long, so we'll want to create a text file named ''RunSample.txt'' in the <tt>SDK\Windows</tt> directory as an option file to submit to <tt>stride</tt>.		The command line arguments are very long, so we'll want to create a text file named ''RunSample.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\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:47Z

Building Instrumented Source Under Test

← Older revision		Revision as of 00:14, 15 May 2010
Line 2:		Line 2:
	In this step, we will add pre-instrumented example source that provide an overview of STRIDE instrumentation techniques. The [[Expectations Sample]] sources are described in the linked article.		In this step, we will add pre-instrumented example source that provide an overview of STRIDE instrumentation techniques. The [[Expectations Sample]] sources 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_scrips/Expectations</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_scrips/Expectations</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]].