is Google's (unit) testing and mocking framework for C++ tests.
| gmock_output_test_golden.txt (googletest-release-1.10.0) | : | gmock_output_test_golden.txt (googletest-release-1.11.0) |
|---|
| | |
| skipping to change at line 78 | | skipping to change at line 78 |
|---|
| Function call: Bar3(0, 1) | | Function call: Bar3(0, 1) |
| Expected: to be called once | | Expected: to be called once |
| Actual: called twice - over-saturated and active | | Actual: called twice - over-saturated and active |
| [ FAILED ] GMockOutputTest.ExcessiveCallToVoidFunction | | [ FAILED ] GMockOutputTest.ExcessiveCallToVoidFunction |
| [ RUN ] GMockOutputTest.UninterestingCall | | [ RUN ] GMockOutputTest.UninterestingCall |
| | |
| GMOCK WARNING: | | GMOCK WARNING: |
| Uninteresting mock function call - returning default value. | | Uninteresting mock function call - returning default value. |
| Function call: Bar2(0, 1) | | Function call: Bar2(0, 1) |
| Returns: false | | Returns: false |
|
| NOTE: You can safely ignore the above warning unless this call should not happen
. Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to en
force the call. See https://github.com/google/googletest/blob/master/googlemock
/docs/cook_book.md#knowing-when-to-expect for details. | | NOTE: You can safely ignore the above warning unless this call should not happen
. Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to en
force the call. See https://github.com/google/googletest/blob/master/docs/gmock
_cook_book.md#knowing-when-to-expect for details. |
| [ OK ] GMockOutputTest.UninterestingCall | | [ OK ] GMockOutputTest.UninterestingCall |
| [ RUN ] GMockOutputTest.UninterestingCallToVoidFunction | | [ RUN ] GMockOutputTest.UninterestingCallToVoidFunction |
| | |
| GMOCK WARNING: | | GMOCK WARNING: |
| Uninteresting mock function call - returning directly. | | Uninteresting mock function call - returning directly. |
| Function call: Bar3(0, 1) | | Function call: Bar3(0, 1) |
|
| NOTE: You can safely ignore the above warning unless this call should not happen
. Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to en
force the call. See https://github.com/google/googletest/blob/master/googlemock
/docs/cook_book.md#knowing-when-to-expect for details. | | NOTE: You can safely ignore the above warning unless this call should not happen
. Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to en
force the call. See https://github.com/google/googletest/blob/master/docs/gmock
_cook_book.md#knowing-when-to-expect for details. |
| [ OK ] GMockOutputTest.UninterestingCallToVoidFunction | | [ OK ] GMockOutputTest.UninterestingCallToVoidFunction |
| [ RUN ] GMockOutputTest.RetiredExpectation | | [ RUN ] GMockOutputTest.RetiredExpectation |
| unknown file: Failure | | unknown file: Failure |
| | |
| Unexpected mock function call - returning default value. | | Unexpected mock function call - returning default value. |
| Function call: Bar2(1, 1) | | Function call: Bar2(1, 1) |
| Returns: false | | Returns: false |
| Google Mock tried the following 2 expectations, but none matched: | | Google Mock tried the following 2 expectations, but none matched: |
| | |
| FILE:#: tried expectation #0: EXPECT_CALL(foo_, Bar2(_, _))... | | FILE:#: tried expectation #0: EXPECT_CALL(foo_, Bar2(_, _))... |
| | |
| skipping to change at line 269 | | skipping to change at line 269 |
|---|
| Expected: to be called once | | Expected: to be called once |
| Actual: called twice - over-saturated and active | | Actual: called twice - over-saturated and active |
| [ FAILED ] GMockOutputTest.ExcessiveCallWithDefaultAction | | [ FAILED ] GMockOutputTest.ExcessiveCallWithDefaultAction |
| [ RUN ] GMockOutputTest.UninterestingCallWithDefaultAction | | [ RUN ] GMockOutputTest.UninterestingCallWithDefaultAction |
| | |
| GMOCK WARNING: | | GMOCK WARNING: |
| Uninteresting mock function call - taking default action specified at: | | Uninteresting mock function call - taking default action specified at: |
| FILE:#: | | FILE:#: |
| Function call: Bar2(2, 2) | | Function call: Bar2(2, 2) |
| Returns: true | | Returns: true |
|
| NOTE: You can safely ignore the above warning unless this call should not happen
. Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to en
force the call. See https://github.com/google/googletest/blob/master/googlemock
/docs/cook_book.md#knowing-when-to-expect for details. | | NOTE: You can safely ignore the above warning unless this call should not happen
. Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to en
force the call. See https://github.com/google/googletest/blob/master/docs/gmock
_cook_book.md#knowing-when-to-expect for details. |
| | |
| GMOCK WARNING: | | GMOCK WARNING: |
| Uninteresting mock function call - taking default action specified at: | | Uninteresting mock function call - taking default action specified at: |
| FILE:#: | | FILE:#: |
| Function call: Bar2(1, 1) | | Function call: Bar2(1, 1) |
| Returns: false | | Returns: false |
|
| NOTE: You can safely ignore the above warning unless this call should not happen
. Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to en
force the call. See https://github.com/google/googletest/blob/master/googlemock
/docs/cook_book.md#knowing-when-to-expect for details. | | NOTE: You can safely ignore the above warning unless this call should not happen
. Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to en
force the call. See https://github.com/google/googletest/blob/master/docs/gmock
_cook_book.md#knowing-when-to-expect for details. |
| [ OK ] GMockOutputTest.UninterestingCallWithDefaultAction | | [ OK ] GMockOutputTest.UninterestingCallWithDefaultAction |
| [ RUN ] GMockOutputTest.ExplicitActionsRunOutWithDefaultAction | | [ RUN ] GMockOutputTest.ExplicitActionsRunOutWithDefaultAction |
| | |
| GMOCK WARNING: | | GMOCK WARNING: |
| FILE:#: Too few actions specified in EXPECT_CALL(foo_, Bar2(_, _))... | | FILE:#: Too few actions specified in EXPECT_CALL(foo_, Bar2(_, _))... |
| Expected to be called twice, but has only 1 WillOnce(). | | Expected to be called twice, but has only 1 WillOnce(). |
| GMOCK WARNING: | | GMOCK WARNING: |
| FILE:#: Actions ran out in EXPECT_CALL(foo_, Bar2(_, _))... | | FILE:#: Actions ran out in EXPECT_CALL(foo_, Bar2(_, _))... |
| Called 2 times, but only 1 WillOnce() is specified - taking default action speci
fied at: | | Called 2 times, but only 1 WillOnce() is specified - taking default action speci
fied at: |
| FILE:#: | | FILE:#: |
| | |
| skipping to change at line 316 | | skipping to change at line 316 |
|---|
| [ FAILED ] GMockOutputTest.MismatchArguments | | [ FAILED ] GMockOutputTest.MismatchArguments |
| [ FAILED ] GMockOutputTest.MismatchWith | | [ FAILED ] GMockOutputTest.MismatchWith |
| [ FAILED ] GMockOutputTest.MismatchArgumentsAndWith | | [ FAILED ] GMockOutputTest.MismatchArgumentsAndWith |
| [ FAILED ] GMockOutputTest.UnexpectedCallWithDefaultAction | | [ FAILED ] GMockOutputTest.UnexpectedCallWithDefaultAction |
| [ FAILED ] GMockOutputTest.ExcessiveCallWithDefaultAction | | [ FAILED ] GMockOutputTest.ExcessiveCallWithDefaultAction |
| [ FAILED ] GMockOutputTest.PrintsMatcher | | [ FAILED ] GMockOutputTest.PrintsMatcher |
| | |
| FILE:#: ERROR: this mock object should be deleted but never is. Its address is @
0x#. | | FILE:#: ERROR: this mock object should be deleted but never is. Its address is @
0x#. |
| FILE:#: ERROR: this mock object should be deleted but never is. Its address is @
0x#. | | FILE:#: ERROR: this mock object should be deleted but never is. Its address is @
0x#. |
| FILE:#: ERROR: this mock object should be deleted but never is. Its address is @
0x#. | | FILE:#: ERROR: this mock object should be deleted but never is. Its address is @
0x#. |
|
| ERROR: 3 leaked mock objects found at program exit. Expectations on a mock objec
t is verified when the object is destructed. Leaking a mock means that its expec
tations aren't verified, which is usually a test bug. If you really intend to le
ak a mock, you can suppress this error using testing::Mock::AllowLeak(mock_objec
t), or you may use a fake or stub instead of a mock. | | ERROR: 3 leaked mock objects found at program exit. Expectations on a mock objec
t are verified when the object is destructed. Leaking a mock means that its expe
ctations aren't verified, which is usually a test bug. If you really intend to l
eak a mock, you can suppress this error using testing::Mock::AllowLeak(mock_obje
ct), or you may use a fake or stub instead of a mock. |
| | | |
| End of changes. 5 change blocks. |
|---|
| 4 lines changed or deleted | | 4 lines changed or added |
|---|
"Fossies" - the Fresh Open Source Software Archive 