Studio:Samples Overview

The STRIDE Samples comprises a set of STRIDE workspaces and target application projects that provide examples of STRIDE concepts. You may use these samples as guidelines when applying STRIDE technology to your specific testing scenarios.

Samples Organization

The Samples are grouped into topics, which in turn lead you through one or more sample projects.

Typically, each sample consists of building the target application within Visual Studio, executing the sample script files from the command line, and executing the sample workspace from within STRIDE Studio. Results may be verified by viewing the generated report files in a web browser, or command line output.

If your primary interest is in target-based (xUnit-style) testing, proceed to the Test Units topic. If your primary interest is in integration or QA-style testing, proceed to the scripting topic. The SCL samples detail STRIDE Interface instrumentation. The Intercept Module sample provides examples for generating and executing an Intercept Module.

Samples Source

All samples contain Microsoft Visual Studio 2005 projects for building target applications, source code that has been instrumented as STRIDE interfaces and test units to be invoked from the Host platform, and STRIDE workspaces and scripts for running tests.

The Samples are installed under the %STRIDE_DIR%\Samples directory.

The root directory of the sample will typically contain:

• The Visual Studio 2005 project for building a Windows Off-Target App, which is a Windows console program that simulates an embedded system running remotely. (Even though the emulation is running on the same computer as STRIDE Studio, it runs in its own process, and communication is carried out over TCP/IP, just as it would be if a remote target were involved.)
• The STRIDE Studio workspace that organizes the test scripts and C/C++ header files that support the test execution. Studio manages the test order and hierarchy, provides basic infrastructure routines for setting up and tearing down before and after test execution, such as starting/stopping the simulator application and managing TraceViews.
• STRIDE Auto-generated source code (known as the IM, or Intercept Module)
• A Scripts subdirectory that contains script files that drive the testing.
• A subdirectory that contains source C/C++ files that define the test interfaces and content for the target application.

Note: The target application (console program) must be built using Microsoft Visual Studio 2005 or 2008 because those programs feature custom build steps that allow STRIDE Build Tools to be integrated into the build process.

Sample Topics

• Hello Stride

• Test Units

• Remote Interface Script

• Reporting Script

• Instrumenting Interfaces with SCL

• Generating Intercept Modules