Studio:WorkspaceSetup.pl

The FrameworkSetup.pl script (found in the STRIDE scripts directory) provides a command line tool for creating workspaces from a Framework. This script requires perl for execution as well as the STRIDE Test Utilities.

Usage

Summary

 FrameworkSetup.pl -w MyWorkspace -d MyDir -f fxname [-g fxdir -p pkg -q pkgdir -s customsettings -c customconfig]

Parameters

-w | --workspacename = WorkspaceName

Specifies the name new workspace to be created. This workspace will be created in the directory specified by the --dirworkspace argument or in the current directory (if no workspace directory is specified).

-d | --dirworkspace = WorkspaceDirectory

Specifies the directory in which to create the new workspace. Defaults to the current directory.

-f | --framework = TargetFramework

Specifies the STRIDE Target Framework to use when creating the workspace. As of this writing, STRIDE provides two basic frameworks: Linux for a FedoraCore7 based target machine and Windows for a host-based simulation emulator. Customers may create additional frameworks and specify additional search paths for this script to use to locate the frameworks.

-g | --dirframework = FrameworkSearchDirectory

Specifies an additional directory path to search for the specified framework. If the framework is not found in the default STRIDE frameworks directory, these directories will be searched. This option can be specified multiple times to add multiple directories to the framework search path.

-p | --package = PackageName

Specifies a Test Package to add to the workspace when it is created. If no packages are specified, the workspace will be created without any tests in it. This option can be specified multiple times to add multiple packages to the new workspace

-q | --dirpackage = PackageSearchDirectory

Specifies an additional directory path to search for packages. For any package that is specified with the --package option, we first look in the packages directory in the STRIDE insatllation directory. If it is not found there, we will search in the location(s) specified by this option. This option can be specified multiple times to add multiple additional directories to the packages search path.

-s | --commonsettings = MySettings.pm

Allows users to specify a different CommonSettings file to copy into the generated workspace directory. This allows framework users to generate a workspace with a customized set of local settings.

-c | --workspaceconfig = MyConfig.pm

Allows users to specify a different WorkspaceConfig file to use when creating the workspace. This allows framework users to generate a workspace with custom config parameters.

Workspace Layout

The workspaces that are created by WorkspaceSetup will have the following files and folders (items in <brackets> indicate folders):

 <Script Files>
   <build>
     CheckEnv.pl
     PreprocessTestClasses.pl
     CompileWorkspace.pl
     CreateInterceptModule.pl
     BuildStrideAgent.pl
     <Intercept Module Overrides>
       <{Package_X}>
         (optional package specific scripts, grouped into a package folder) 
       <...> 
   <setup>
     StartStrideAgent.pl
   <test>
       <{Package_X}>
         (package specific test scripts, grouped into a package folder)
       <...> 
   <teardown>
     StopStrideAgent.pl
     TweakResults.pl
   <utility>
     (optional Framework specific utility libraries)
     <recovery>
       OnError.pl
       OnTimeout.pl
     CommonSettings.pm
     FrameworkUtilities.pm
 <Source Files>
   <Framework>
     strideIMProbe_SCL.h
     srTest.h
   <{Package_X}>
     (optional package specific source, grouped into a package folder) 
   <...>

build Folder

This folder contains the general and Framework-specific scripts necessary for building the STRIDE workspace and strideAgent device image.

Intercept Module Overrides Folder

This folder may contain one or more Test Package-specific scripts for properly configuring the Intercept Module settings for the interfaces associated with the package.

setup Folder

This folder contains the scripts necessary to transfer the strideAgent image and start the process on the device.

test Folder

This folder contains all package-specific tests, grouped in sub-folders by package name. This folder also has the "OnRunConnect" property set to true so that a target connection will be initiated when it is executed. The connection is established using your global connection settings (see STRIDE Studio reference guide for more information).

teardown Folder

This folder contains the scripts necessary to stop the strideAgent process and remove the strideAgent image from teh device.

utility Folder

This folder contains utility libraries that are associated with the workspace. Some files come from the common STRIDE Framework, while others are Framework-specific. Not all of the files in this directory tree are included in execution; as such, they are in the workspace primarily for convenience to the users.

recovery Folder

This folder contains the OnError and OnTimeout scripts – either a specific implementation provided by the Framework or the default implementation provide by the STRIDE common files.

Framework Folder

This folder contains source code required for general Framework test execution and recovery.