There's still a very bizarre issue where `params` and `data` are both being populated with access tokens or whatever, where in the case of OAuth2 it should just be params. This only happens when it passes in something like: `{'params': {}, 'data': {}, 'headers': {}}`. The exact point at which this happens is in the fake_request method as the update over the params key is called, which should insert the fake access token. Prior to this invocation the `kwargs` are correct, afterwards both `params` and `data `keys are mysteriously updated. Fortunately this is just a very few test cases, but it's still annoying.