Difference between revisions of "Running Diagnostics With Target"
(→Running STRIDE Diagnostics) |
|||
| Line 13: | Line 13: | ||
Specify your database and device options as required. | Specify your database and device options as required. | ||
| − | + | ==Interpreting Diagnostic Results== | |
Upon running, the host console running stride will display summary test results: | Upon running, the host console running stride will display summary test results: | ||
<pre> | <pre> | ||
| Line 44: | Line 44: | ||
All tests should pass. | All tests should pass. | ||
| − | == | + | ==Publishing Results== |
Optionally, if you have Internet connectivity and access to your company's [[STRIDE Test Space|Test Space]]<ref>You need to have an account with access to a dedicated project and space created by your Test Space administrator</ref> you could run again the diagnostics and upload the results by executing: | Optionally, if you have Internet connectivity and access to your company's [[STRIDE Test Space|Test Space]]<ref>You need to have an account with access to a dedicated project and space created by your Test Space administrator</ref> you could run again the diagnostics and upload the results by executing: | ||
Revision as of 09:47, 20 April 2010
This article describes how to run the built-in STRIDE diagnostics with your target device. It assumes that your have completed the steps described in the article Build Integration.
Contents
Running STRIDE Diagnostics
To execute the diagnostic tests, use a Windows or Linux host computer that has connectivity with the target system via your configured STRIDE transport (TCP/IP or serial). Additionally, make the generated STRIDE database (.sidb) visible to the host computer via a shared filesystem or a file copy to the host system.
If not already present, install the appropriate Host Tools package on the host computer.
Start the target app running on the target hardware, then run stride as follows:
stride --diagnostics --database=<path>/stride.sidb --device=<device_address> --run="*"
Specify your database and device options as required.
Interpreting Diagnostic Results
Upon running, the host console running stride will display summary test results:
Loading database...
Connecting to device...
runtime version: 4.1.0x
Diagnosing target application...
test unit "Link"
Loopback ............
Payload Fragmentation
Stub-Proxy Deadlock
Target Characteristics
> 4 passed, 0 failed, 0 in progress, 0 not in use.
test unit "Stat"
> 2 passed, 0 failed, 0 in progress, 0 not in use.
test unit "Time"
> 2 passed, 0 failed, 0 in progress, 0 not in use.
---------------------------------------------------------------------
Summary: 8 passed, 0 failed, 0 in progress, 0 not in use.
Disconnecting from device...
Saving result file...
Once the test run is complete, you will see the files stride.xml (result name defaults to same as database name) and, if you were connected to the Internet when you ran the tests, stride.xsl in the directory from which you ran stride.
By opening stride.xml in a web browser, the xsl is automatically applied to create html in the browser.
All tests should pass.
Publishing Results
Optionally, if you have Internet connectivity and access to your company's Test Space[1] you could run again the diagnostics and upload the results by executing:
stride --diagnostics --database=<path>/stride.sidb --device=<device_address> -u --testspace=https://<user>:<pwd>@<mycompany>.stridetestspace.com --project="Stride Deployment" --space=Diagnostics --run="*"
Notes
- ↑ You need to have an account with access to a dedicated project and space created by your Test Space administrator
