Test Integration - Revision history

Ivailop: /* Running the TestIntro Tests */

2013-09-25T23:22:56Z

Running the TestIntro Tests

← Older revision		Revision as of 23:22, 25 September 2013
Line 13:		Line 13:

	== Running the TestIntro Tests ==		== Running the TestIntro Tests ==
	To execute the TestIntro tests, use a Windows or ~~Linux~~ host computer that has connectivity with the target system via your configured STRIDE transport (TCP/IP or serial). Additionally, make the generated STRIDE database (.sidb) visible to the host computer via a shared filesystem or a file copy to the host system.		To execute the TestIntro tests, use a Windows, Linux or FreeBSD host computer that has connectivity with the target system via your configured STRIDE transport (TCP/IP or serial). Additionally, make the generated STRIDE database (.sidb) visible to the host computer via a shared filesystem or a file copy to the host system.

	If not already present, install the appropriate [[Desktop_Installation \| desktop Framework package]] on the host computer.		If not already present, install the appropriate [[Desktop_Installation \| desktop Framework package]] on the host computer.

Ivailop: /* Uploading and Viewing Results in Test Space */

2013-02-20T20:48:19Z

Uploading and Viewing Results in Test Space

← Older revision		Revision as of 20:48, 20 February 2013
Line 46:		Line 46:

	<source lang="bash">		<source lang="bash">
	stride --database=<path>/stride.sidb --device=<device_address> -u --testspace=~~https://~~<user>:<pwd>@<mycompany>.stridetestspace.com --project="Stride Deployment" --space=TestIntro --run="*"		stride --database=<path>/stride.sidb --device=<device_address> -u --testspace=<user>:<pwd>@<mycompany>.stridetestspace.com --project="Stride Deployment" --space=TestIntro --run="*"
	</source>		</source>

Marku: /* Notes */

2010-06-02T17:34:32Z

Notes

← Older revision		Revision as of 17:34, 2 June 2010
Line 59:		Line 59:
	<references/>		<references/>

	[[Category:~~Framework Integration~~]]		[[Category:Installation]]

Marku: /* Running the TestIntro Tests */

2010-06-02T17:16:54Z

Running the TestIntro Tests

← Older revision		Revision as of 17:16, 2 June 2010
Line 15:		Line 15:
	To execute the TestIntro tests, use a Windows or Linux host computer that has connectivity with the target system via your configured STRIDE transport (TCP/IP or serial). Additionally, make the generated STRIDE database (.sidb) visible to the host computer via a shared filesystem or a file copy to the host system.		To execute the TestIntro tests, use a Windows or Linux host computer that has connectivity with the target system via your configured STRIDE transport (TCP/IP or serial). Additionally, make the generated STRIDE database (.sidb) visible to the host computer via a shared filesystem or a file copy to the host system.

	If not already present, install the appropriate [[Desktop_Installation \| ~~STRIDE~~ Framework]] ~~package~~ on the host computer.		If not already present, install the appropriate [[Desktop_Installation \| desktop Framework package]] on the host computer.

	To run the tests, ensure that your target system is running, then enter the following in a host console:		To run the tests, ensure that your target system is running, then enter the following in a host console:

Ivailop: /* Running the TestIntro Tests */

2010-05-19T23:02:30Z

Running the TestIntro Tests

← Older revision		Revision as of 23:02, 19 May 2010
Line 26:		Line 26:
	Loading database...		Loading database...
	Connecting to device...		Connecting to device...
	~~runtime version: 4.1.xx~~
	Executing test units...		Executing test units...
	s2_testintro_cclass		s2_testintro_cclass

Ivailop: /* Running the TestIntro Tests */

2010-05-17T22:54:43Z

Running the TestIntro Tests

