Installation Overview - Revision history

Ivailop: /* Desktop Installation */

2013-09-25T23:18:07Z

Desktop Installation

← Older revision		Revision as of 23:18, 25 September 2013
Line 4:		Line 4:

	== Desktop Installation ==		== Desktop Installation ==
	This is a standard installation that targets a desktop PC running either Windows or ~~Linux (x86)~~. It includes all pieces that comprise a [[STRIDE_Overview#STRIDE_Framework \| ''STRIDE Test Framework'']].		This is a standard installation that targets a desktop PC running either Windows, Linux or FreeBSD. It includes all pieces that comprise a [[STRIDE_Overview#STRIDE_Framework \| ''STRIDE Test Framework'']].

	Once installed, the test framework provides all the files needed		Once installed, the test framework provides all the files needed

Ivailop: /* Desktop Installation */

2011-06-09T17:44:29Z

Desktop Installation

← Older revision		Revision as of 17:44, 9 June 2011
Line 4:		Line 4:

	== Desktop Installation ==		== Desktop Installation ==
	This is a standard installation that targets a desktop PC running either Windows ~~(XP or Win7)~~ or Linux (x86). It includes all pieces that comprise a [[STRIDE_Overview#STRIDE_Framework \| ''STRIDE Test Framework'']] ~~for Windows or Linux~~.		This is a standard installation that targets a desktop PC running either Windows or Linux (x86). It includes all pieces that comprise a [[STRIDE_Overview#STRIDE_Framework \| ''STRIDE Test Framework'']].

	Once installed, the test framework provides all the files needed		Once installed, the test framework provides all the files needed

Marku at 22:24, 8 June 2011

2011-06-08T22:24:49Z

← Older revision		Revision as of 22:24, 8 June 2011
Line 22:		Line 22:
	* You can have a single PC fulfill the roles of both the host and the target platform when running tests (i.e. no hardware required)		* You can have a single PC fulfill the roles of both the host and the target platform when running tests (i.e. no hardware required)

	This is very convenient for performing STRIDE training exercises and for cases where off-target test development is feasible. Note that the Embedded Target Installation is not required when using the off-target environment		This is very convenient for performing STRIDE training exercises and for cases where off-target test development is feasible. Note that the [[Installation_Overview#Embedded Target Installation \| Embedded Target Installation]] is not required when using the off-target environment

	For more information, please see:		For more information, please see:

Marku: /* Desktop Installation */

2011-06-08T22:22:34Z

Desktop Installation

← Older revision		Revision as of 22:22, 8 June 2011
Line 7:		Line 7:

	Once installed, the test framework provides all the files needed		Once installed, the test framework provides all the files needed
	* to perform STRIDE training exercises
	* to run and publish tests executing on your remote target hardware		* to run and publish tests executing on your remote target hardware
	* to build and run sample tests leveraging the off-target environment		* to build and run sample tests leveraging the off-target environment
			* to perform STRIDE training exercises

	For more information, please see:		For more information, please see:
Line 20:		Line 20:

	* You can build test applications that run on your PC instead of on your target hardware		* You can build test applications that run on your PC instead of on your target hardware
	* You can have a single PC fulfill the roles of both the host and the target platform when running tests		* You can have a single PC fulfill the roles of both the host and the target platform when running tests (i.e. no hardware required)
	** Target hardware ~~is not~~ required ~~in this case~~

	This is very convenient for performing STRIDE training exercises and for cases where off-target test development is feasible. Note that the Embedded Target Installation is not required when using the off-target environment		This is very convenient for performing STRIDE training exercises and for cases where off-target test development is feasible. Note that the Embedded Target Installation is not required when using the off-target environment

Marku: /* Embedded Target Installation */

2011-06-08T22:14:47Z

Embedded Target Installation

← Older revision		Revision as of 22:14, 8 June 2011
Line 41:		Line 41:

	For more information, please see:		For more information, please see:
	* [[~~Target_Integration_Overview~~]]		* [[Target Integration Overview]]



	[[Category: Installation]]		[[Category: Installation]]

Timd at 21:32, 8 June 2011

2011-06-08T21:32:55Z

← Older revision		Revision as of 21:32, 8 June 2011
Line 1:		Line 1:
	= Introduction =		= Introduction =
	~~The STRIDE test system consists of two major sub-systems:~~
	* [[STRIDE_Overview#STRIDE_Framework \| Test Framework]]
	* [[STRIDE_Overview#STRIDE_Test_Space \| Test Space]]

	~~To begin using~~ STRIDE ~~there~~ are ~~a number~~ of ~~installation steps required which will be outlined in this article.~~		STRIDE installs on both your desktop PC and your target embedded platform. Installation packages are provided for each of these as follows:

	~~The~~ ''STRIDE Test Framework'' ~~has three main components:~~		== Desktop Installation ==
	~~# '''Runner''' - host-based command-line utility~~ for ~~interactive and automated test execution~~		This is a standard installation that targets a desktop PC running either Windows (XP or Win7) or Linux (x86). It includes all pieces that comprise a [[STRIDE_Overview#STRIDE_Framework \| ''STRIDE Test Framework'']] for Windows or Linux.
	~~# '''Runtime''' - software source package that integrates with your embedded application software~~
	~~# '''Build Tools''' - command-line utilities that integrate with your target software build process~~

	''STRIDE ~~Test Space'' does NOT require installation, only an account setup (i.e. user~~-~~name and password).~~		Once installed, the test framework provides all the files needed
			* to perform STRIDE training exercises
			* to run and publish tests executing on your remote target hardware
			* to build and run sample tests leveraging the off-target environment

	~~= Test Framework =~~		For more information, please see:
	~~The ''Test Framework'' enables the creation of fully automated Test Assets used to verify the internal design of your software. This section provides~~ information ~~on the required installation steps to enable executing STRIDE based tests.~~

	~~== User's~~ Desktop ==		* [[Desktop_Installation \| Desktop installation instructions]]
	~~For the user there is a desktop installation package that contains the~~ [[~~STRIDE_Runner~~ \| ~~'''Runner'''~~]] ~~and a number of associated artifacts. The package is a zip file and is targeted for either the Windows operating system or Linux.~~		* [[STRIDE_Overview#STRIDE_Framework \| STRIDE Test Framework]]

	~~When writing test cases both C/C++ and Perl can be used~~. ~~As part of the installation a STRIDE specific Perl library is installed~~. ~~If you intend~~ on ~~writing Perl base test scripts there are additional Perl module dependencies that required installation. Also~~, ~~it is very important to validate~~ the ~~Perl specific~~ installation.		=== Off Target Environment ===
			While actual verification is done using tests running on-target (i.e. on your embedded platform), the desktop installation also provides an off-target environment that makes the following possible:

	~~Please refer to~~ the ~~following [[Desktop_Installation \| desktop installation]] instructions.~~		* You can build test applications that run on your PC instead of on your target hardware
			* You can have a single PC fulfill the roles of both the host and the target platform when running tests
			** Target hardware is not required in this case

	~~== Off~~-Target ~~(optional) ==~~		This is very convenient for performing STRIDE training exercises and for cases where off-target test development is feasible. Note that the Embedded Target Installation is not required when using the off-target environment
	~~[[image:STRIDE_Desktop.jpg\|right\|300px\| The Off~~-~~Target configuration puts both host and~~ target ~~code on the desktop]]~~

	~~Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately~~, STRIDE~~'s cross-platform capabilities make it possible to run STRIDE in a '''host-only''' ''~~Off-Target ~~Configuration'' that emulates your target system.~~		For more information, please see:
			* [[STRIDE Off-Target Environment]]

	~~In order to conduct~~ '''~~training~~'~~'' or build~~ and ~~execute our [[Samples_Overview \| Samples]]~~, ~~we leverage this environment~~ (i.e. ~~single Windows or Linux (x86) computer for both the target~~ and ~~host systems~~). Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ''Off-Target Environment'' are directly transferable to a production environment. This enables the user to create their own ''sandbox'' for training and Off-Target unit testing.		=== Test Space ===
			''STRIDE Test Space'' is a cloud-based application and does not require installation, only an account setup (i.e. user-name and password).

	~~The Off-Target Environment utilizes the~~ [[~~Desktop_Installation#SDK~~\|~~Framework's "SDK"~~]] ~~that can be built and executed on the host system. When using the SDK Makefile a simulated target ''native application'' is generated, which we call a '''~~Test ~~Application (TestApp)'''.~~		For more information please see:
			* [[STRIDE_Test_Space \| Test Space Overview]]
			* [[Test_Space_Setup \| Test Space Setup]]

	~~The [[STRIDE Runner]] application executes on~~ the ~~same system~~ and ~~communicates with~~ the ~~'''TestApp''' process over a TCP/IP connection. This setup frees you from external hardware dependencies and provides for a rapid "edit/~~build~~/test" cycle~~.		== Embedded Target Installation ==
			This installation is typically performed by the team responsible for maintaining your target build environment, and is only required to be done once per target platform. The installation involves custom integration of the STRIDE build tools into your target build toolchain.

	~~Please verify that your Host system contains one of the following '''compilers''':~~		This installation is not required for any activities performed purely in the [[STRIDE Off-Target Environment]].
	* For Windows Microsoft Visual Studio 2005 or later is required~~. If you don't already have Visual Studio,~~ the ~~free~~ [~~http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express Visual C++ Express] can be used (download~~ [~~http://www.microsoft.com/express/download/#webInstall here~~]).
	* For Linux the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] ~~(included by default in almost all Linux distros) is required~~.

	For ~~instructions on building a '''TestApp''' refer to the following [[Build a TestApp \| article]].~~		For more information, please see:
			* [[Target_Integration_Overview]]
	~~== Target Integration ==~~
	The '''Runtime''' and '''Build Tools''' are installed with your software application and development tool-chain as a one-time ''integration activity'' as described [[Target_Integration_Overview \| here]]. Typical developers are not required to understand the details involved with target integration.

	~~= Test Space =~~
	~~[[STRIDE_Overview#STRIDE_TEST_SPACE \| ''Test Space'']] is used for storing and analyzing test results, thus providing on-demand availability of timely, accurate~~, ~~and meaningful test results data.~~

	~~To begin leveraging ''Test Space'' you are required to be assigned a URL with the following form~~:

	~~https://yourcompanyname.stridetestspace.com~~

	~~Once this has been assigned your administrator will setup accounts.~~

	~~Please refer to the following~~ [[~~Test_Space_Setup \| Test Space Setup~~]] ~~instructions.~~



	[[Category: Installation]]		[[Category: Installation]]

Marku at 21:23, 8 June 2011

2011-06-08T21:23:24Z

← Older revision		Revision as of 21:23, 8 June 2011
Line 10:		Line 10:
	# '''Runtime''' - software source package that integrates with your embedded application software		# '''Runtime''' - software source package that integrates with your embedded application software
	# '''Build Tools''' - command-line utilities that integrate with your target software build process		# '''Build Tools''' - command-line utilities that integrate with your target software build process

	For the typical user only the '''Runner''' requires installation. The '''Runtime''' and '''Build Tools''' are installed with your software application and development tool-chain as a one-time ''integration activity'' as described [[Target_Integration_Overview \| here]].

	''STRIDE Test Space'' does NOT require installation, only an account setup (i.e. user-name and password).		''STRIDE Test Space'' does NOT require installation, only an account setup (i.e. user-name and password).

	= Test Framework =		= Test Framework =
	The ''Test Framework'' enables the creation of fully automated Test Assets used to verify the internal design of your software. This section provides information on the required ~~desktop~~ installation steps to enable executing STRIDE based tests.		The ''Test Framework'' enables the creation of fully automated Test Assets used to verify the internal design of your software. This section provides information on the required installation steps to enable executing STRIDE based tests.

	== Desktop ~~Installation~~ ==		== User's Desktop ==
	For the user there is a desktop installation package that contains the [[STRIDE_Runner \| '''Runner''']] and a number of associated artifacts. The package is a zip file and is targeted for either the Windows operating system or Linux.		For the user there is a desktop installation package that contains the [[STRIDE_Runner \| '''Runner''']] and a number of associated artifacts. The package is a zip file and is targeted for either the Windows operating system or Linux.

Line 25:		Line 23:
	Please refer to the following [[Desktop_Installation \| desktop installation]] instructions.		Please refer to the following [[Desktop_Installation \| desktop installation]] instructions.

	== Off-Target ~~Environment~~ ==		== Off-Target (optional) ==
	[[image:STRIDE_Desktop.jpg\|right\|300px\| The Off-Target configuration puts both host and target code on the desktop]]		[[image:STRIDE_Desktop.jpg\|right\|300px\| The Off-Target configuration puts both host and target code on the desktop]]

	Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a '''host-only''' ''Off-Target Configuration'' that emulates your target system. ~~All of the supplied~~ [[Samples_Overview \| ~~samples~~]] ~~run identically under either the Off-Target~~ environment or ~~your actual~~ target. ~~In addition, any test~~ code ~~you write~~ will ~~also~~ run in ~~either~~ environment. This enables the user to create their own '''sandbox''' for training and Off-Target unit testing.		Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a '''host-only''' ''Off-Target Configuration'' that emulates your target system.

			In order to conduct '''training''' or build and execute our [[Samples_Overview \| Samples]], we leverage this environment (i.e. single Windows or Linux (x86) computer for both the target and host systems). Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ''Off-Target Environment'' are directly transferable to a production environment. This enables the user to create their own ''sandbox'' for training and Off-Target unit testing.

			The Off-Target Environment utilizes the [[Desktop_Installation#SDK\|Framework's "SDK"]] that can be built and executed on the host system. When using the SDK Makefile a simulated target ''native application'' is generated, which we call a '''Test Application (TestApp)'''.

			The [[STRIDE Runner]] application executes on the same system and communicates with the '''TestApp''' process over a TCP/IP connection. This setup frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.

	~~The Off-Target Environment utilizes~~ the [~~[Desktop_Installation#SDK\|Framework's "SDK"]~~] ~~that~~ can be ~~built and executed on the host system~~. ~~The [[STRIDE Runner~~]~~] application executes on~~ the ~~same system and communicates with the "target" process over a TCP~~/~~IP connection~~. ~~This set up frees you from external hardware dependencies and provides for a rapid "edit~~/~~build~~/~~test" cycle~~.		Please verify that your Host system contains one of the following '''compilers''':
			* For Windows Microsoft Visual Studio 2005 or later is required. If you don't already have Visual Studio, the free [http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express Visual C++ Express] can be used (download [http://www.microsoft.com/express/download/#webInstall here]).
			* For Linux the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] (included by default in almost all Linux distros) is required.

	~~In order to conduct training or build and execute our [[Samples_Overview \| Samples]], we leverage~~ a single Windows or Linux (x86) computer for both the target and host systems. Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ''~~Off-Target Environment~~'' ~~are directly transferable~~ to a ~~production environment~~.		For instructions on building a '''TestApp''' refer to the following [[Build a TestApp \| article]].

	~~Please refer to the following~~ [[~~Off-Target_Environment_Setup~~ \| ~~Off-Target Environment Setup~~]] ~~instructions~~.		== Target Integration ==
			The '''Runtime''' and '''Build Tools''' are installed with your software application and development tool-chain as a one-time ''integration activity'' as described [[Target_Integration_Overview \| here]]. Typical developers are not required to understand the details involved with target integration.

	= Test Space =		= Test Space =

Timd: /* Introduction */

2011-06-07T17:55:37Z

Introduction

← Older revision		Revision as of 17:55, 7 June 2011
Line 11:		Line 11:
	# '''Build Tools''' - command-line utilities that integrate with your target software build process		# '''Build Tools''' - command-line utilities that integrate with your target software build process

	For the typical user only the '''Runner''' requires installation. The '''Runtime''' and '''Build Tools''' are installed with ''your'' software application and development tool-chain as a ~~onetime~~ ''integration activity'' as described [[Target_Integration_Overview \| here]].		For the typical user only the '''Runner''' requires installation. The '''Runtime''' and '''Build Tools''' are installed with your software application and development tool-chain as a one-time ''integration activity'' as described [[Target_Integration_Overview \| here]].

	''STRIDE Test Space'' does NOT require installation, only an account setup (i.e. user-name and password).		''STRIDE Test Space'' does NOT require installation, only an account setup (i.e. user-name and password).

Marku: /* Introduction */

2011-06-07T17:24:11Z

Introduction

← Older revision		Revision as of 17:24, 7 June 2011
Line 2:		Line 2:
	The STRIDE test system consists of two major sub-systems:		The STRIDE test system consists of two major sub-systems:
	* [[STRIDE_Overview#STRIDE_Framework \| Test Framework]]		* [[STRIDE_Overview#STRIDE_Framework \| Test Framework]]
	* [[STRIDE_Overview#STRIDE_Test_Space \| ~~Hosted Web Application~~]]		* [[STRIDE_Overview#STRIDE_Test_Space \| Test Space]]

	To begin using STRIDE there are a number of installation steps required which will be outlined in this article.		To begin using STRIDE there are a number of installation steps required which will be outlined in this article.

Marku: /* Off-Target Environment */

2011-06-06T21:40:06Z

Off-Target Environment

← Older revision		Revision as of 21:40, 6 June 2011
Line 32:		Line 32:
	The Off-Target Environment utilizes the [[Desktop_Installation#SDK\|Framework's "SDK"]] that can be built and executed on the host system. The [[STRIDE Runner]] application executes on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.		The Off-Target Environment utilizes the [[Desktop_Installation#SDK\|Framework's "SDK"]] that can be built and executed on the host system. The [[STRIDE Runner]] application executes on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.

	In order to conduct training or build and execute ~~the samples~~, we leverage a single Windows or Linux (x86) computer for both the target and host systems. Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ''Off-Target Environment'' are directly transferable to a production environment.		In order to conduct training or build and execute our [[Samples_Overview \| Samples]], we leverage a single Windows or Linux (x86) computer for both the target and host systems. Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ''Off-Target Environment'' are directly transferable to a production environment.

	Please refer to the following [[Off-Target_Environment_Setup \| Off-Target Environment Setup]] instructions.		Please refer to the following [[Off-Target_Environment_Setup \| Off-Target Environment Setup]] instructions.