-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Sidekiq tries to run in test env #1907
Comments
Thanks, Mike! |
This is happening for me as well but I am not using Sidetiq. |
Post the backtrace.
|
I am realizing now that it is probably related to me doing something unconventional in that I am using the batch middleware in my tests. I am within a Sidekiq::Testing.fake! block though. Here is the backtrace nonetheless. I am able to get around this using this hack but I know that you don't recommend mocking Redis. Is there a way that I can avoid needing redis running to test this?
|
rspec-sidekiq has some Batch support, I think it mocks it out so you don't need redis? |
Hi All!
I have a very strange issue: Sidekiq tries to establish connection to Redis in test environment.
I'm using sidekiq 3.2.2 with rspec-sidekiq 2.0.0.beta on rails 4.1.4 with ruby 2.1.2
Here is my test
If I try to run
bundle exec rspec
with working redis, I'm getting pretty nice output:But if I try to run tests with stopped redis I'm getting this:
rails_helper.rb
I just have no idea why it happens.
Could you please help with that?
Many thanks.
The text was updated successfully, but these errors were encountered: