-
Notifications
You must be signed in to change notification settings - Fork 0
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
Test are failing #59
Comments
I never had such issues with the final version. What it indeed does is to replay the interaction for all further assertions. Meaning the first create is recorded and its assertion run, whereas all further assertions are then based on the recorded interaction and thus do not expect the Were there any changes regarding the |
Not that I know of. I also checked out your last commit. |
It looks like it just ignores the first recording, records a second time, and only matches requests on the third run. |
From my understanding it is very dependent on the record mode how the behavior is: There may also be side effects if some interactions already exists in a cassette or a parent cassette (which we don't use by exclude: true). To record new one must delete the files manually however. Maybe we can also set the recording flag on non-repeatable interactions explicitely. I still wonder how this worked for you. Did you only record with |
Tests are failing for me (especially Heroku for now).
It's pretty hard to debug this stuff ^^
@croeck Should the before block really be run before each of the included examples? How can this work? Shouldn't it return a
name is already taken
error at the second call (as it always does for me)? I don't fully understand the control flow I think. Should it replay the interaction on the second call?The text was updated successfully, but these errors were encountered: