Fix Signal unit test undefined behavior (gmock)
#1184
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The original `EXPECT_CALL` already has an implicit `Times(1)`, so there is no need for a second `EXPECT_CALL` with an explicit `Times(0)`. This also removes an `EXPECT_CALL` after a call to a mock handler, which would be undefined behavior. Thus this removes the undefined behavior.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1159
Remove redundant
EXPECT_CALL. The implicitTimes(1)makes the call withTimes(0)redundant.Removing the redundant call removes undefined behavior caused by setting an expectation after a call to the mock handler.
Split up the unit tests so there is only one expectation per test.