Running Diagnostics With Target: Difference between revisions
| (9 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
==Running STRIDE Diagnostics== | ==Running STRIDE Diagnostics== | ||
To execute the diagnostic tests, use a Windows or | To execute the diagnostic tests, use a desktop (Windows, Linux or FreeBSD) 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 [[ | If not already present, install the appropriate [[Desktop_Installation|desktop Framework package]] on the host computer. | ||
Start the target app running on the target hardware, then run [[Stride Runner|stride]] as follows: | Start the target app running on the target hardware, then run [[Stride Runner|stride]] as follows: | ||
<source lang="bash"> | <source lang="bash"> | ||
stride --diagnostics --database=<path>/stride.sidb --device=<device_address> --run="*" | stride --diagnostics --database=<path>/stride.sidb --device=<device_address> --run="*" --output=diagnostics | ||
</source> | </source> | ||
| Line 18: | Line 18: | ||
Loading database... | Loading database... | ||
Connecting to device... | Connecting to device... | ||
runtime version: | runtime version: 5.x.yy | ||
Executing diagnostics... | |||
test unit "Link" | test unit "Link" | ||
Loopback ............ | Loopback ............ | ||
| Line 33: | Line 31: | ||
> 2 passed, 0 failed, 0 in progress, 0 not in use. | > 2 passed, 0 failed, 0 in progress, 0 not in use. | ||
--------------------------------------------------------------------- | --------------------------------------------------------------------- | ||
Summary: | Summary: 8 passed, 0 failed, 0 in progress, 0 not in use. | ||
Disconnecting from device... | Disconnecting from device... | ||
| Line 40: | Line 38: | ||
</pre> | </pre> | ||
Once the test run is complete, you will see the files | Once the test run is complete, you will see the files ''diagnostics.xml'' (result name defaults to same as database name if the '--output" option is not used) and, if you were connected to the Internet when you ran the tests, ''diagnostics.xsl'' in the directory from which you ran stride. | ||
By opening | By opening ''diagnostics.xml'' in a web browser, the xsl is automatically applied to create html in the browser. | ||
All tests should pass. | All tests should pass. | ||
| Line 53: | Line 51: | ||
--run "*" | --run "*" | ||
--database <path>/stride.sidb --device=<device_address> | --database <path>/stride.sidb --device=<device_address> | ||
--testspace | --testspace <user>:<pwd>@<mycompany>.stridetestspace.com | ||
--project Sandbox | --project Sandbox | ||
--space | --space Diagnostics | ||
--upload | --upload | ||
</source> | </source> | ||
| Line 62: | Line 60: | ||
<references/> | <references/> | ||
[[Category: | [[Category:Installation]] | ||
Latest revision as of 20:16, 5 June 2014
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.
Running STRIDE Diagnostics
To execute the diagnostic tests, use a desktop (Windows, Linux or FreeBSD) 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 desktop Framework 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="*" --output=diagnostics
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: 5.x.yy
Executing diagnostics...
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 diagnostics.xml (result name defaults to same as database name if the '--output" option is not used) and, if you were connected to the Internet when you ran the tests, diagnostics.xsl in the directory from which you ran stride.
By opening diagnostics.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 submitting the following command line parameters to stride:
--diagnostics
--run "*"
--database <path>/stride.sidb --device=<device_address>
--testspace <user>:<pwd>@<mycompany>.stridetestspace.com
--project Sandbox
--space Diagnostics
--upload
Notes
- ↑ You need to have an account with access to a dedicated project and space created by your Test Space administrator