Closed rouge8 closed 8 years ago
No it's not. I have a fix for it though and can create a 0.7.1 quick fix release for this.
0.7.1 should fix this for you. Thanks for reporting it!
Thanks for the super fast fix!
It does work, yes? (And you caught me in a slump while some deployments were finishing.)
Yup!
On Tuesday, June 14, 2016, Ian Cordasco notifications@github.com wrote:
It does work, yes? (And you caught me in a slump while some deployments were finishing.)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sigmavirus24/betamax/issues/108#issuecomment-226064970, or mute the thread https://github.com/notifications/unsubscribe/AAOdzZyHm04W1l0O98H4qtQMISD2KxQJks5qL1Z5gaJpZM4I1wp1 .
Config changes to
current_cassette
on thebetamax_recorder
pytest fixture persist between tests. I expected changes tobetamax_recorder.current_cassette
to behave like a pytest function-scoped fixture, wherebetamax_recorder
would be new and clean on each test.With betamax==0.7.0, pytest==2.9.2 and the following tests, whichever test runs second will fail:
Is this intended behavior?