Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can MatchExpectationsInOrder be modified after some expectations have been already set? #60

Closed
AA33 opened this issue Dec 2, 2016 · 1 comment

Comments

@AA33
Copy link

AA33 commented Dec 2, 2016

How does this method affect expectation matching? There could be two ways it could work:

  • Allow random order on all expectations set before or after calling this method.
  • Allow random order on expectations set after calling this method while expectations set before calling this method are expected to be in order.

Which of the above (or some other logic) is the current functionality? The documentation seems to have skipped over this.

@l3pp4rd
Copy link
Member

l3pp4rd commented Dec 2, 2016

yes probably will need to document it in more detail. it is affected right after you set it.

  • given you have a list of expectations, MatchExpectationsInOrder is true
  • when execute few queries in expected order
  • and you change MatchExpectationsInOrder to false
  • the rest of unfulfilled expectations can be matched in any order

At least I think it should act this way from looking into the source code..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants