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.

Sign up for GitHub

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

Jump to bottom

"calls" constraint of mock in not always cleared before next test run #32

Closed

jvarlamova opened this issue Nov 22, 2019 · 0 comments

Labels

bug

jvarlamova commented Nov 22, 2019 •

edited

Loading

How to reproduce:

Execute test with mock with "calls" constraint

...
 mocks:
    someservice:
      strategy: uriVary
      uris:
         v1/test:
          calls: 1
          strategy: file
          filename: responses/test.json
...

After that run next test without mocks.
It will fail with error:

mock someservice: at path $.uriVary.v1/test: number of calls does not match: expected 1, actual 0

The text was updated successfully, but these errors were encountered:

luza added the bug label

fetinin added a commit to fetinin/gonkey that referenced this issue


          Reset mocks for each test (lamoda#32)

fd4bc30

luza pushed a commit that referenced this issue


          Reset mocks for each test (#32) (#36)

3fdeccf

jvarlamova closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment