-
Notifications
You must be signed in to change notification settings - Fork 71
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
Make stub data accessible #44
Comments
Hi, Could you give a bit more specifics on the functionality you propose? Are you saying that you want the ability to use a different backend to the client? i.e., something like |
More simple, can I import for example, MockSolrResponse, https://github.com/andycasey/ads/blob/master/ads/tests/mocks.py#L50, and use for testing my app, rather than hitting the API. As far as I can tell, you can't access it when installed via pip atm:
|
To use If we want this feature to be user-facing, I think we can come up with a simpler API/workflow to implement that functionality, but I'd need to understand more details of those use cases. If its for developers, then I think adding it to the package-level Thoughts? |
I'm still split. I feel there will be some people who would want to work explicitly with the context-manager, and some people who want to treat it as a magic box, with a flag such as 'dry_run', without having to understand the underlying machinery. So, for now I'd just add the I'm open to other suggestions though, my feelings may be biased. |
This can be closed if #53 is merged. |
There are some stub data for both expected SolrQuery and MetricsQuery, in the repository. It'd be useful to have them accessible via the import.
eg.,
The context being that we have a lot of users testing on the API directly and hitting their API rate limit, rather than using the stub data you've got available in the package.
The text was updated successfully, but these errors were encountered: