View source for Running and Publishing the TestIntro Sample

== Building Instrumented Source Under Test ==
In this step, will will add a set of sample tests that provide an overview of STRIDE testing techniques. The [[Test Intro Sample]] tests are described in the linked article.

To begin, be sure that TestApp is not running, then copy the <tt>.c</tt> and <tt>.h</tt> files found in <tt>Samples/test_in_c_cpp/TestIntro</tt> to <tt>SDK/Windows/sample_src</tt> (or <tt>SDK/Posix/sample_src</tt> for Linux). 

Once the files have been copied to <tt>sample_src</tt>, simply build TestApp as described in [[Building_an_Off-Target_Test_App | here]].

== Running Test Intro Samples and Publishing Results to Test Space ==
Note: To successfully publish results you are required to create a test space called '''TestIntro'''. Refer to [[Test Space Setup]] for more information.

Here we will run all tests in the <tt>TestApp.sidb</tt> database.<ref>Note that the S2 diagnostic tests are treated separately, and are not run unless the <tt>--diagnostics</tt> option is specified to <tt>stride</tt>.</ref>

# Run the build above TestApp in a console window.
# Invoke <tt>stride</tt> in a separate console window (different from the running TestApp) -- as shown below and verify Summary results.

Here are the command line parameters that we will submit to <tt>stride</tt>

<pre>
--database ./out/TestApp.sidb 
--device TCP:localhost:8000
--upload
--testspace USER:PASS@mycompany.stridetestspace.com
--project Training
--space TestIntro
</pre>

A couple of things to note:
* You will have to replace ''USER:PASS'' with your S2-assigned TestSpace user name and password
* You will have to replace ''mycompany'' with your S2-assigned subdomain name
* The project "Training" and TestSpace "TestIntro" have been pre-created within your company STRIDE TestSpace
* If you setup [[STRIDE_Runner#Environment_Variables | environment variables]] for the '''project''' and / or '''space''' they are not required in the option file. Note: Command line options override environment variables.  

The command line is very long, so we'll want to create a text file named ''RunTestIntro.txt'' in the <tt>SDK\Windows</tt> (or <tt>SDK/Posix</tt> for Linux) directory as an option file to submit to <tt>stride</tt>.

If you haven't done so already, start <tt>TestApp</tt> running in a separate console window.

Now run stride as follows (starting from the <tt>SDK\Windows</tt> or <tt>SDK/Posix</tt> directory):

<source lang="bash">
stride -O RunTestIntro.txt --run="*"
</source>

The output should look like this:
<pre>
Loading database...
Connecting to device...
Executing...
  test unit "s2_testintro_flist"
    > 2 passed, 1 failed, 0 in progress, 0 not in use.
  test unit "s2_testintro_cclass"
    > 1 passed, 1 failed, 0 in progress, 0 not in use.
  test unit "s2_testintro_testdoubles"
    > 3 passed, 0 failed, 0 in progress, 0 not in use.
  test unit "s2_testintro_testpoints"
    > 3 passed, 0 failed, 0 in progress, 0 not in use.
  test unit "s2_testintro_parameters"
    > 2 passed, 0 failed, 0 in progress, 0 not in use.
  --------------------------------------------------------------------- 
  Summary: 11 passed, 2 failed, 0 in progress, 0 not in use.

Disconnecting from device...
Saving result file...
</pre>

=== Viewing Results in Test Space ===
First navigate to the S2-provided TestSpace with your browser. The URL has the form: <nowiki>https://companyname.stridetestspace.com</nowiki>. On the page that is presented, enter your login credentials.

At the top of the next page, click on the All Projects link to view the status of existing projects. Here you should see the Training project listed, with its contained TestSpace ''TestIntro'' shown.

Clicking the ''TestIntro'' link will present you with the ''TestIntro'' TestSpace page. From the top-line results at the bottom of the page you can drill down into the Sequence_1 results to see the test details.

=== Analyzing the Results ===
At this point, we recommend that you take some time to review the techniques used in the TestIntro sample tests and correlate the results shown in Test Space with the various STRIDE constructs in the sample source. The article [[Test Intro Sample]] describes the tests in detail.

The following articles will be helpful in your analysis:

*[[Test Units]]
*[[Test Macros]]
*[[Test Log]]
*[[Test Point]]
*[[Test Double]]


<hr/>
<references/>

[[Category:Installation]]