Training Overview (old) - Revision history

Marku: Marku moved page Training Overview to Training Overview (old) without leaving a redirect

2014-11-22T15:01:40Z

Marku moved page Training Overview to Training Overview (old) without leaving a redirect

← Older revision	Revision as of 15:01, 22 November 2014
(No difference)

Ivailop: /* Prerequisites */

2013-09-24T19:56:07Z

Prerequisites

← Older revision		Revision as of 19:56, 24 September 2013
Line 5:		Line 5:
	In order to build and execute the samples that we use in the training, please complete and verify the following prerequisites		In order to build and execute the samples that we use in the training, please complete and verify the following prerequisites

	# complete the [[Desktop Installation]]. Be sure to include ~~perl~~, as described in the ~~installation for~~ [[Desktop_Installation#~~Perl_Setup~~\|~~windows]] or [[Desktop_Installation#Perl_Setup_2\|linux~~]], if you want to do training related to host-based test scripting.		# complete the [[Desktop Installation]]. Be sure to include Perl, as described in the [[Desktop_Installation#Perl_Installation_.28Optional.29\|article]], if you want to do training related to host-based test scripting.
	# setup [[Test Space Setup \| Test Space]] for test result publishing		# setup [[Test Space Setup \| Test Space]] for test result publishing
	# install the desktop development toolchain for your host, as described in the [[Off-Target Environment]] article. This is required for building the STRIDE runtime and samples.		# install the desktop development toolchain for your host, as described in the [[Off-Target Environment]] article. This is required for building the STRIDE runtime and samples.

Marku at 16:43, 29 August 2011

2011-08-29T16:43:55Z

← Older revision		Revision as of 16:43, 29 August 2011
Line 26:		Line 26:
	* For most samples, we provide some observations that help summarize aspects of the results that might be of interest to you. These observations are not necessarily comprehensive - in fact, we hope you'll discover other interesting features in the samples that we haven't mentioned.		* For most samples, we provide some observations that help summarize aspects of the results that might be of interest to you. These observations are not necessarily comprehensive - in fact, we hope you'll discover other interesting features in the samples that we haven't mentioned.

	[[Category: ~~Training~~]]		[[Category: Training_OLD]]

Marku: /* How we train */

2010-12-08T19:32:13Z

How we train

