Closed trandoanhung1991 closed 9 years ago
Does this same error happen if you use Sucker Punch without Activejob?
I haven't tried that yet. But so far my workaround works so I haven't the motivation to mess with it further.
How would I go about replicating a similar condition without using ActiveJob as the middleman?
Installing sucker punch per the readme and using the test helper to assert your job was run.
On Tuesday, August 25, 2015, Hung Tran notifications@github.com wrote:
I haven't tried that yet. But so far my workaround works so I haven't the motivation to mess with it further.
How would I go about replicating a similar condition without using ActiveJob as the middleman?
— Reply to this email directly or view it on GitHub https://github.com/brandonhilkert/sucker_punch/issues/124#issuecomment-134508846 .
_Build a Ruby Gem is available! http://brandonhilkert.com/books/build-a-ruby-gem/?utm_source=gmail-sig&utm_medium=email&utm_campaign=gmail_
I'm trying to use Sucker punch via Active Job for async devise mail deliveries. However, I'm having trouble testing due to this problem. FWIW, SP works fine, it's just the testing where it crashes.
rails_helper.rb
config/initializers/sucker_punch.rb
spec file
The only way I can get testing to work is to use Active Job's
:test
adapter via checkingRails.env.test?
in sucker_punch.rb