Test Function List Sample - Revision history

Ivailop: /* Tests Description */

2014-08-05T19:33:47Z

Tests Description

← Older revision		Revision as of 19:33, 5 August 2014
Line 18:		Line 18:

	==== runtimeservices_simple ====		==== runtimeservices_simple ====
	This example shows how to use [[Runtime Test Services#srTestCaseSetStatus\|srTestCaseSetStatus]] to set status and [[Runtime Test Services#~~srTestCaseAddComment~~\|~~srTestCaseAddComment~~]] to add a comment.		This example shows how to use [[Runtime Test Services#srTestCaseSetStatus\|srTestCaseSetStatus]] to set status and [[Runtime Test Services#srTestCaseAddAnnotation\|srTestCaseAddAnnotation]] to add a comment.

	==== runtimeservices_dynamic ====		==== runtimeservices_dynamic ====
	This example shows how to use ~~[[Runtime Test Services#srTestSuiteAddSuite\|srTestSuiteAddSuite]],~~ [[Runtime Test Services#srTestSuiteAddCase\|srTestSuiteAddCase]], [[Runtime Test Services#~~srTestSuiteAddAnnotation~~\|~~srTestSuiteAddAnnotation~~]], and [[Runtime Test Services#srTestAnnotationAddComment\|srTestAnnotationAddComment]] for dynamic suite, test, and annotation creation in the context of a single test method.		This example shows how to use [[Runtime Test Services#srTestSuiteAddCase\|srTestSuiteAddCase]], [[Runtime Test Services#srTestCaseAddAnnotation\|srTestCaseAddAnnotation]], and [[Runtime Test Services#srTestAnnotationAddComment\|srTestAnnotationAddComment]] for dynamic suite, test, and annotation creation in the context of a single test method.

	==== runtimeservices_override ====		==== runtimeservices_override ====
Line 27:		Line 27:

	==== runtimeservices_varcomment ====		==== runtimeservices_varcomment ====
	This example demonstrates the use of [http://en.wikipedia.org/wiki/Printf printf] style format strings with [[Runtime Test Services#~~srTestCaseAddComment~~\|~~srTestCaseAddComment~~]].		This example demonstrates the use of [http://en.wikipedia.org/wiki/Printf printf] style format strings with [[Runtime Test Services#srTestCaseAddAnnotation\|srTestCaseAddAnnotation]].

	== Run Tests ==		== Run Tests ==

Ivailop: /* runtimeservices_simple */

2011-07-05T23:31:34Z

runtimeservices_simple

← Older revision		Revision as of 23:31, 5 July 2011
Line 18:		Line 18:

	==== runtimeservices_simple ====		==== runtimeservices_simple ====
	This example shows how to use [[Runtime Test Services#srTestCaseSetStatus\|srTestCaseSetStatus]] to set status, [[Runtime Test Services#srTestCaseAddComment\|srTestCaseAddComment]] to add a comment.		This example shows how to use [[Runtime Test Services#srTestCaseSetStatus\|srTestCaseSetStatus]] to set status and [[Runtime Test Services#srTestCaseAddComment\|srTestCaseAddComment]] to add a comment.

	==== runtimeservices_dynamic ====		==== runtimeservices_dynamic ====

Ivailop: /* runtimeservices_simple */

2011-07-05T23:29:39Z

runtimeservices_simple

← Older revision		Revision as of 23:29, 5 July 2011
Line 18:		Line 18:

	==== runtimeservices_simple ====		==== runtimeservices_simple ====
	This example shows how to use [[Runtime Test Services#srTestCaseSetStatus\|srTestCaseSetStatus]] to set status, [[Runtime Test Services#srTestCaseAddComment\|srTestCaseAddComment]] to add a comment~~, and srTEST_ADD_COMMENT_WITH_LOCATION to add a comment that automatically includes line and file information~~.		This example shows how to use [[Runtime Test Services#srTestCaseSetStatus\|srTestCaseSetStatus]] to set status, [[Runtime Test Services#srTestCaseAddComment\|srTestCaseAddComment]] to add a comment.

	==== runtimeservices_dynamic ====		==== runtimeservices_dynamic ====

Marku at 16:52, 9 June 2011

2011-06-09T16:52:57Z

@@ Line 1: / Line 1: @@
 == Introduction ==
-Function Lists are abbreviated as ''flist'' in both pragmas (as in [[scl_test_flist]]) and documentation. The Test flist Samples pertain to test units that contain lists of functions to be executed. The Test FList functionality is intended as a simple grouping of test functions and are designed to be used with the C language (although it is not restricted from compilation in a C++ environment as well). Test FLists does not support more advanced usages patterns like private test data. If you need more advanced functionality, consider using [[Test Class Samples|Test Classes (C++)]] or [[Test CClass Samples|Test C-Classes]].
+Function Lists are abbreviated as ''flist'' in both pragmas (as in [[scl_test_flist]]) and documentation. The Test flist Samples pertain to test units that contain lists of functions to be executed. The Test FList functionality is intended as a simple grouping of test functions and are designed to be used with the C language (although it is not restricted from compilation in a C++ environment as well). Test FLists does not support more advanced usages patterns like private test data. If you need more advanced functionality, consider using [[Test Class Sample|Test Classes (C++)]] or [[Test CClass Sample|Test C-Classes]].
 == Tests Description ==
@@ Line 28: / Line 28: @@
 ==== runtimeservices_varcomment ====
 This example demonstrates the use of [http://en.wikipedia.org/wiki/Printf printf] style format strings with [[Runtime Test Services#srTestCaseAddComment|srTestCaseAddComment]].
 [[Category: Samples]]

Marku: moved Test Function List Samples to Test Function List Sample

2011-06-06T23:49:13Z

moved Test Function List Samples to Test Function List Sample

← Older revision	Revision as of 23:49, 6 June 2011
(No difference)

Ivailop: /* basic_simple */

2009-10-01T00:32:48Z

basic_simple

← Older revision		Revision as of 00:32, 1 October 2009
Line 9:		Line 9:

	==== basic_simple ====		==== basic_simple ====
	This example demonstrates passing and failing tests using the primary integer types that infer status from.		This example demonstrates passing and failing tests using the primary integer (int, short, and char) types that infer status from.

	==== basic_fixtures ====		==== basic_fixtures ====

Ivailop: /* basic_simple */

2009-10-01T00:31:12Z

basic_simple

← Older revision		Revision as of 00:31, 1 October 2009
Line 9:		Line 9:

	==== basic_simple ====		==== basic_simple ====
	This example demonstrates passing and failing tests using the primary ~~POD~~ types that infer status from ~~(int, short, and char)~~.		This example demonstrates passing and failing tests using the primary integer types that infer status from.

	==== basic_fixtures ====		==== basic_fixtures ====

Ivailop: /* basic_simple */

2009-10-01T00:24:40Z

basic_simple

← Older revision		Revision as of 00:24, 1 October 2009
Line 9:		Line 9:

	==== basic_simple ====		==== basic_simple ====
	This example demonstrates passing and failing tests using the primary POD types that infer status from (int~~, bool~~, short, and char)~~. The bool type is only accepted in C++ mode~~.		This example demonstrates passing and failing tests using the primary POD types that infer status from (int, short, and char).

	==== basic_fixtures ====		==== basic_fixtures ====

Ivailop: /* Introduction */

2009-09-30T23:46:52Z

Introduction

← Older revision		Revision as of 23:46, 30 September 2009
Line 1:		Line 1:
	== Introduction ==		== Introduction ==

	Function Lists are abbreviated as ''flist'' in both pragmas (as in [[scl_test_flist]]) and documentation. The Test flist Samples pertain to test units that contain lists of functions to be executed. The Test FList functionality is intended as a simple grouping of test functions and are designed to be used with the C language (although it is not restricted from compilation in a C++ environment as well). Test FLists does not support more advanced usages patterns like private test data. If you need more advanced functionality, consider using [[Test Class Samples\|Test Classes (c++)]] or [[Test CClass Samples\|Test C-Classes]].		Function Lists are abbreviated as ''flist'' in both pragmas (as in [[scl_test_flist]]) and documentation. The Test flist Samples pertain to test units that contain lists of functions to be executed. The Test FList functionality is intended as a simple grouping of test functions and are designed to be used with the C language (although it is not restricted from compilation in a C++ environment as well). Test FLists does not support more advanced usages patterns like private test data. If you need more advanced functionality, consider using [[Test Class Samples\|Test Classes (C++)]] or [[Test CClass Samples\|Test C-Classes]].

	== Tests Description ==		== Tests Description ==

Ivailop: /* Introduction */

2009-09-30T23:46:38Z

Introduction

← Older revision		Revision as of 23:46, 30 September 2009
Line 1:		Line 1:
	== Introduction ==		== Introduction ==

	Function Lists are abbreviated as ''flist'' in both pragmas (as in [[scl_test_flist]]) and documentation. The Test flist Samples pertain to test units that contain lists of functions to be executed. The Test FList functionality is intended as a simple grouping of test functions and are designed to be used with the C language (although it is not restricted from compilation in a C++ environment as well). Test FLists ~~require that all functions have c-linkage (extern "C") and~~ does not support more advanced usages patterns like private test data. If you need more advanced functionality, consider using [[Test Class Samples\|Test Classes (c++)]] or [[Test CClass Samples\|Test C-Classes]].		Function Lists are abbreviated as ''flist'' in both pragmas (as in [[scl_test_flist]]) and documentation. The Test flist Samples pertain to test units that contain lists of functions to be executed. The Test FList functionality is intended as a simple grouping of test functions and are designed to be used with the C language (although it is not restricted from compilation in a C++ environment as well). Test FLists does not support more advanced usages patterns like private test data. If you need more advanced functionality, consider using [[Test Class Samples\|Test Classes (c++)]] or [[Test CClass Samples\|Test C-Classes]].

	== Tests Description ==		== Tests Description ==