STRIDE Overview - Revision history

Marku at 22:45, 23 November 2010

2010-11-23T22:45:46Z

← Older revision		Revision as of 22:45, 23 November 2010
Line 66:		Line 66:

	<hr/>		<hr/>
	For a PDF version of this article please click [[Media:STRIDE_4.2_Datasheet.pdf \| ''~~here~~'']]		For a '''PDF version''' of this article please click [[Media:STRIDE_4.2_Datasheet.pdf \| '''HERE''']]

			For an '''overview screencast''' of STRIDE please click [[STRIDE_Overview_Video \| '''HERE''']]

			<hr/>
	[[Category: Overview]]		[[Category: Overview]]

Marku: /* STRIDE Testing Features */

2010-11-09T18:31:23Z

STRIDE Testing Features

← Older revision		Revision as of 18:31, 9 November 2010
Line 45:		Line 45:
	* Integration Testing.		* Integration Testing.

	STRIDE has been designed to deliver a broad spectrum of [[What_is_Unique_About_STRIDE#~~Offers_testing_techniques_for_deeper_coverage~~ \| '''testing capabilities''']] that enable teams to '''''test earlier and more effectively'''''. Unique features such as [[What_is_Unique_About_STRIDE#Test_Macros \| '''assertion macros''']], [[What_is_Unique_About_STRIDE#Fixturing \| '''fixturing''']], and [[What_is_Unique_About_STRIDE#Test_Doubles \| '''function doubling''']] facilitate deeper test coverage of your software components. STRIDE also provides [[What_is_Unique_About_STRIDE#Expectations \|'''Expectations''']] as an added validation technique. Expectation testing is unique in that it ''does not'' focus on calling functions and validating return values. The technique rather validates the expected sequencing of the software, along with state data, executing under normal operating conditions.		STRIDE has been designed to deliver a broad spectrum of [[What_is_Unique_About_STRIDE#STRIDE_offers_testing_techniques_for_deeper_coverage \| '''testing capabilities''']] that enable teams to '''''test earlier and more effectively'''''. Unique features such as [[What_is_Unique_About_STRIDE#Test_Macros \| '''assertion macros''']], [[What_is_Unique_About_STRIDE#Fixturing \| '''fixturing''']], and [[What_is_Unique_About_STRIDE#Test_Doubles \| '''function doubling''']] facilitate deeper test coverage of your software components. STRIDE also provides [[What_is_Unique_About_STRIDE#Expectations \|'''Expectations''']] as an added validation technique. Expectation testing is unique in that it ''does not'' focus on calling functions and validating return values. The technique rather validates the expected sequencing of the software, along with state data, executing under normal operating conditions.

	Tests can be implemented in both [[What_is_Unique_About_STRIDE#C.2FC.2B.2B \| '''native code''']] on the target and [[What_is_Unique_About_STRIDE#Script \| '''script''']] on the host.		Tests can be implemented in both [[What_is_Unique_About_STRIDE#C.2FC.2B.2B \| '''native code''']] on the target and [[What_is_Unique_About_STRIDE#Script \| '''script''']] on the host.

Marku at 23:38, 8 November 2010

2010-11-08T23:38:28Z

← Older revision		Revision as of 23:38, 8 November 2010
Line 64:		Line 64:

	</font>		</font>

			<hr/>
			For a PDF version of this article please click [[Media:STRIDE_4.2_Datasheet.pdf \| ''here'']]

	[[Category: Overview]]		[[Category: Overview]]

Marku at 23:42, 4 November 2010

2010-11-04T23:42:23Z

← Older revision		Revision as of 23:42, 4 November 2010
Line 5:		Line 5:
	The STRIDE system consists of:		The STRIDE system consists of:
	; A software ''Framework''		; A software ''Framework''
	: enabling the creation of fully automated '''''Test Assets''''' ~~that repeatably~~ verify the internal design of your software		: enabling the creation of fully automated '''''Test Assets''''' used to verify the internal design of your software

	; A hosted ''Web Application - [[STRIDE_Overview#STRIDE_Test_Space \| '''Test Space''']]		; A hosted ''Web Application - [[STRIDE_Overview#STRIDE_Test_Space \| '''Test Space''']]

Marku at 22:43, 4 November 2010

2010-11-04T22:43:26Z

← Older revision		Revision as of 22:43, 4 November 2010
Line 47:		Line 47:
	STRIDE has been designed to deliver a broad spectrum of [[What_is_Unique_About_STRIDE#Offers_testing_techniques_for_deeper_coverage \| '''testing capabilities''']] that enable teams to '''''test earlier and more effectively'''''. Unique features such as [[What_is_Unique_About_STRIDE#Test_Macros \| '''assertion macros''']], [[What_is_Unique_About_STRIDE#Fixturing \| '''fixturing''']], and [[What_is_Unique_About_STRIDE#Test_Doubles \| '''function doubling''']] facilitate deeper test coverage of your software components. STRIDE also provides [[What_is_Unique_About_STRIDE#Expectations \|'''Expectations''']] as an added validation technique. Expectation testing is unique in that it ''does not'' focus on calling functions and validating return values. The technique rather validates the expected sequencing of the software, along with state data, executing under normal operating conditions.		STRIDE has been designed to deliver a broad spectrum of [[What_is_Unique_About_STRIDE#Offers_testing_techniques_for_deeper_coverage \| '''testing capabilities''']] that enable teams to '''''test earlier and more effectively'''''. Unique features such as [[What_is_Unique_About_STRIDE#Test_Macros \| '''assertion macros''']], [[What_is_Unique_About_STRIDE#Fixturing \| '''fixturing''']], and [[What_is_Unique_About_STRIDE#Test_Doubles \| '''function doubling''']] facilitate deeper test coverage of your software components. STRIDE also provides [[What_is_Unique_About_STRIDE#Expectations \|'''Expectations''']] as an added validation technique. Expectation testing is unique in that it ''does not'' focus on calling functions and validating return values. The technique rather validates the expected sequencing of the software, along with state data, executing under normal operating conditions.

	Tests can be implemented in both [[What_is_Unique_About_STRIDE=#C.2FC.2B.2B \| '''native code''']] on the target and [[What_is_Unique_About_STRIDE#Script \| '''script''']] on the host.		Tests can be implemented in both [[What_is_Unique_About_STRIDE#C.2FC.2B.2B \| '''native code''']] on the target and [[What_is_Unique_About_STRIDE#Script \| '''script''']] on the host.
	<br>		<br>
	<br>		<br>

Marku at 22:40, 4 November 2010

2010-11-04T22:40:37Z

@@ Line 11: / Line 11: @@
 ==STRIDE Framework ==
 [[image:STRIDE 4.2 Framework-a.jpg |right|400px|border ]]
@@ Line 26: / Line 21: @@
 === Runner ===
 The '' '''Framework''' '' also contains a lightweight [[Stride_Runner | '''Runner''']] application that is a host-based command-line utility for interactive and automated test execution. It also provides services for result publishing to our [[STRIDE_Test_Space | '''hosted web application''']].
 ===Build Tools===
@@ Line 31: / Line 28: @@
 The [[STRIDE_Build_Tools | '''STRIDE Build Tools''']] are a set of command-line utilities that integrate with your target software build process. They preprocess standard C/C++ header files that contain STRIDE test declarations to  auto-generate source code comprising a custom [[Intercept_Module | '''Intercept Module''']]. The intercept module code is then built with the Runtime to provide ''fixturing'' and ''harnessing'' test logic as part of your build image.
 ==STRIDE Test Space==
@@ Line 56: / Line 38: @@
 <br>
 <br>
 <br>
 <hr/>

Marku at 15:22, 4 November 2010

2010-11-04T15:22:07Z

← Older revision		Revision as of 15:22, 4 November 2010
Line 7:		Line 7:
	: enabling the creation of fully automated '''''Test Assets''''' that repeatably verify the internal design of your software		: enabling the creation of fully automated '''''Test Assets''''' that repeatably verify the internal design of your software

	; A hosted ''Web Application - [[STRIDE_Test_Space \| '''Test Space''']]		; A hosted ''Web Application - [[STRIDE_Overview#STRIDE_Test_Space \| '''Test Space''']]
	: for storing and analyzing test results, thus providing on-demand availability of timely, accurate, and meaningful test results data.		: for storing and analyzing test results, thus providing on-demand availability of timely, accurate, and meaningful test results data


Line 49:		Line 49:
	==STRIDE Test Space==		==STRIDE Test Space==
	[[image:STRIDE 4.2 Test Space.jpg \| 430px \| right \| border]]		[[image:STRIDE 4.2 Test Space.jpg \| 430px \| right \| border]]
	Once tests have been implemented, they are executed using the host-based '''Runner''' application. Resulting '''test reports''' can be automatically uploaded to our '''web application''' - [[STRIDE_Test_Space \| '''STRIDE Test Space''']]. This application allows both local and distributed team members to track and collaborate on results.		Once tests have been implemented, they are executed using the host-based [[STRIDE_Runner \| '''Runner''']] application. Resulting '''test reports''' can be automatically uploaded to our '''web application''' - [[STRIDE_Test_Space \| '''STRIDE Test Space''']]. This application allows both local and distributed team members to track and collaborate on results.

	Failure resolution is optimized by centralizing results and providing specific source information related to failures. ''Test Space'' also has built-in '''collaboration features''' in the form of email notification for new results and regression against a baseline as well as messaging.		Failure resolution is optimized by centralizing results and providing specific source information related to failures. ''Test Space'' also has built-in '''collaboration features''' in the form of email notification for new results and regression against a baseline as well as messaging.

			<br>
	<br>		<br>
	<br>		<br>

Ivailop at 23:37, 3 November 2010

2010-11-03T23:37:26Z

← Older revision		Revision as of 23:37, 3 November 2010
Line 11:		Line 11:


	STRIDE supports three general [[~~Types_of_Testing_Supported~~ \| '''types of testing''']]:		STRIDE supports three general [[Types_of_Testing_Supported_by_STRIDE \| '''types of testing''']]:
	* Unit Testing,		* Unit Testing,
	* API Testing, and		* API Testing, and

Marku at 21:29, 3 November 2010

2010-11-03T21:29:59Z

← Older revision		Revision as of 21:29, 3 November 2010
Line 1:		Line 1:
	<span style="#color:#0067A5"> <font size="5"> Welcome to the STRIDE™ Wiki </font> </span>		<span style="#color:#0067A5"> <font size="5"> Welcome to the STRIDE™ Wiki </font> </span>
			__NOTOC__
	STRIDE™ is a '''test infrastructure''' used by engineers to implement and execute tests for validating embedded software executing On-Target. STRIDE has been designed specifically for '''On-Target White-box Testing'''.		STRIDE™ is a '''test infrastructure''' used by engineers to implement and execute tests for validating embedded software executing On-Target. STRIDE has been designed specifically for '''On-Target White-box Testing'''.

Line 7:		Line 7:
	: enabling the creation of fully automated '''''Test Assets''''' that repeatably verify the internal design of your software		: enabling the creation of fully automated '''''Test Assets''''' that repeatably verify the internal design of your software

	; A hosted ''Web Application''		; A hosted ''Web Application - [[STRIDE_Test_Space \| '''Test Space''']]
	: for storing and analyzing test results, thus providing on-demand availability of timely, accurate, and meaningful test results data.		: for storing and analyzing test results, thus providing on-demand availability of timely, accurate, and meaningful test results data.

Line 17:		Line 17:


	=The STRIDE Framework =		==The STRIDE Framework ==

			[[image:STRIDE 4.2 Framework-a.jpg \|right\|400px\|border ]]

			===Runtime===
			The STRIDE Framework includes a [[Runtime_Reference \| '''Runtime''']] software source package that supports connectivity with the host system. It is integrated with embedded application software to enable ''testability'' to be compiled into the software with minimal impact on performance or the size of the application. The software is agnostic to the RTOS, CPU, and transport. It can be configured to support multi-processes, multi-threads, user/kernel spaces, or a simpler single application process. Typically the runtime is configured as a background thread and only executes when running tests. It provides [[Runtime_Test_Services \| '''services for testing''']] and [[Source_Instrumentation_Overview \| '''source instrumentation''']].

	[[~~image:STRIDE 4~~.~~2 Framework.jpg~~ \|~~right\|460px\|border~~ ]]		=== Runner ===
			The '' '''Framework''' '' also contains a lightweight [[Stride_Runner \| '''Runner''']] application that is a host-based command-line utility for interactive and automated test execution. It also provides services for result publishing to our [[STRIDE_Test_Space \| '''hosted web application''']].

	==~~Runtime~~==		===Build Tools===
	~~The STRIDE Framework includes a~~ [[~~Runtime_Reference \| '''Runtime''']] software source package that supports connectivity with the host system~~. It is integrated with embedded application software to enable ''testability'' to be compiled into the software with minimal impact on performance or the size of the application. The software is agnostic to the RTOS, CPU, and transport. It can be configured to support multi-~~processes, multi-threads, user/kernel spaces, or a simpler single application process~~. ~~Typically the runtime is configured as a background thread and only executes when running tests. It provides [[Runtime_Test_Services~~ \| ~~'''services for testing''']] and [[Source_Instrumentation_Overview~~ \| ~~'''source instrumentation'''~~]].		[[image:STRIDE 4.2 Framework-b.jpg \|right\|300px \| border]]

	~~==Build Tools==~~
	The [[STRIDE_Build_Tools \| '''STRIDE Build Tools''']] are a set of command-line utilities that integrate with your target software build process. They preprocess standard C/C++ header files that contain STRIDE test declarations to auto-generate source code comprising a custom [[Intercept_Module \| '''Intercept Module''']]. The intercept module code is then built with the Runtime to provide ''fixturing'' and ''harnessing'' test logic as part of your build image.		The [[STRIDE_Build_Tools \| '''STRIDE Build Tools''']] are a set of command-line utilities that integrate with your target software build process. They preprocess standard C/C++ header files that contain STRIDE test declarations to auto-generate source code comprising a custom [[Intercept_Module \| '''Intercept Module''']]. The intercept module code is then built with the Runtime to provide ''fixturing'' and ''harnessing'' test logic as part of your build image.

	~~== Runner ==~~
	The '' '''Framework''' '' also contains a lightweight [[Stride_Runner \| '''Runner''']] application that is a host-based command-line utility for interactive and automated test execution. It also provides services for result publishing to our [[STRIDE_Test_Space \| '''hosted web application''']].

	==~~Test Capabilities~~==		== Testing Features ==
	STRIDE has been designed to deliver a broad spectrum of [[What_is_Unique_About_STRIDE#Offers_testing_techniques_for_deeper_coverage \| '''testing capabilities''']] that enable teams to '''''test earlier and more effectively'''''. Unique features such as [[Test_Macros \| '''test macros''']], [[File_Transfer_Services \| '''file fixturing''']], and [[Using_Test_Doubles \| '''function doubling''']] facilitate deeper test coverage of your software components.		STRIDE has been designed to deliver a broad spectrum of [[What_is_Unique_About_STRIDE#Offers_testing_techniques_for_deeper_coverage \| '''testing capabilities''']] that enable teams to '''''test earlier and more effectively'''''. Unique features such as [[Test_Macros \| '''test macros''']], [[File_Transfer_Services \| '''file fixturing''']], and [[Using_Test_Doubles \| '''function doubling''']] facilitate deeper test coverage of your software components.

Line 45:		Line 47:
	The tests can be implemented in both [[Test_Units_Overview \| '''native code''']] on the target and [[Test_Modules_Overview \| '''script''']] on the host.		The tests can be implemented in both [[Test_Units_Overview \| '''native code''']] on the target and [[Test_Modules_Overview \| '''script''']] on the host.

	=STRIDE Test Space=		==STRIDE Test Space==
	[[image:STRIDE 4.2 Test Space.jpg \| 430px \| right \| border]]		[[image:STRIDE 4.2 Test Space.jpg \| 430px \| right \| border]]
	Once tests have been implemented, they are executed using the host-based '''Runner''' application. Resulting '''test reports''' can be automatically uploaded to our '''web application''' - [[STRIDE_Test_Space \| '''STRIDE Test Space''']]. This application allows both local and distributed team members to track and collaborate on results.		Once tests have been implemented, they are executed using the host-based '''Runner''' application. Resulting '''test reports''' can be automatically uploaded to our '''web application''' - [[STRIDE_Test_Space \| '''STRIDE Test Space''']]. This application allows both local and distributed team members to track and collaborate on results.
Line 51:		Line 53:
	Failure resolution is optimized by centralizing results and providing specific source information related to failures. ''Test Space'' also has built-in '''collaboration features''' in the form of email notification for new results and regression against a baseline as well as messaging.		Failure resolution is optimized by centralizing results and providing specific source information related to failures. ''Test Space'' also has built-in '''collaboration features''' in the form of email notification for new results and regression against a baseline as well as messaging.

	~~<br>~~
	<br>		<br>
	<br>		<br>
Line 61:		Line 62:
	<hr/>		<hr/>

	* '''[[What is Unique About STRIDE]]'''		* '''[[What is Unique About STRIDE \| What is Unique About STRIDE]]'''

	* '''[[Types of Testing Supported]]'''		* '''[[Types of Testing Supported by STRIDE \| Types of Testing Supported]]'''

	* '''[[Frequently Asked Questions About STRIDE \| Frequently Asked Questions]]'''		* '''[[Frequently Asked Questions About STRIDE \| Frequently Asked Questions]]'''

Marku at 22:49, 2 November 2010

2010-11-02T22:49:41Z

← Older revision		Revision as of 22:49, 2 November 2010
Line 1:		Line 1:
	STRIDE™ has been designed specifically for ''on-target white-box testing''. STRIDE™ is a test system used for validating embedded software executing on-target. The STRIDE™ system consists of a '' '''Framework''' '' for testing and a hosted '' '''Web Application''' '' for storing and analyzing test results.		<span style="#color:#0067A5"> <font size="5"> Welcome to the STRIDE™ Wiki </font> </span>

	~~The '' '''Framework''' '' includes~~ a ''~~cross-platform~~'' ~~[[Runtime_Reference \|~~ ''~~'runtime''']] source package that supports connectivity with the host system~~ and ~~provides [[Runtime_Test_Services \| '''services~~ for ~~testing''']] and [[Source_Instrumentation_Overview \| '''source instrumentation''']]. The '' '''runtime''' '' enables testability to be compiled into the~~ embedded software ~~with minimal impact on performance or the size of the application~~. ~~The~~ '' '~~''Framework''' '' also contains a host~~-~~based [[Stride_Runner \| '''runner''']] for interactive and automated test execution and publishing to our [[STRIDE_Test_Space \| '''hosted web application~~''']].		STRIDE™ is a '''test infrastructure''' used by engineers to implement and execute tests for validating embedded software executing On-Target. STRIDE has been designed specifically for '''On-Target White-box Testing'''.

			The STRIDE system consists of:
			; A software ''Framework''
			: enabling the creation of fully automated '''''Test Assets''''' that repeatably verify the internal design of your software

	~~[[image~~:~~STRIDE 4~~.~~2.jpg \| 500px]]~~		; A hosted ''Web Application''
			: for storing and analyzing test results, thus providing on-demand availability of timely, accurate, and meaningful test results data.

	STRIDE's test system is designed to deliver a broad spectrum of ''testing capabilities'' that enable teams to test earlier and more effectively. Developers can implement [[Test_Units_Overview \| '''API and unit tests''']] in C/C++ that execute on On-Target and are controlled from the host. Unique features such as [[File_Transfer_Services \| '''file fixturing''']] and [[Using_Test_Doubles \| '''function doubling''']] facilitate deeper coverage of your software components. Because the '' '''Framework''' '' is ''cross-platform'', testing can also be executed using Off-Target environments such as Windows and Linux host machines. The [[Linux SDK \| '''Linux''']] and [[Windows SDK \| '''Windows''']] ''SDKs'' allow for a seamless transition between the real target and an off-target host environment.

	~~Beyond traditional developer~~ testing, STRIDE also ~~provides~~ [[~~Test_Modules_Overview~~ \|'''~~behavior~~-based testing ~~techniques~~''']]. ~~Behavior-based~~ testing is ~~different than unit testing or API testing~~ in that it ''does not'' focus on calling functions and validating return values. ~~Behavior testing,~~ rather, validates the ''expected sequencing of the software'' executing under normal operating conditions. This can span threads and process boundaries, and even multiple targets, as the application(s) is running. Developers insert instrumentation [[Test_Point \| '''~~macros~~''']] to enable this approach, making it especially effective for testing legacy code. This kind of ''~~expectation-based~~'' ~~testing~~ can be used to ~~validate~~ broadly scoped scenarios that span system~~-wide, for~~ example:		STRIDE supports three general [[Types_of_Testing_Supported \| '''types of testing''']]:
			* Unit Testing,
			* API Testing, and
			* Integration Testing.


			=The STRIDE Framework =


			[[image:STRIDE 4.2 Framework.jpg \|right\|460px\|border ]]

			==Runtime==
			The STRIDE Framework includes a [[Runtime_Reference \| '''Runtime''']] software source package that supports connectivity with the host system. It is integrated with embedded application software to enable ''testability'' to be compiled into the software with minimal impact on performance or the size of the application. The software is agnostic to the RTOS, CPU, and transport. It can be configured to support multi-processes, multi-threads, user/kernel spaces, or a simpler single application process. Typically the runtime is configured as a background thread and only executes when running tests. It provides [[Runtime_Test_Services \| '''services for testing''']] and [[Source_Instrumentation_Overview \| '''source instrumentation''']].

			==Build Tools==
			The [[STRIDE_Build_Tools \| '''STRIDE Build Tools''']] are a set of command-line utilities that integrate with your target software build process. They preprocess standard C/C++ header files that contain STRIDE test declarations to auto-generate source code comprising a custom [[Intercept_Module \| '''Intercept Module''']]. The intercept module code is then built with the Runtime to provide ''fixturing'' and ''harnessing'' test logic as part of your build image.

			== Runner ==
			The '' '''Framework''' '' also contains a lightweight [[Stride_Runner \| '''Runner''']] application that is a host-based command-line utility for interactive and automated test execution. It also provides services for result publishing to our [[STRIDE_Test_Space \| '''hosted web application''']].

			==Test Capabilities==
			STRIDE has been designed to deliver a broad spectrum of [[What_is_Unique_About_STRIDE#Offers_testing_techniques_for_deeper_coverage \| '''testing capabilities''']] that enable teams to '''''test earlier and more effectively'''''. Unique features such as [[Test_Macros \| '''test macros''']], [[File_Transfer_Services \| '''file fixturing''']], and [[Using_Test_Doubles \| '''function doubling''']] facilitate deeper test coverage of your software components.

			STRIDE also provides [[Expectations \|'''Expectations''']] as an added validation technique. Expectation testing is unique in that it ''does not'' focus on calling functions and validating return values. The technique rather validates the '''''expected sequencing of the software, along with state data,''''' executing under normal operating conditions. This can span threads and process boundaries, and even multiple targets, as the application(s) is running. Developers insert simple instrumentation macros called [[Test_Point \| '''Test Points''']] to enable this approach, making it especially effective for testing legacy code.

			This kind of ''validation'' technique can be used to test broadly scoped scenarios that span your entire system; For example:

	* Complete data flow through system components		* Complete data flow through system components
Line 15:		Line 43:
	* … and much more		* … and much more

	Once tests have been implemented, they are executed using the '' ''~~'runner~~''' '' ~~and~~ test reports can be automatically uploaded to our '''web application''' - [[STRIDE_Test_Space \| '''STRIDE Test Space''']]. This application allows ~~all~~ team members to track and collaborate on ~~results. Failure resolution is optimized by centralizing results, providing specific source information related to failures, and automatic email notification for new~~ results.		The tests can be implemented in both [[Test_Units_Overview \| '''native code''']] on the target and [[Test_Modules_Overview \| '''script''']] on the host.

			=STRIDE Test Space=
			[[image:STRIDE 4.2 Test Space.jpg \| 430px \| right \| border]]
			Once tests have been implemented, they are executed using the host-based '''Runner''' application. Resulting '''test reports''' can be automatically uploaded to our '''web application''' - [[STRIDE_Test_Space \| '''STRIDE Test Space''']]. This application allows both local and distributed team members to track and collaborate on results.

	<~~!--hr/--~~>		Failure resolution is optimized by centralizing results and providing specific source information related to failures. ''Test Space'' also has built-in '''collaboration features''' in the form of email notification for new results and regression against a baseline as well as messaging.
	<br/>
			<br>
			<br>
			<br>
			<br>
			<hr/>

	<font size="3">		<font size="3">
	'''For more details refer to the following:'''		'''For more details refer to the following:'''
			<hr/>

	* '''[[What is Unique About STRIDE]]'''		* '''[[What is Unique About STRIDE]]'''
Line 28:		Line 66:

	* '''[[Frequently Asked Questions About STRIDE \| Frequently Asked Questions]]'''		* '''[[Frequently Asked Questions About STRIDE \| Frequently Asked Questions]]'''


	</font>		</font>

	[[Category: Overview]]		[[Category: Overview]]