What's the best way to test delayed_job chains with rSpec?

Question

Currently when I have a delayed method in my code like the following:

CommentMailer.delay.deliver_comments(@comment, true)

I write something like this in my spec:

dj = mock("DelayProxy")
CommentMailer.should_receive(:delay).and_return(dj)
dj.should_receive(:deliver_comments).with(comment, true)

Is there a better way to handle this and/or chained methods like that in rSpec in general?

Anh Nguyen · Answer 1 · 2013-07-01T12:00:27.163

27

We can just have one more line in the before block as following:

CommentMailer.stub(:delay).and_return(CommentMailer)

Then you then can have the normal mock check as following:

CommentMailer.should_receive(:deliver_comments).with(comment, true)

edited Jul 01 '13 at 12:00

answered Apr 16 '12 at 07:17

Anh Nguyen

1,202
14
17

Using `stub` from rspec-mocks' old `:should` syntax without explicitly enabling the syntax is deprecated in rspec-3. This seems to work `expect(CommentMailer).to receive(:delay).and_return(CommentMailer)`. If you dont want to explicitly test it, you could use `allow` instead of `expect`. – Pete Jan 29 '16 at 19:09

score 2 · Accepted Answer · edited May 23 '17 at 10:31

2

Here are some discussions about chaining methods in rSpec that I found helpful:

Stubbing Chained Methods with Rspec

http://groups.google.com/group/rspec/browse_thread/thread/6b8394836d2390b0#

edited May 23 '17 at 10:31

Community

1
1

answered Sep 20 '11 at 21:32

Jared

2,885
2
28
31

score 1 · Answer 3 · answered Jul 14 '17 at 07:41

describe '#perform' do
    subject do
      Delayed::Worker.delay_jobs = false
      proc { worker.perform() }
    end

    it { is_expected.to change { ActionMailer::Base.deliveries.length }.by(2) }
  end

Set delayed job as false and u can test it like simple

What's the best way to test delayed_job chains with rSpec?

3 Answers3

Linked