Test Space Setup: Difference between revisions

From STRIDE Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Accessing Your Test Space Instance==
==Accessing Your Test Space Instance==
To begin, we will verify that you can access your company's STRIDE Test Space. Navigate to the S2-provided Test Space with your browser. The URL has the form:
To begin, we will verify that you can access your company's [[STRIDE_Test_Space | STRIDE Test Space]]. Navigate to the S2-provided Test Space with your browser. The URL has the form:
   
   
  https://''companyname''.stridetestspace.com.
  https://''company''.stridetestspace.com  


On the page that is presented, enter your Username and Password, then click the ''Log in'' button.
On the page that is presented, enter your Username and Password, then click the ''Log in'' button.


==Create Project and Space for Samples==
==Create Projects and Spaces ==
Now that you are logged-in to Test Space, you should create a '''Project''' and one or more '''Test Spaces''' to publish results from the tests you execute. Please review [[Creating Test Spaces|this article]] on creating new test spaces. For evaluations, we often recommend that you create a project called '''Sandbox''' and a number of different test spaces (i.e. Samples, Diagnostics, etc.). Note: some instructions assume certain test spaces already exist. If they do not yet exist you should create them at that time.  
Now that you are logged-in to Test Space, you should create a '''Project''' and one or more '''Test Spaces''' to publish results from the tests you execute. Please review [[Creating Test Spaces|this article]] on creating new test spaces. For evaluations, we often recommend that you create a project called '''Sandbox''' and a number of different test spaces (i.e. Samples, etc.).  


==Publishing Results with the Runner==
==Publishing Results with the Runner==
You can automatically publish test results with the [[STRIDE Runner | Runner]] by passing in command [[STRIDE Runner#Options | options]]. An example might be something like the following:
You can automatically publish test results with the [[STRIDE Runner | Runner]] by passing in Test Space [[STRIDE Runner#Options | command line options]] along with your other runner options. An example might be something like the following:
<pre>
stride --testspace https://USER:PASS@company.stridetestspace.com --project Sandbox --space Samples --upload
</pre>


The Runner also supports [[STRIDE_Runner#Environment Variables | environment variables]] that can be leverages for commonly used Test Space options.
  stride '''--upload''' '''--testspace''' <nowiki>USER:PASS@company.stridetestspace.com</nowiki> '''--project''' Sandbox '''--space''' Samples ''[other options]''
 
 
The Runner also supports [[STRIDE_Runner#Environment Variables | environment variables]] that can be leveraged for commonly used Test Space options.


[[Category:Installation]]
[[Category:Installation]]

Latest revision as of 20:51, 20 February 2013

Accessing Your Test Space Instance

To begin, we will verify that you can access your company's STRIDE Test Space. Navigate to the S2-provided Test Space with your browser. The URL has the form:

https://company.stridetestspace.com 

On the page that is presented, enter your Username and Password, then click the Log in button.

Create Projects and Spaces

Now that you are logged-in to Test Space, you should create a Project and one or more Test Spaces to publish results from the tests you execute. Please review this article on creating new test spaces. For evaluations, we often recommend that you create a project called Sandbox and a number of different test spaces (i.e. Samples, etc.).

Publishing Results with the Runner

You can automatically publish test results with the Runner by passing in Test Space command line options along with your other runner options. An example might be something like the following:

 stride --upload --testspace USER:PASS@company.stridetestspace.com --project Sandbox --space Samples [other options]


The Runner also supports environment variables that can be leveraged for commonly used Test Space options.