You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
It was actually much simpler than that, just set RQ_CONNECTION_CLASS = 'fakeredis.FakeStrictRedis' when setting the config variables. The relevant sections are:
class Config:
APP_NAME = os.environ.get('APP_NAME')
RQ_CONNECTION_CLASS = 'fakeredis.FakeStrictRedis'
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.
Activity
jezdez commentedon Mar 26, 2018
There is a class attribute called connection_class that is used in the
RQ._connectmethod to create the Redis client. Since fakeredis supports the from_url API it should be enough to subclass theRQclass and overwriteconnection_classwith the dotted path to the fakeredis client class.moritz89 commentedon Mar 26, 2018
jezdez commentedon Mar 26, 2018
Would make sense to add a testing section to the docs. Mind opening a PR?
moritz89 commentedon Mar 27, 2018
Check that 👍🏼
moritz89 commentedon Mar 29, 2018
It was actually much simpler than that, just set
RQ_CONNECTION_CLASS = 'fakeredis.FakeStrictRedis'when setting the config variables. The relevant sections are: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
jezdez commentedon Sep 19, 2018
@moritz89 Yeah, adding something to docs/index.rst makes sense to me, as a "Testing" section?
moritz89 commentedon Sep 19, 2018