← Older revision		Revision as of 22:54, 17 May 2010
Line 15:		Line 15:
	To execute the TestIntro tests, use a Windows or Linux host computer that has connectivity with the target system via your configured STRIDE transport (TCP/IP or serial). Additionally, make the generated STRIDE database (.sidb) visible to the host computer via a shared filesystem or a file copy to the host system.		To execute the TestIntro tests, use a Windows or Linux host computer that has connectivity with the target system via your configured STRIDE transport (TCP/IP or serial). Additionally, make the generated STRIDE database (.sidb) visible to the host computer via a shared filesystem or a file copy to the host system.

	If not already present, install the appropriate [[~~Package_Installation#Host_Tools~~ \| ~~Host Tools~~]] package on the host computer.		If not already present, install the appropriate [[Desktop_Installation \| STRIDE Framework]] package on the host computer.

	To run the tests, ensure that your target system is running, then enter the following in a host console:		To run the tests, ensure that your target system is running, then enter the following in a host console:

Ivailop at 22:53, 17 May 2010

2010-05-17T22:53:16Z

← Older revision		Revision as of 22:53, 17 May 2010
Line 59:		Line 59:
	== Notes ==		== Notes ==
	<references/>		<references/>
	[[Category:~~Remove~~]]
			[[Category:Framework Integration]]

Ivailop: moved Test Execution to Test Integration

2010-05-17T22:51:32Z

moved Test Execution to Test Integration

← Older revision	Revision as of 22:51, 17 May 2010
(No difference)

Ivailop: /* Running the TestIntro Tests */

2010-05-17T22:50:36Z

Running the TestIntro Tests

← Older revision		Revision as of 22:50, 17 May 2010
Line 19:		Line 19:
	To run the tests, ensure that your target system is running, then enter the following in a host console:		To run the tests, ensure that your target system is running, then enter the following in a host console:
	<source lang="bash">		<source lang="bash">
	stride --database=<path>/stride.sidb --device=<device_address> --run=*		stride --database=<path>/stride.sidb --device=<device_address> --run="*"
	</source>		</source>

Line 47:		Line 47:

	<source lang="bash">		<source lang="bash">
	stride --database=<path>/stride.sidb --device=<device_address> -u --testspace=https://<user>:<pwd>@<mycompany>.stridetestspace.com --project="Stride Deployment" --space=TestIntro --run=*		stride --database=<path>/stride.sidb --device=<device_address> -u --testspace=https://<user>:<pwd>@<mycompany>.stridetestspace.com --project="Stride Deployment" --space=TestIntro --run="*"
	</source>		</source>

Ivailop at 22:49, 17 May 2010

2010-05-17T22:49:07Z

← Older revision		Revision as of 22:49, 17 May 2010
Line 1:		Line 1:
	In this article, we discuss adding tests to your target build and running these tests.		In this article, we discuss adding tests to your target build and running these tests.

	The starting point of this article assumes that you have completed the steps described in the article [[~~Test~~ Integration]].		The starting point of this article assumes that you have completed the steps described in the article [[Build Integration]].

	== Adding the TestIntro Tests to the Target Build ==		== Adding the TestIntro Tests to the Target Build ==
	Here we will add the [[Test Intro Sample\|TestIntro sample tests]] to the target build.<ref>The TestIntro sample is distributed in the [[~~Package_Installation~~#Samples\|Samples package]].</ref> We will use the same technique used earlier in the [[~~Test_Integration~~#Building_the_Target_with_STRIDE_Diagnostics\|~~Test~~ Integration]] to incorporate these tests.		Here we will add the [[Test Intro Sample\|TestIntro sample tests]] to the target build.<ref>The TestIntro sample is distributed in the [[Distribution Files#Samples\|Samples package]].</ref> We will use the same technique used earlier in the [[Build_Integration#Building_the_Target_with_STRIDE_Diagnostics\|Build Integration]] to incorporate these tests.

	The [[Test Unit Pragmas\|SCL pragmas]] that declare the TestIntro test units are in the file <tt>s2_testintro_test.h</tt>, so this file needs to be supplied as input to the STRIDE build tools. If you are using the Makefile technique described in [[~~Test_Integration~~#Build_Tool_Inputs\|~~Test~~ Integration]], you simply need to add <tt>[path]Samples/TestIntro/s2_testintro_test.h</tt> to the <tt>SCL_SRCS_H</tt> variable so that it will be picked up as input to <tt>s2scompile</tt>.		The [[Test Unit Pragmas\|SCL pragmas]] that declare the TestIntro test units are in the file <tt>s2_testintro_test.h</tt>, so this file needs to be supplied as input to the STRIDE build tools. If you are using the Makefile technique described in [[Build_Integration#Build_Tool_Inputs\|Build Integration]], you simply need to add <tt>[path]Samples/TestIntro/s2_testintro_test.h</tt> to the <tt>SCL_SRCS_H</tt> variable so that it will be picked up as input to <tt>s2scompile</tt>.

	In addition, you need to include the TestIntro source files in the target compile/link.		In addition, you need to include the TestIntro source files in the target compile/link.