Test Point Sample: Difference between revisions

From STRIDE Wiki
Jump to navigation Jump to search
(New page: Category:Samples)
 
No edit summary
Line 1: Line 1:
=== StateController.c ===
This file impelements a simple state machine that we wish to test. The state machine runs in its own thread, and starts when the thread function *StateControllerTask* is executed.
=== SequenceTest.h ===
This file defines a class--SequenceTest--that is specified as a STRIDE test class using the *scl_test_class()* pragma.
SequenceTest derives from stride::srTest and thus inherits the test functionality implemented in this class.
=== SequenceTest.cpp ===
This file implements three tests of the state machine implemented in StateController.c. These tests demonstrate the use of the *srTestPointExpect()* macro to verify activity in another thread.
As the macro name suggests, we create an "expectation" of activity and then validate the observed activity against the expectation using rules that we specify. If the expectation is met, the test passes; if the expectation is not met, the test fails.
==== ExactTest ====
==== LooseTest ====
==== TimeoutTest ====
[[Category:Samples]]
[[Category:Samples]]

Revision as of 18:29, 25 March 2009

StateController.c

This file impelements a simple state machine that we wish to test. The state machine runs in its own thread, and starts when the thread function *StateControllerTask* is executed.

SequenceTest.h

This file defines a class--SequenceTest--that is specified as a STRIDE test class using the *scl_test_class()* pragma.

SequenceTest derives from stride::srTest and thus inherits the test functionality implemented in this class.

SequenceTest.cpp

This file implements three tests of the state machine implemented in StateController.c. These tests demonstrate the use of the *srTestPointExpect()* macro to verify activity in another thread.

As the macro name suggests, we create an "expectation" of activity and then validate the observed activity against the expectation using rules that we specify. If the expectation is met, the test passes; if the expectation is not met, the test fails.

ExactTest

LooseTest

TimeoutTest