Studio:Workspace Setup

This article outlines the recommend standards for a Test Workspace organization. The WorkspaceSetup.pl utility script automatically sets up a workspace:

 WorkspaceSetup.pl -w name

Folder Layout

<Scripts Files>
  setup -- relevant setup fixtures
  test -- test assets
     your suite1
     your suite2
  teardown -- relevant teardown fixtures
  utility -- utilities and libraries

Folder Contents

Documents

Customer

• customer-supplied documents that are not included or linked on the project portal wiki

S2

• S2-generated documents that are not included or linked in the project portal wiki
• S2-generated documents that have been uploaded to the project portal wiki and embedded in a wiki page. (e.g. Visio drawings, screen shots, etc.)

Source

Customer source code required to build the target is stored here.

Subfolder organization should follow that used by the customer.

Target

Local target app built from Visual Studio (customer source + IM) Workspace database (.sidb) built from STRIDE Studio

TestAssets

Note: If there are multiple components, each requiring a unique set of TestAssets, than a sub-folder should be created representing the name of the component under test.

The following hierarchy is recommended:

TestWorkspace

STRIDE workspace (.ssw) file goes here

TestUnits

If the workspace has test units defined, source files go here

TestScripts

Test scripts

SCL

Header files comprising this project's SCL go here as well as any s2instrument option files

UtilityScripts

Helper scripts and modules go here