-
Notifications
You must be signed in to change notification settings - Fork 48
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
Add a testing option to use fakeredis #55
Comments
There is a class attribute called connection_class that is used in the |
Would it make sense to add example code somewhere? Or is there a blog or repo that can be used as an example?
… On 26. Mar 2018, at 09:11, Jannis Leidel ***@***.***> wrote:
There is a class attribute called connection_class that is used in the RQ._connect method to create the Redis client. Since fakeredis supports the from_url API it should be enough to subclass the RQ class and overwrite connection_class with the dotted path to the fakeredis client class.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Would make sense to add a testing section to the docs. Mind opening a PR? |
Check that 👍🏼 |
It was actually much simpler than that, just set
Where and how would it make sense to add the documentation? I would add a section in https://github.com/rq/Flask-RQ2/blob/master/docs/index.rst |
@moritz89 Yeah, adding something to docs/index.rst makes sense to me, as a "Testing" section? |
Totally forgot about it. I’ll send you an MR by the end of next week.
… On 19. Sep 2018, at 10:25, Jannis Leidel ***@***.***> wrote:
@moritz89 Yeah, adding something to docs/index.rst makes sense to me, as a "Testing" section?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
When writing unit tests it would be useful to have an option to use fakeredis instead of a real redis server. Are there any accepted methods that I am missing or would it make sense to integrate it directly into this library?
One approach is described by python-rq but I am not sure how to best integrate it.
For context, I am using Flask-base and would like to test the registration aspect, which creates a queue event but fails since there is no running redis server.
The text was updated successfully, but these errors were encountered: