Studio:Workspace Setup - Revision history

Timd: Text replace - 'Category:Project Organization' to 'Category:Studio:Project Organization'

2009-08-20T22:34:06Z

Text replace - 'Category:Project Organization' to 'Category:Studio:Project Organization'

← Older revision		Revision as of 22:34, 20 August 2009
Line 17:		Line 17:


	[[Category:Project Organization]]		[[Category:Studio:Project Organization]]

Timd: Workspace Setup moved to Studio:Workspace Setup

2009-08-18T21:45:39Z

Workspace Setup moved to Studio:Workspace Setup

← Older revision	Revision as of 21:45, 18 August 2009
(No difference)

Ivailop at 16:57, 5 June 2009

2009-06-05T16:57:04Z

← Older revision		Revision as of 16:57, 5 June 2009
Line 18:		Line 18:

	[[Category:Project Organization]]		[[Category:Project Organization]]
	~~[[Category:Practice]]~~

Timd at 01:42, 10 December 2008

2008-12-10T01:42:45Z

← Older revision		Revision as of 01:42, 10 December 2008
Line 4:		Line 4:


	The auto-generated workspace will contain the following folders. For more [[WorkspaceSetup.pl \| details]] refer to WorkspaceSetup.pl.		The auto-generated workspace will contain the following logical folders. For more [[WorkspaceSetup.pl \| details]] refer to WorkspaceSetup.pl.

	<~~Scripts~~ Files>		<Script Files>
	[[#setup\|setup]] ''-- relevant setup fixtures''		[[#setup\|setup]] ''-- relevant setup fixtures''
	[[#test\|test]] ''-- test assets''		[[#test\|test]] ''-- test assets''
Line 14:		Line 14:
	Test Suites and Test Cases shall be placed under the '''test''' folder.		Test Suites and Test Cases shall be placed under the '''test''' folder.

	~~The following is an example of setting up publishing via the workspace:~~

	~~// Demo portal = http://demoportal.s2technologies.com/~~

	~~var portal = studio.Workspace.Portal;~~

	~~// portal.EnableUpload = false; // default to off~~
	~~portal.Server = "demoportal.s2technologies.com/testresults/";~~
	~~portal.Path = "/DEMO";~~
	~~portal.TimestampPath = true;~~
	~~portal.SpaceName = "DEMO";~~
	~~portal.UserName = "marku";~~
	~~portal.Password = "seaside";~~


	[[Category:Project Organization]]		[[Category:Project Organization]]
	[[Category:Practice]]		[[Category:Practice]]

Marku at 15:52, 1 December 2008

2008-12-01T15:52:08Z

@@ Line 13: / Line 13: @@
 Test Suites and Test Cases shall be placed under the '''test''' folder.
 [[Category:Project Organization]]
 [[Category:Practice]]

Marku at 15:45, 30 November 2008

2008-11-30T15:45:35Z

← Older revision		Revision as of 15:45, 30 November 2008
Line 1:		Line 1:
	This article outlines the recommended organization for a Test Workspace. The [[WorkspaceSetup.pl]] utility script should be used to create the workspace. The command line script will automatically create a workspace with the passed in ''name'':		This article outlines the recommended organization for a Test Workspace. The [[WorkspaceSetup.pl]] utility script should be used to create the workspace. The ''command line'' script will automatically create a workspace with the passed in ''name'':

	WorkspaceSetup.pl -w ''name''		WorkspaceSetup.pl -w ''name''


	The auto-generated workspace will contain the following folders. For more [[WorkspaceSetup.pl \| details]] refer to WorkspaceSetup.pl:		The auto-generated workspace will contain the following folders. For more [[WorkspaceSetup.pl \| details]] refer to WorkspaceSetup.pl.

	<Scripts Files>		<Scripts Files>

Marku at 15:43, 30 November 2008

2008-11-30T15:43:10Z

← Older revision		Revision as of 15:43, 30 November 2008
Line 1:		Line 1:
	This article outlines the ~~recommend standards~~ for a Test Workspace ~~organization~~. The [[WorkspaceSetup.pl]] utility script automatically ~~sets up~~ a workspace:		This article outlines the recommended organization for a Test Workspace. The [[WorkspaceSetup.pl]] utility script should be used to create the workspace. The command line script will automatically create a workspace with the passed in ''name'':

	WorkspaceSetup.pl -w ''name''		WorkspaceSetup.pl -w ''name''


	The workspace ~~created~~ will ~~be automatically setup with~~ the following folders:		The auto-generated workspace will contain the following folders. For more [[WorkspaceSetup.pl \| details]] refer to WorkspaceSetup.pl:

	<Scripts Files>		<Scripts Files>
	[[#setup\|setup]] ''-- relevant setup fixtures''		[[#setup\|setup]] ''-- relevant setup fixtures''
	[[#test\|test]] ''-- test assets''		[[#test\|test]] ''-- test assets''
	~~[[#yourSuite1\|your suite1]]~~
	~~[[#yourSuite2\|your suite2]]~~
	[[#teardown\|teardown]] ''-- relevant teardown fixtures''		[[#teardown\|teardown]] ''-- relevant teardown fixtures''
	[[#utility\|utility]] ''-- utilities and libraries''		[[#utility\|utility]] ''-- utilities and libraries''

			Test Suites and Test Cases shall be placed under the '''test''' folder.

	[[Category:Project Organization]]		[[Category:Project Organization]]
	[[Category:Practice]]		[[Category:Practice]]

Marku at 15:33, 30 November 2008

2008-11-30T15:33:05Z

@@ Line 4: / Line 4: @@
-=Folder Layout=
+The workspace created will be automatically setup with the following folders:
   <Scripts Files>
@@ Line 13: / Line 13: @@
     [[#teardown|teardown]] ''-- relevant teardown fixtures''
     [[#utility|utility]] ''-- utilities and libraries''
 [[Category:Project Organization]]
 [[Category:Practice]]

Marku at 15:31, 30 November 2008

2008-11-30T15:31:33Z

← Older revision		Revision as of 15:31, 30 November 2008
Line 1:		Line 1:
	This article outlines standards for ~~placement of STRIDE solution files and folders~~.		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=		=Folder Layout=

	<~~Solution Root~~>		<Scripts Files>
	[[#~~Documents~~\|~~Documents~~]] ''-- relevant ~~documents~~''		[[#setup\|setup]] ''-- relevant setup fixtures''
	[[#~~Customer~~\|~~Customer~~]]		[[#test\|test]] ''-- test assets''
	[[#S2\|S2]]		[[#yourSuite1\|your suite1]]
	[[#~~Source~~\|~~Source~~]] ~~''-- customer target source''~~		[[#yourSuite2\|your suite2]]
	[[#~~Target~~\|~~Target~~]] ''-- ~~instrumented target binary and STRIDE databse~~''		[[#teardown\|teardown]] ''-- relevant teardown fixtures''
	[[#~~TestAssets~~\|~~TestAssets~~]] ''-- ~~test assets~~''		[[#utility\|utility]] ''-- utilities and libraries''
	~~[[#TestWorkspace\|TestWorkspace]]~~
	~~[[#TestUnits\|TestUnits]]~~
	~~[[#TestScripts\|TestScripts]]~~
	~~[[#SCL\|SCL]]~~
	~~[[#UtilityScripts\|UtilityScripts]]~~

	=Folder Contents=		=Folder Contents=

Marku: New page: This article outlines standards for placement of STRIDE solution files and folders. =Folder Layout= Documents ''-- relevant documents'' [[#Custo...

2008-11-30T15:16:19Z

New page: This article outlines standards for placement of STRIDE solution files and folders. =Folder Layout= <Solution Root> Documents ''-- relevant documents'' [[#Custo...

New page

This article outlines standards for placement of STRIDE solution files and folders.

=Folder Layout=

<Solution Root>
[[#Documents|Documents]] ''-- relevant documents''
[[#Customer|Customer]]
[[#S2|S2]]
[[#Source|Source]] ''-- customer target source''
[[#Target|Target]] ''-- instrumented target binary and STRIDE databse''
[[#TestAssets|TestAssets]] ''-- test assets''
[[#TestWorkspace|TestWorkspace]]
[[#TestUnits|TestUnits]]
[[#TestScripts|TestScripts]]
[[#SCL|SCL]]
[[#UtilityScripts|UtilityScripts]]

=Folder Contents=

== Documents ==
;Customer
:<ul><li>customer-supplied documents that are not included or linked on the project portal wiki</li></ul>
;S2
:<ul><li>S2-generated documents that are not included or linked in the project portal wiki</li><li>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.)</li></ul>

==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

[[Category:Project Organization]]
[[Category:Practice]]