Installation Overview: Difference between revisions

From STRIDE Wiki
Jump to navigation Jump to search
 
(6 intermediate revisions by 3 users not shown)
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:
# '''Runner''' - host-based command-line utility for interactive and automated test execution
# '''Runtime''' - software source package that integrates with your embedded application software
# '''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).
 
= 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.


== Desktop Installation ==
== Desktop Installation ==
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.  
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'']].  


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


Please refer to the following [[Desktop_Installation | desktop installation]] instructions.
For more information, please see:


== Off-Target Environment ==
* [[Desktop_Installation | Desktop installation instructions]]
[[image:STRIDE_Desktop.jpg|right|300px| The Off-Target configuration puts both host and target code on the desktop]]
* [[STRIDE_Overview#STRIDE_Framework | STRIDE Test Framework]]


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.
=== 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:


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.
* 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 (i.e. no hardware 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.
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


Please refer to the following [[Off-Target_Environment_Setup | Off-Target Environment Setup]] instructions.
For more information, please see:
* [[STRIDE Off-Target Environment]]  


= Test Space =
=== 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.  
''STRIDE Test Space'' is a cloud-based application and does not require installation, only an account setup (i.e. user-name and password).


To begin leveraging ''Test Space'' you are required to be assigned a URL with the following form:
For more information please see:
* [[STRIDE_Test_Space | Test Space Overview]]
* [[Test_Space_Setup | Test Space Setup]]


https://yourcompanyname.stridetestspace.com
== 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.


Once this has been assigned your administrator will setup accounts.
This installation is not required for any activities performed purely in the [[STRIDE Off-Target Environment]].


Please refer to the following [[Test_Space_Setup | Test Space Setup]] instructions.
For more information, please see:
* [[Target Integration Overview]]






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

Latest revision as of 23:18, 25 September 2013

Introduction

STRIDE installs on both your desktop PC and your target embedded platform. Installation packages are provided for each of these as follows:

Desktop Installation

This is a standard installation that targets a desktop PC running either Windows, Linux or FreeBSD. It includes all pieces that comprise a STRIDE Test Framework.

Once installed, the test framework provides all the files needed

  • to run and publish tests executing on your remote target hardware
  • to build and run sample tests leveraging the off-target environment
  • to perform STRIDE training exercises

For more information, please see:

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:

  • 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 (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

For more information, please see:

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

For more information please see:

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.

This installation is not required for any activities performed purely in the STRIDE Off-Target Environment.

For more information, please see:

Retrieved from "https://www.stridewiki.com/index.php?title=Installation_Overview&oldid=13983"