Introduce mockSequence and further simplify tests #569
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
|
LGTM. @wvanbergen ? |
|
Much nicer 👍 |
wvanbergen
added a commit
that referenced
this pull request
Nov 16, 2015
Introduce mockSequence and further simplify tests
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.
This PR introduces
mockSequenceresponse builder that is created of a sequence of (mock)responses and everytime whenMockBrokercalls itsFormethod it returns the next response from the sequence. When the last element in the sequence is reached it is returned for every subsequent call of theFormethod.This change allows to define
MockBrockerhandler withSetHandlerByMapexclusively, that makes tests a bit shorter and easier to read.