-
Notifications
You must be signed in to change notification settings - Fork 39
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
Testing multi-request flows and MockProvider #114
Comments
I have a few (late night thoughts) on how this could be fixed. We could replace the
and pass an instance of ResponseOverride in the init. Another approach we could take here is turn These are my 2 ideas for now. Totally open to suggestions/better ways to solve this problem. |
Made a simple change that solves this problem for now: #115 |
Hi!
I'm trying to test a flow where access tokens are refreshed(similar to #42 ), and I'm using a MockProvider instead of making actual network requests (imagine making a
MockProvider
where if a request is made with the old token, it'll return a "failed" json and if the request is made with a new token, you get the "success" json). However, since the request in theMockProvider
closure doesn't contain any information about the middleware, authentication etc, I can't check what token the request is made with.Any suggestions on how I can write a test for this? 🤔
The text was updated successfully, but these errors were encountered: