Test Units Overview - Revision history

Ivailop: /* Unique STRIDE Test Unit Features */

2013-09-25T23:09:57Z

Unique STRIDE Test Unit Features

← Older revision		Revision as of 23:09, 25 September 2013
Line 18:		Line 18:
	In addition, STRIDE Test Units offer these unique features:		In addition, STRIDE Test Units offer these unique features:
	; On-Target Execution		; On-Target Execution
	: Tests execute on the target hardware in a true operational environment. Execution and reporting is controlled from a remote Windows or ~~Linux~~ host		: Tests execute on the target hardware in a true operational environment. Execution and reporting is controlled from a remote desktop (Windows, Linux or FreeBSD) host
	; Dynamic Test and Suite Generation		; Dynamic Test and Suite Generation
	: Test cases and suites can be created and manipulated at runtime		: Test cases and suites can be created and manipulated at runtime

2010-06-02T22:16:36Z

Unique STRIDE Test Unit Features

← Older revision		Revision as of 22:16, 2 June 2010
Line 23:		Line 23:
	; [[Using Test Doubles\|Test Doubles]]		; [[Using Test Doubles\|Test Doubles]]
	: Dynamic runtime function substitution to implement on-the-fly mocks, stubs, and doubles		: Dynamic runtime function substitution to implement on-the-fly mocks, stubs, and doubles
	; [[~~Using~~ Test ~~Points~~\|~~Asynchronous~~ Testing ~~Framework~~]] (Test Points)		; [[Test Point Testing in C/C++\|Behavior Testing]] (Test Points)
	: Support for testing of asynchronous activities occurring in multiple threads		: Support for testing of asynchronous activities occurring in multiple threads
	; Multiprocess Testing Framework		; Multiprocess Testing Framework

2010-05-25T23:15:30Z

Test Unit Features

← Older revision		Revision as of 23:15, 25 May 2010
Line 11:		Line 11:
	* Specification of expected results within test methods (typically by using one or more [[Test Code Macros]])		* Specification of expected results within test methods (typically by using one or more [[Test Code Macros]])
	* Test fixturing (optional setup and teardown)		* Test fixturing (optional setup and teardown)
			* Test parametrization (optional constructor/initialization parameters)
	* Automated execution		* Automated execution
	* Automated results report generation		* Automated results report generation

2010-05-05T22:23:48Z

2010-05-05T22:04:17Z

← Older revision	Revision as of 22:04, 5 May 2010
(No difference)

2010-02-15T21:46:36Z

Individual Tests

← Older revision		Revision as of 21:46, 15 February 2010
Line 37:		Line 37:
	# Setting up a test fixture (optional)		# Setting up a test fixture (optional)
	# Exercising the System Under Test (SUT)		# Exercising the System Under Test (SUT)
	# Verifying that the expected outcome has occurred (typically using calls to ''~~Pass/Fail~~ Macros'' or ''Test Points'')		# Verifying that the expected outcome has occurred (typically using calls to ''Test Code Macros'' or ''Test Points'')
	# Tearing down the test fixture (optional)		# Tearing down the test fixture (optional)

2010-02-15T21:45:50Z

Test Unit Features

← Older revision		Revision as of 21:45, 15 February 2010
Line 9:		Line 9:
	* Specification of a test as a test method		* Specification of a test as a test method
	* Aggregation of individual tests into test suites which form execution and reporting units		* Aggregation of individual tests into test suites which form execution and reporting units
	* Specification of expected results within test methods (typically by using one or more [[~~Pass/Fail Macros\|~~Test Macros]])		* Specification of expected results within test methods (typically by using one or more [[Test Code Macros]])
	* Test fixturing (optional setup and teardown)		* Test fixturing (optional setup and teardown)
	* Automated execution		* Automated execution

2009-09-30T17:12:57Z

Text replace - 'Category:For Developers...' to 'Category:Testing'

2009-09-22T19:19:58Z

Integrating Test Units Into Your Target Build

← Older revision		Revision as of 19:19, 22 September 2009
Line 199:		Line 199:

	== Integrating Test Units Into Your Target Build ==		== Integrating Test Units Into Your Target Build ==
	STRIDE Test Units are easily [[Integration_Overview\|integrated into your target build ~~since~~]] all required test harnessing code is automatically generated based on header files that include [[Test Unit Pragmas\|STRIDE Test pragmas]].		STRIDE Test Units are easily [[Integration_Overview\|integrated into your target build]] since all required test harnessing code is automatically generated based on header files that include [[Test Unit Pragmas\|STRIDE Test pragmas]].

	This harnessing code (referred to as [[Intercept Module\|Intercept Module]], or IM code) is responsible for		This harnessing code (referred to as [[Intercept Module\|Intercept Module]], or IM code) is responsible for

2009-09-22T19:19:36Z

Integrating Test Units Into Your Target Build

← Older revision		Revision as of 19:19, 22 September 2009
Line 199:		Line 199:

	== Integrating Test Units Into Your Target Build ==		== Integrating Test Units Into Your Target Build ==
	STRIDE Test Units are easily integrated into your target build since all required test harnessing code is automatically generated based on header files that include [[Test Unit Pragmas\|STRIDE Test pragmas]].		STRIDE Test Units are easily [[Integration_Overview\|integrated into your target build since]] all required test harnessing code is automatically generated based on header files that include [[Test Unit Pragmas\|STRIDE Test pragmas]].

	This harnessing code (referred to as [[Intercept Module\|Intercept Module]], or IM code) is responsible for		This harnessing code (referred to as [[Intercept Module\|Intercept Module]], or IM code) is responsible for