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
I run rspec with spring rspec and I have to restart spring every time in order to get jobs placed on queues, which obviously defeats the purpose of using spring.
I have a test that places an job on a queue and then checks that the queue size equals 1. This works fine when I run rspec and also the first time I run spring rspec. Every subsequent time I run spring rspec, the queue size is always 0 no matter how many jobs I place on it. There are no errors.
This happens whether I run ResqueSpec.reset! or not. It seems that when using spring, ResqueSpec is in some sort of unusable state when the test suite finishes.
The text was updated successfully, but these errors were encountered:
I run rspec with
spring rspec
and I have to restart spring every time in order to get jobs placed on queues, which obviously defeats the purpose of using spring.I have a test that places an job on a queue and then checks that the queue size equals 1. This works fine when I run
rspec
and also the first time I runspring rspec
. Every subsequent time I runspring rspec
, the queue size is always 0 no matter how many jobs I place on it. There are no errors.This happens whether I run
ResqueSpec.reset!
or not. It seems that when using spring, ResqueSpec is in some sort of unusable state when the test suite finishes.The text was updated successfully, but these errors were encountered: