You can monitor stubs execution to check against certain expectations, such as the number of calls to a given stub or stubs call sequence. Expectations should be defined inside the test cases and are verified just after the test case execution is finished. If the expectation is not met, then a suitable message is generated and output to the results. All expectations are removed at the end of test case execution after the outcome has been verified.
To configure stub expectations, the stub must have been created with one of the following dynamic stub configuration options enabled in the test configuration used to generate stubs:
See Dynamic Stubs Configuration for additional information. |
The following table describes the available expectation types:
Expectation | Description |
---|---|
CPPTEST_EXPECT_NCALLS(<func-id>, <value>) | The number of calls to the |
CPPTEST_EXPECT_NCALLS_MORE_THAN(<func-id>, <value>) | The number of calls to the |
CPPTEST_EXPECT_NCALLS_LESS_THAN(<func-id>, <value>) | The number of calls to the |
CPPTEST_EXPECT_NCALLS_IN_RANGE(<func-id>,<min>,<max>) | The number of calls to the |
CPPTEST_EXPECT_CALL_SEQUENCE() [Add<func-id>|AddNTimes<func-id>] | Specified the expected sequence for calls made to the stubs |
The following examples present typical ways to set stub definition expectations.
The API that sets expectations for the number of stub calls is the same for C and C++. |
Defining an expectation for the stub call sequence:
The following example sets expectations for a foo -> goo -> foo (3times) -> goo
stub call sequence:
[C] CPPTEST_EXPECT_CALL_SEQUENCE()->Add("foo")->Add(goo")->AddNTimes("foo", 3)->Add("goo"); [C++] CPPTEST_EXPECT_CALL_SEQUENCE().Add("foo").Add(goo").AddNTimes("foo", 3).Add("goo"); |
The defined expectation as shown in this example is violated in the following situations: