Frequently Asked Questions About STRIDE - Revision history

Timd: /* What kind of training is required? */

2015-07-07T18:35:10Z

What kind of training is required?

← Older revision		Revision as of 18:35, 7 July 2015
Line 54:		Line 54:
	=== What kind of training is required? ===		=== What kind of training is required? ===

	Our training [[Training Overview \| approach]] is based on wiki articles, samples, and leveraging the [[Stride Sandbox]. The training has been set up for self-guided instruction that can be leveraged for an initial introduction of the technology and on-demand for specific topics when required.		Our training [[Training Overview \| approach]] is based on wiki articles, samples, and leveraging the [[Stride Sandbox]]. The training has been set up for self-guided instruction that can be leveraged for an initial introduction of the technology and on-demand for specific topics when required.

	== Integration with Stride ==		== Integration with Stride ==

Timd: /* On-Target Installation */

2015-07-07T18:34:20Z

On-Target Installation

← Older revision		Revision as of 18:34, 7 July 2015
Line 48:		Line 48:

	==== On-Target Installation ====		==== On-Target Installation ====
	For standard embedded platforms such as Linux, Android and Windows the installation process varies between a few hours to a couple of days. We provide SDK packages that provide a reference to integrators.		For standard embedded platforms such as Linux, Android and Windows the installation process varies between a few hours to a couple of days, depending on the complexity of your build environment. We provide SDK packages that provide a reference to integrators.

	For proprietary embedded targets, a custom [[Platform_Abstraction_Layer\|Platform Abstraction Layer (PAL)]] is required. The PAL provides the glue between the [[STRIDE Runtime \| Stride Runtime]] and services offered by the OS. It is the only piece of the runtime that is customized between operating systems. The implementation of the PAL ranges between a day to a week depending on the complexity of the OS. There is also a [[Build Integration \| build integration]] step. This involves integrating the [[STRIDE Build Tools \| Stride Build Tools]] into your software make process. The activity ranges from a single day to several days.		For proprietary embedded targets, a custom [[Platform_Abstraction_Layer\|Platform Abstraction Layer (PAL)]] is required. The PAL provides the glue between the [[STRIDE Runtime \| Stride Runtime]] and services offered by the OS. It is the only piece of the runtime that is customized between operating systems. The implementation of the PAL ranges between a day to a week depending on the complexity of the OS. There is also a [[Build Integration \| build integration]] step. This involves integrating the [[STRIDE Build Tools \| Stride Build Tools]] into your software make process. The activity ranges from a single day to several days.

	=== What kind of training is required? ===		=== What kind of training is required? ===

Timd: /* Unit Testing */

2015-07-07T18:31:03Z

Unit Testing

← Older revision		Revision as of 18:31, 7 July 2015
Line 17:		Line 17:
	* It can be difficult to automate execution of the full set of tests on the real target device		* It can be difficult to automate execution of the full set of tests on the real target device

	'''Unit Testing''' legacy software may have limited value, particularly if the software is stable with respect to defects. The best ''return-of-effort'' is often experienced when focused on '''brand new''' software components.		'''Unit Testing''' of legacy software may have limited value, particularly if the software is stable with respect to defects. The best ''return-of-effort'' is often experienced when focused on '''brand new''' software components.

	=== API Testing ===		=== API Testing ===

Marku at 02:39, 7 July 2015

2015-07-07T02:39:50Z

Show changes

Marku at 21:37, 1 July 2015

2015-07-01T21:37:11Z

@@ Line 1: / Line 1: @@
 == Getting Started ==
@@ Line 35: / Line 76: @@
 The [[STRIDE Runtime]] overhead is minimized by collecting raw data on the target, and transferring information at a low priority task to the host for processing. Processing is only active when executing tests via the [[STRIDE Runner]].
 == Testing ==
@@ Line 46: / Line 86: @@
 Yes. Tests can be also be built and executed using the [[Off-Target Environment]]. In order for this to work, your device source code must be built along with the test code using the host's desktop toolchain (MSVC on Windows, gcc on Linux).
 == Test Automation  ==
@@ Line 67: / Line 106: @@
 If you are using a continuous integration server to initiate your testing, it's likely that it supports different forms of notification when the testing is complete, so it's often possible to attach the xml report data as part of the CI server notification.
 == Source Instrumentation ==
@@ Line 90: / Line 128: @@
 Yes. Once you have some behavior tests written, it's worthwhile to maintain that instrumentation and the corresponding tests, which allows you to run the tests on any stride-enabled build. All of the instrumentation macros are easily no-opped via a single preprocessor flag, so you can choose to effectively remove the instrumentation code on select builds (production/release builds, for example). The ultimate value of instrumentation is the continuous feedback you get by regularly executing the automated tests on the build.

Timd: /* Getting Started */

2012-11-13T18:03:07Z

Getting Started

← Older revision		Revision as of 18:03, 13 November 2012
Line 3:		Line 3:
	=== How long does it take to install STRIDE? ===		=== How long does it take to install STRIDE? ===

	~~For standard platforms such as Linux the~~ installation ~~process varies between a few hours~~ to a ~~couple of days. We provide [[:Category:SDKs\|SDK packages]] that work out of the box~~ for ~~our [[Off-Target Environment]], but also provide a reference to integrators~~.		==== Off-Target Installation ====
			Off-target installation to a desktop or laptop PC takes just minutes; support is offered for Windows and Linux.

	For proprietary targets a [[Platform_Abstraction_Layer\|Platform Abstraction Layer (PAL)]] is required. The PAL provides the glue between the [[STRIDE Runtime]] and services offered by the OS. It is the only piece of the runtime that is customized between operating systems. The implementation of the PAL ranges between a day to a week depending on the complexity of the OS. There is also a [[Build Integration \| build integration]] step. This involves integrating the [[STRIDE Build Tools]] into your software make process. The activity ranges from a single day to several.		==== On-Target Installation ====
			For standard embedded platforms such as Linux, Android and Windows the installation process varies between a few hours to a couple of days. We provide [[:Category:SDKs\|SDK packages]] that work out of the box for our [[Off-Target Environment]], but also provide a reference to integrators.

			For proprietary embedded targets, a custom [[Platform_Abstraction_Layer\|Platform Abstraction Layer (PAL)]] is required. The PAL provides the glue between the [[STRIDE Runtime]] and services offered by the OS. It is the only piece of the runtime that is customized between operating systems. The implementation of the PAL ranges between a day to a week depending on the complexity of the OS. There is also a [[Build Integration \| build integration]] step. This involves integrating the [[STRIDE Build Tools]] into your software make process. The activity ranges from a single day to several days.

	=== What kind of training is required? ===		=== What kind of training is required? ===

	Our training [[Training Overview \| approach]] is based on wiki articles, [[Samples \| samples]], and leveraging the [[Off-Target Environment]]. The training has been set up for self-guided instruction that can be leveraged for an initial introduction of the technology and on-demand for specific topics when required.		Our training [[Training Overview \| approach]] is based on wiki articles, [[Samples \| samples]], and leveraging the [[Off-Target Environment]]. The training has been set up for self-guided instruction that can be leveraged for an initial introduction of the technology and on-demand for specific topics when required.

	== Integration with STRIDE ==		== Integration with STRIDE ==

Timd at 17:57, 13 November 2012

2012-11-13T17:57:36Z

@@ Line 1: / Line 1: @@
 == Integration with STRIDE ==
@@ Line 20: / Line 32: @@
 The [[STRIDE Runtime]] overhead is minimized by collecting raw data on the target, and transferring information at a low priority task to the host for processing. Processing is only active when executing tests via the [[STRIDE Runner]].
 == Testing ==
@@ Line 51: / Line 42: @@
 Yes. Tests can be also be built and executed using the [[Off-Target Environment]]. In order for this to work, your device source code must be built along with the test code using the host's desktop toolchain (MSVC on Windows, gcc on Linux).
 == Test Automation  ==
@@ Line 72: / Line 64: @@
 If you are using a continuous integration server to initiate your testing, it's likely that it supports different forms of notification when the testing is complete, so it's often possible to attach the xml report data as part of the CI server notification.
-=== How long does it take to install STRIDE? ===
+== Source Instrumentation ==
-For standard platforms such as Linux the installation process varies between a few hours to a couple of days. We provide [[:Category:SDKs|SDK packages]] that work out of the box for our [[Off-Target Environment]], but also provide a reference to integrators.
+Our experience on a wide-range of systems has shown minimal impact from the STRIDE instrumentation.  The STRIDE Runtime has been designed to be small, portable, and readily configurable, allowing it to be optimized for the platform's specific characteristics.
-For proprietary targets a [[Platform_Abstraction_Layer|Platform Abstraction Layer (PAL)]] is required. The PAL provides the glue between the [[STRIDE Runtime]] and services offered by the OS. It is the only piece of the runtime that is customized between operating systems. The implementation of the PAL ranges between a day to a week depending on the complexity of the OS. There is also a [[Build Integration | build integration]] step. This involves integrating the [[STRIDE Build Tools]] into your software make process. The activity ranges from a single day to several.
+=== Should I leave Test Points in? ===
-=== What kind of training is required? ===
+Yes. Once you have some behavior tests written, it's worthwhile to maintain that instrumentation and the corresponding tests, which allows you to run the tests on any stride-enabled build. All of the instrumentation macros are easily no-opped via a single preprocessor flag, so you can choose to effectively remove the instrumentation code on select builds (production/release builds, for example). The ultimate value of instrumentation is the continuous feedback you get by regularly executing the automated tests on the build.
 [[Category: Overview]]

Ivailop: /* Is there any alternative to running STRIDE tests with a real device? */

2011-06-09T17:34:36Z

Is there any alternative to running STRIDE tests with a real device?

← Older revision		Revision as of 17:34, 9 June 2011
Line 50:		Line 50:
	=== Is there any alternative to running STRIDE tests with a real device? ===		=== Is there any alternative to running STRIDE tests with a real device? ===

	Yes. Tests can be also be built and executed using the [[Off-Target Environment]]. In order for this to work, your device source code must be built along with the test code using the host's desktop toolchain (MSVC on ~~windows~~, gcc on ~~linux~~).		Yes. Tests can be also be built and executed using the [[Off-Target Environment]]. In order for this to work, your device source code must be built along with the test code using the host's desktop toolchain (MSVC on Windows, gcc on Linux).

	== Test Automation ==		== Test Automation ==

Ivailop: /* What languages are supported? */

2010-11-03T23:38:12Z

What languages are supported?

← Older revision		Revision as of 23:38, 3 November 2010
Line 46:		Line 46:
	=== What languages are supported? ===		=== What languages are supported? ===

	[[~~Types_of_Testing_Supported~~#Unit Testing \| Unit tests]] and [[~~Types_of_Testing_Supported~~#API_Testing \| API Tests]] are written using '''C and C++'''. [[~~Types_of_Testing_Supported~~#Integration_Testing \| Integration Tests]] can be written using '''Perl''' and '''C/C++'''.		[[Types_of_Testing_Supported_by_STRIDE#Unit Testing \| Unit tests]] and [[Types_of_Testing_Supported_by_STRIDE#API_Testing \| API Tests]] are written using '''C and C++'''. [[Types_of_Testing_Supported_by_STRIDE#Integration_Testing \| Integration Tests]] can be written using '''Perl''' and '''C/C++'''.

	=== Is there any alternative to running STRIDE tests with a real device? ===		=== Is there any alternative to running STRIDE tests with a real device? ===

Ivailop: /* Testing */

2010-11-03T18:26:21Z

Testing

← Older revision		Revision as of 18:26, 3 November 2010
Line 44:		Line 44:
	== Testing ==		== Testing ==

	=== What languages are supported ? ===		=== What languages are supported? ===

	[[Types_of_Testing_Supported#Unit Testing \| Unit tests]] and [[Types_of_Testing_Supported#API_Testing \| API Tests]] are written using '''C and C++'''. [[Types_of_Testing_Supported#Integration_Testing \| Integration Tests]] can be written using '''Perl''' and '''C/C++'''.		[[Types_of_Testing_Supported#Unit Testing \| Unit tests]] and [[Types_of_Testing_Supported#API_Testing \| API Tests]] are written using '''C and C++'''. [[Types_of_Testing_Supported#Integration_Testing \| Integration Tests]] can be written using '''Perl''' and '''C/C++'''.

	=== Is there any alternative to running STRIDE tests with a real device ? ===		=== Is there any alternative to running STRIDE tests with a real device? ===

	Yes. Tests can be also be built and executed using the [[Off-Target Environment]]. In order for this to work, your device source code must be built along with the test code using the host's desktop toolchain (MSVC on windows, gcc on linux).		Yes. Tests can be also be built and executed using the [[Off-Target Environment]]. In order for this to work, your device source code must be built along with the test code using the host's desktop toolchain (MSVC on windows, gcc on linux).