Case when Sidekiq::Testing is disabled about rspec-sidekiq HOT 3 CLOSED

Hi there. OK, so your calling Sidekiq::Testing.disable! so you may test against an actual instance of Redis? Your right in that the matcher doesn't cater for that, but your Gist appears to be doing the correct logic to test that scenario.

Your code looks good, would you be willing to start a pull request with that change? I'd like to roll that into the matcher as I can see it being useful for others.

from rspec-sidekiq.

There is one thing to consider. When the job is enqueued with perform_at method the job will be enqueued in the schedule queue. The way to inspect this queue is to simply: ::Sidekiq::ScheduledSet.new.map(&:item). I thought about appending those items to the @actual in the have_enqueued_job matcher. But that would make the corresponding spec file more complicated. So either we refactor the spec file or we add another matcher named have_scheduled_job or something similar.

from rspec-sidekiq.

I like the idea of a have_scheduled_job matcher alongside the have_enqueued_job. They are separate enough to warrant a separate matcher and indeed would make for simpler specs. Will have to weight this up against an alternative syntax such as have_enqueued_job#at

from rspec-sidekiq.