Running Diagnostics With Target - Revision history

Ivailop: /* Interpreting Diagnostic Results */

2014-06-05T20:16:45Z

Interpreting Diagnostic Results

← Older revision		Revision as of 20:16, 5 June 2014
Line 18:		Line 18:
	Loading database...		Loading database...
	Connecting to device...		Connecting to device...
	runtime version: 4.3.xx		runtime version: 5.x.yy
	Executing diagnostics...		Executing diagnostics...
	test unit "Link"		test unit "Link"

Ivailop: /* Running STRIDE Diagnostics */

2013-09-25T23:12:30Z

Running STRIDE Diagnostics

← Older revision		Revision as of 23:12, 25 September 2013
Line 2:		Line 2:

	==Running STRIDE Diagnostics==		==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.		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_Installation\|desktop Framework package]] on the host computer.		If not already present, install the appropriate [[Desktop_Installation\|desktop Framework package]] on the host computer.

Ivailop: /* Publishing Results */

2013-02-20T20:53:09Z

Publishing Results

← Older revision		Revision as of 20:53, 20 February 2013
Line 51:		Line 51:
	--run "*"		--run "*"
	--database <path>/stride.sidb --device=<device_address>		--database <path>/stride.sidb --device=<device_address>
	--testspace ~~https://~~<user>:<pwd>@<mycompany>.stridetestspace.com		--testspace <user>:<pwd>@<mycompany>.stridetestspace.com
	--project Sandbox		--project Sandbox
	--space Diagnostics		--space Diagnostics

Ivailop: /* Interpreting Diagnostic Results */

2011-06-09T17:24:27Z

Interpreting Diagnostic Results

← Older revision		Revision as of 17:24, 9 June 2011
Line 18:		Line 18:
	Loading database...		Loading database...
	Connecting to device...		Connecting to device...
	runtime version: 4.2.0x		runtime version: 4.3.xx
	Executing diagnostics...		Executing diagnostics...
	test unit "Link"		test unit "Link"

Ivailop: /* Running STRIDE Diagnostics */

2010-11-01T17:34:22Z

Running STRIDE Diagnostics

← Older revision		Revision as of 17:34, 1 November 2010
Line 8:		Line 8:
	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="*" --output diagnostics		stride --diagnostics --database=<path>/stride.sidb --device=<device_address> --run="*" --output=diagnostics
	</source>		</source>

Marku: /* Interpreting Diagnostic Results */

2010-10-11T15:47:13Z

Interpreting Diagnostic Results

← Older revision		Revision as of 15:47, 11 October 2010
Line 19:		Line 19:
	Connecting to device...		Connecting to device...
	runtime version: 4.2.0x		runtime version: 4.2.0x
	~~Diagnosing target application..~~.		Executing diagnostics...
	~~script "diagnostics~~.~~pl"~~
	~~> 3 passed, 0 failed, 0 in progress, 0 not in use~~.
	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: 11 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...		Disconnecting from device...
Line 40:		Line 38:
	</pre>		</pre>

	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.		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 ~~stride~~.xml in a web browser, the xsl is automatically applied to create html in the browser.		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.

Marku: /* Running STRIDE Diagnostics */

2010-10-11T15:41:27Z

Running STRIDE Diagnostics

← Older revision		Revision as of 15:41, 11 October 2010
Line 8:		Line 8:
	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>

Marku: /* Notes */

2010-06-02T17:34:11Z

Notes

← Older revision		Revision as of 17:34, 2 June 2010
Line 62:		Line 62:
	<references/>		<references/>

	[[Category:~~Framework Integration~~]]		[[Category:Installation]]

Marku: /* Running STRIDE Diagnostics */

2010-06-02T17:14:51Z

Running STRIDE Diagnostics

← Older revision		Revision as of 17:14, 2 June 2010
Line 4:		Line 4:
	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.		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 [[~~Framework_Installation~~\|~~STRIDE~~ Framework]] ~~package~~ on the host computer.		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:

Marku: /* Publishing Results */

2010-05-20T22:59:24Z

Publishing Results

← Older revision		Revision as of 22:59, 20 May 2010
Line 55:		Line 55:
	--testspace https://<user>:<pwd>@<mycompany>.stridetestspace.com		--testspace https://<user>:<pwd>@<mycompany>.stridetestspace.com
	--project Sandbox		--project Sandbox
	--space ~~MySpaceName~~		--space Diagnostics
	--upload		--upload
	</source>		</source>