Scl test setup: Difference between revisions
Jump to navigation
Jump to search
(→Notes) |
|||
Line 22: | Line 22: | ||
== Notes == | == Notes == | ||
* This pragma identifies the setup fixture of an existing test unit, i.e. either a class with [[scl_test_class]] applied to it, or a function name with scl_test_flist applied to it. | * This pragma identifies the setup fixture of an existing test unit, i.e. either a class with [[scl_test_class]] applied to it, or a function name with [[scl_test_flist]] applied to it. | ||
* There may be only one setup fixture per test unit. | * There may be only one setup fixture per test unit. | ||
* The test unit name must match the class-name parameter of an [[scl_test_class|scl_test_class pragma]], or the test-unit-name parameter of an [[scl_test_flist|scl_test_flist pragma]] that has already been declared. | * The test unit name must match the class-name parameter of an [[scl_test_class|scl_test_class pragma]], or the test-unit-name parameter of an [[scl_test_flist|scl_test_flist pragma]] that has already been declared. |
Revision as of 20:32, 20 March 2009
The scl_test_setup pragma
The scl_test_setup pragma declares a member method to be a setup fixture for an existing test unit. The setup method will be called before the execution of each test method.
Syntax
#pragma scl_test_setup(test-unit-name, function-name)
Parameters | Type | Description |
test-unit-name | String | Name of a captured test unit. |
function-name | String | Name of a member function of the test unit to be used as a setup fixture. |
Notes
- This pragma identifies the setup fixture of an existing test unit, i.e. either a class with scl_test_class applied to it, or a function name with scl_test_flist applied to it.
- There may be only one setup fixture per test unit.
- The test unit name must match the class-name parameter of an scl_test_class pragma, or the test-unit-name parameter of an scl_test_flist pragma that has already been declared.
- This pragma can only work in STRIDE version 2.1 or later.
- The host PC must also have a recent distribution of ActiveState Perl installed.
Example
#include <srtest.h>
class RuntimeServices_fixtures {
public:
void setup (void)
{
srTestCaseAddComment(srTEST_CASE_DEFAULT, srNULL, "setup called");
}
void teardown (void)
{
srTestCaseAddComment(srTEST_CASE_DEFAULT, srNULL, "teardown called");
}
void tc_ExpectPass(void)
{
srTestCaseAddComment(srTEST_CASE_DEFAULT, srNULL, "this test should pass");
srTestCaseSetStatus(srTEST_CASE_DEFAULT, srTEST_PASS, 0);
}
void tc_ExpectFail(void)
{
srTestCaseAddComment(srTEST_CASE_DEFAULT, srNULL, "this test should fail");
srTestCaseSetStatus(srTEST_CASE_DEFAULT, srTEST_FAIL, 0);
}
};
#ifdef _SCL
#pragma scl_test_class(RuntimeServices_fixtures)
#pragma scl_test_setup(RuntimeServices_fixtures, setup)
#pragma scl_test_teardown(RuntimeServices_fixtures, teardown)
#endif
See Also
- Refer to the Test Units page for more information on capturing and qualifying test classes.