← Older revision		Revision as of 19:32, 8 December 2010
Line 12:		Line 12:
	== How we train ==		== How we train ==

	Our training articles are based on a handful of [[Samples \| samples]] that we ~~provide with the~~ [[~~Off-Target Environment~~ \| ~~off-target~~]] ~~framework distribution~~. The samples are self-documented (using doxygen or perldoc) and this content will be attached to the test report whenever a sample is executed.		Our training articles are based on a handful of [[Samples \| samples]] that we [[Desktop_Installation#Directories_and_Files \| provide with]] the Desktop installation package. The samples are self-documented (using doxygen or perldoc) and this content will be attached to the test report whenever a sample is executed.

	The samples were created to be as simple as possible while sufficiently demonstrating the topic at hand. In particular, the samples are '''very light''' on core application logic (that is, the source under test) -- they focus instead on the code that leverages STRIDE to define and execute tests. As you review the sample code, if you find yourself confused about which code is the test logic and which is the source under test, try reading the source file comments to discern this. If you are still unclear about how the source is organized, feel free to contact us for clarification.		The samples were created to be as simple as possible while sufficiently demonstrating the topic at hand. In particular, the samples are '''very light''' on core application logic (that is, the source under test) -- they focus instead on the code that leverages STRIDE to define and execute tests. As you review the sample code, if you find yourself confused about which code is the test logic and which is the source under test, try reading the source file comments to discern this. If you are still unclear about how the source is organized, feel free to contact us for clarification.

Marku: /* Prerequisites */

2010-12-08T19:24:42Z

Prerequisites

← Older revision		Revision as of 19:24, 8 December 2010
Line 5:		Line 5:
	In order to build and execute the samples that we use in the training, please complete and verify the following prerequisites		In order to build and execute the samples that we use in the training, please complete and verify the following prerequisites

	# complete the [[Desktop Installation]]. Be sure to include perl, as described in the installation for [[Desktop_Installation#~~Perl~~\|windows]] or [[Desktop_Installation#~~Perl_2~~\|linux]], if you want to do training related to host-based test scripting.		# complete the [[Desktop Installation]]. Be sure to include perl, as described in the installation for [[Desktop_Installation#Perl_Setup\|windows]] or [[Desktop_Installation#Perl_Setup_2\|linux]], if you want to do training related to host-based test scripting.
	# setup [[Test Space Setup \| Test Space]] for test result publishing		# setup [[Test Space Setup \| Test Space]] for test result publishing
	# install the desktop development toolchain for your host, as described in the [[Off-Target Environment]] article. This is required for building the STRIDE runtime and samples.		# install the desktop development toolchain for your host, as described in the [[Off-Target Environment]] article. This is required for building the STRIDE runtime and samples.

Marku: /* Prerequisites */

2010-08-23T16:03:19Z

Prerequisites

← Older revision		Revision as of 16:03, 23 August 2010
Line 3:		Line 3:
	== Prerequisites ==		== Prerequisites ==

	In order to build and execute the samples that we use in the training, please complete or verify the following prerequisites		In order to build and execute the samples that we use in the training, please complete and verify the following prerequisites

	# complete the [[Desktop Installation]]. Be sure to include perl, as described in the installation for [[Desktop_Installation#~~perl~~\|~~linux~~]] or [[Desktop_Installation#~~perl_2~~\|~~windows~~]], if you want to do training related to host-based test scripting.		# complete the [[Desktop Installation]]. Be sure to include perl, as described in the installation for [[Desktop_Installation#Perl\|windows]] or [[Desktop_Installation#Perl_2\|linux]], if you want to do training related to host-based test scripting.
	# install the desktop development toolchain for your host, as described ~~for~~ [[~~Desktop_Installation#GCC\|linux]] or [[Desktop_Installation#Microsoft_Visual_Studio\|windows~~]]. This is required for building the STRIDE runtime and samples.		# setup [[Test Space Setup \| Test Space]] for test result publishing
	~~# read the [[Off-Target Environment]] over article on leveraging your own training '''sandbox'''.~~		# install the desktop development toolchain for your host, as described in the [[Off-Target Environment]] article. This is required for building the STRIDE runtime and samples.
	~~# build a [[Off-Target_Test_App \| test app]] and successful execute [[Off-Target_Test_App#Diagnostics \| diagnostics]]~~.
	# read the [[STRIDE Overview]] article(s) to familiarize yourself with the high-level approach and components of STRIDE.		# read the [[STRIDE Overview]] article(s) to familiarize yourself with the high-level approach and components of STRIDE.

Marku: /* How we train */

2010-06-08T14:38:04Z

How we train

← Older revision		Revision as of 14:38, 8 June 2010
Line 13:		Line 13:
	== How we train ==		== How we train ==

	Our training articles are based on a handful of samples that we provide with the off-target framework distribution. The samples are ~~usually~~ self-documented (using doxygen or perldoc) and this content will be attached to the test report whenever a sample is executed.		Our training articles are based on a handful of [[Samples \| samples]] that we provide with the [[Off-Target Environment \| off-target]] framework distribution. The samples are self-documented (using doxygen or perldoc) and this content will be attached to the test report whenever a sample is executed.

	The samples were created to be as simple as possible while sufficiently demonstrating the topic at hand. In particular, the samples are '''very light''' on core application logic (that is, the source under test) -- they focus instead on the code that leverages STRIDE to define and execute tests. As you review the sample code, if you find yourself confused about which code is the test logic and which is the source under test, try reading the source file comments to discern this. If you are still unclear about how the source is organized, feel free to contact us for clarification.		The samples were created to be as simple as possible while sufficiently demonstrating the topic at hand. In particular, the samples are '''very light''' on core application logic (that is, the source under test) -- they focus instead on the code that leverages STRIDE to define and execute tests. As you review the sample code, if you find yourself confused about which code is the test logic and which is the source under test, try reading the source file comments to discern this. If you are still unclear about how the source is organized, feel free to contact us for clarification.

Marku: /* Prerequisites */

2010-06-07T21:55:39Z

Prerequisites

← Older revision		Revision as of 21:55, 7 June 2010
Line 5:		Line 5:
	In order to build and execute the samples that we use in the training, please complete or verify the following prerequisites		In order to build and execute the samples that we use in the training, please complete or verify the following prerequisites

	# complete the [[Desktop Installation]]. Be sure to include perl in the installation if you want to do training related to host-based test scripting~~. Verify that the diagnostics pass after installation~~.		# complete the [[Desktop Installation]]. Be sure to include perl, as described in the installation for [[Desktop_Installation#perl\|linux]] or [[Desktop_Installation#perl_2\|windows]], if you want to do training related to host-based test scripting.
	# install the desktop development toolchain for your host, as described for [[Desktop_Installation#GCC\|linux]] or [[Desktop_Installation#Microsoft_Visual_Studio\|windows]]. This is required for building the STRIDE runtime and samples.		# install the desktop development toolchain for your host, as described for [[Desktop_Installation#GCC\|linux]] or [[Desktop_Installation#Microsoft_Visual_Studio\|windows]]. This is required for building the STRIDE runtime and samples.
	# read the [[STRIDE Overview]] article to familiarize yourself with the high-level approach and components of STRIDE.		# read the [[Off-Target Environment]] over article on leveraging your own training '''sandbox'''.
			# build a [[Off-Target_Test_App \| test app]] and successful execute [[Off-Target_Test_App#Diagnostics \| diagnostics]].
			# read the [[STRIDE Overview]] article(s) to familiarize yourself with the high-level approach and components of STRIDE.

	== How we train ==		== How we train ==

Marku at 21:32, 7 June 2010

2010-06-07T21:32:09Z

← Older revision		Revision as of 21:32, 7 June 2010
Line 24:		Line 24:
	* review the reports that are produced when you run the samples. The reports give you a feel for how data is reported in the STRIDE Framework. The extracted documentation is also provided in the report.		* review the reports that are produced when you run the samples. The reports give you a feel for how data is reported in the STRIDE Framework. The extracted documentation is also provided in the report.
	* For most samples, we provide some observations that help summarize aspects of the results that might be of interest to you. These observations are not necessarily comprehensive - in fact, we hope you'll discover other interesting features in the samples that we haven't mentioned.		* For most samples, we provide some observations that help summarize aspects of the results that might be of interest to you. These observations are not necessarily comprehensive - in fact, we hope you'll discover other interesting features in the samples that we haven't mentioned.

			[[Category: Training]]

Mikee: moved ++WIP++ Training Overview to Training Overview

2010-06-07T21:06:25Z

moved ++WIP++ Training Overview to Training Overview

← Older revision	Revision as of 21:06, 7 June 2010
(No difference)