Off-Target Environment: Difference between revisions

From STRIDE Wiki
Jump to navigation Jump to search
No edit summary
(Redirected page to STRIDE Off-Target Environment)
 
(28 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Overview ==
#REDIRECT [[STRIDE Off-Target Environment]]
[[image:STRIDE_Sandbox_Configuration.jpg|right|The sandbox configuration puts both host and target code on the host PC]]
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 "sandbox" that emulates your target system for purposes of evaluation. All of the supplied samples and test code run identically under either the sandbox environment or your actual target. In addition, Any test code you write will also run in either environment.
 
The sandbox utilizes a "target" application that is built and runs on the host system. The test runner application runs 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 rapid build/run cycles.
 
This article guides you through the steps to run and publish a set of sample tests using the sandbox evaluation environment.
 
== Evaluation Steps ==
To simplify the evaluation, we recommend using 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 sandbox evaluation are directly transferable to a production environment.
 
The recommended evaluation steps are as follows:
# Review the STRIDE Overview
# Install required packages
# Activate your STRIDE license
# Configure [[STRIDE Test Space]] for publishing results
# Build and test the basic TargetApp with built-in S2 diagnostic tests, publishing results to TestSpace
# Build and test the TargetApp with the TestIntro sample, publishing results to TestSpace
# Create your own test, run and publish
# Explore other sample tests
 
== Installing Packages ==
The following packages must be installed on the computer you will use for your sandbox environment. (Use Windows or Linux packages as appropriate).
 
See [[Package Installation]] for instructions.
 
* STRIDE SDK
* Host Tools
* Samples
* Build Tools
 
 
 
== Additional Samples ==
Additional samples are included in the STRIDE Samples package. (See [[Package_Installation#Samples|Package Installation]] for installation information.)
 
These samples explore each of the techniques outlined in the Test Intro sample in greater depth. See [[Test Unit Samples]] for details.
 
To include any of the samples into your TestApp, just copy the sources into the <tt>sample_src</tt> and rebuild. To execute the tests, use the stride test runner as before.
 
== Related Links ==
* [[:Category:SDKs|Platform SDKs]]
* [[Build Tools|STRIDE Build Tools]]
* [[Test Units|STRIDE Test Units]]
* [[SCL Pragmas|SCL Pragmas]]
* [[Test Unit Samples|Test Unit Samples]]
* [[Stride Runner|STRIDE Test Runner]]
 
== Notes ==
<references/>
[[Category:Deployment]]
[[Category:SDKs]]

Latest revision as of 18:15, 9 June 2011