Fixes #2242 : Make exceptions for Inorder.verify more standard / spec… #2263
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.
…ific
*Adds NullInsteadOfMockException and NotAMockException checks to Inorder.verify() before checking if mocks were passed in during creation of Inorder
See #2242 for a description of the issue.
Inorder.verify(mock) now first checks if the passed argument is null, and if the mock is in fact a mock, and gives appropriate Exception messages, before checking if the passed in argument was passed during creation of Inorder object, and therefore giving a less specific error message.
Checklist
including project members to get a better picture of the change
commit is meaningful and help the people that will explore a change in 2 years
Fixes #<issue number>
in the description if relevantFixes #<issue number>
if relevant