Test Units Overview: Difference between revisions

From STRIDE Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 10: Line 10:


===How to get started===
===How to get started===
The following is an outline of the required steps to get started with writing C++ test classes.
# Create a new Studio workspace (or open an existing one).
# Set the workspace to cpp mode (for compilation).
# Add {STRIDE_DIR}\inc\srtest.h to the Source Files folder of your workspace.
# Add {STRIDE_DIR}\scripts\TestClasses\TestClass_Preprocess.pl (or .js) to your Script Files folder.  If you will be adding a script to compile the workspace (see next step), this script must always '''preceed''' the compilation step.
# Add a script to compile the workspace.  In it's simplest form, this script can simple be something like:
  #perl syntax
  Win32::OLE->Option(Warn => 3);
  $main::studio->Workspace->Compile();
or
  /* jscript syntax */
  studio.Workspace.Compile();
#

Revision as of 00:35, 20 June 2007

Introduction

STRIDE enables testing of C++ code through the use of xUnit style test classes. Test classes can be written by engineers, captured using an SCL pragma, and executed from the host. STRIDE facilitates the execution of some or all of the test classes by automatically creating entry points for the execution of test classes on the target.

Using CPP Test Classes

Prerequisites

The CPP Test class support only works in the 2.0.0802 version of STRIDE or later. The host PC must also have a recent distribution of ActiveState perl installed.

How to get started

The following is an outline of the required steps to get started with writing C++ test classes.

  1. Create a new Studio workspace (or open an existing one).
  2. Set the workspace to cpp mode (for compilation).
  3. Add {STRIDE_DIR}\inc\srtest.h to the Source Files folder of your workspace.
  4. Add {STRIDE_DIR}\scripts\TestClasses\TestClass_Preprocess.pl (or .js) to your Script Files folder. If you will be adding a script to compile the workspace (see next step), this script must always preceed the compilation step.
  5. Add a script to compile the workspace. In it's simplest form, this script can simple be something like:
 #perl syntax
 Win32::OLE->Option(Warn => 3);
 $main::studio->Workspace->Compile();

or

 /* jscript syntax */
 studio.Workspace.Compile();