如何使用 RSpec 测试delayed_job回调钩子

发布于 2024-11-29 14:54:20 字数 766 浏览 1 评论 0原文

我想验证delayed_job回调钩子是否被调用，但我不知道如何让RSpec来做到这一点，特别是当涉及多层类时。

假设我有一个像这样的 ActiveRecord 模型：

class MyJob < ActiveRecord::Base
  def perform
    # do some stuff
  end
  def after(job)
    # called by delayed_job after perform completes
  end
end

概念上，我想要沿着这些线进行 RSpec 测试（尽管我知道这是不正确的）：

it 'should call the :after callback hook' do
  my_job = MyJob.create
  my_job.should_receive(:after).with(an_instance_of(Delayed::Backend::ActiveRecord::Job))

  Delayed::Job.enqueue(my_job)
  Delayed::Worker.new.work_off
end

我已经仔细研究了 stackoverflow、relishapp.com/rspec 和我能想到的所有其他地方。这不会太难吧？（我打赌@zetetic 在睡梦中就知道答案……；）

（注意：我的实际案例在 MyJob 和 DJ 之间使用了“shim”类。这个简单案例的答案可能会引发更复杂的后续问题！）

原文

I'd like to verify that delayed_job callback hooks are getting called, but I don't see how to get RSpec to do it, especially when several layers of classes are involved.

Assuming I have an ActiveRecord model like this:

class MyJob < ActiveRecord::Base
  def perform
    # do some stuff
  end
  def after(job)
    # called by delayed_job after perform completes
  end
end

Conceptually, I want an RSpec test along these lines (though I know this isn't correct):

it 'should call the :after callback hook' do
  my_job = MyJob.create
  my_job.should_receive(:after).with(an_instance_of(Delayed::Backend::ActiveRecord::Job))

  Delayed::Job.enqueue(my_job)
  Delayed::Worker.new.work_off
end

I've pored over stackoverflow, relishapp.com/rspec and all the other places I can think of. It can't be too hard, right? (I bet @zetetic knows the answer in his sleep... ;)

(Caveat: My actual case uses a 'shim' class between MyJob and DJ. An answer for this simple case may trigger a more complex follow-on!)

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

说谎友 2024-12-06 14:54:20

恕我直言，我认为这不是最好的做法...

通过这样做，您正在尝试规范 DelayedJob 的行为，而不是您的应用程序，并且 DJ 已经有了自己的测试套件。

不管怎样，嘲笑 DelayedJob 本身怎么样？也许您可以通过这样做指定您的 MockedJob 将在处理后调用您的钩子，并且您可以相应地创建匹配器/期望...

回复收藏 0 原文

﹉夏雨初晴づ 2024-12-06 14:54:20

我的建议是查看作业表是否创建了新的作业记录，然后内省该记录的详细信息。我过去用过类似的东西。

it "should sync content from the remote CMS" do      
  DelayedJobs::CMS::Sync.module_eval do
  def perform
    url.should == "http://example.com/tools/datafeed/resorts/all"
    Report.sync!([{'id' => 1, 'name' => 'resort foo'}])
  end
end

lambda do
  Report.sync_all!
end.should change(Delayed::Job, :count)

lambda do
  Delayed::Job.work_off
end.should change(Resort, :count).by(2)
end

My suggestion would be to see if the Jobs table creates a new job record, and then introspect the details of that record. I've used something like this in the past.

it "should sync content from the remote CMS" do      
  DelayedJobs::CMS::Sync.module_eval do
  def perform
    url.should == "http://example.com/tools/datafeed/resorts/all"
    Report.sync!([{'id' => 1, 'name' => 'resort foo'}])
  end
end

lambda do
  Report.sync_all!
end.should change(Delayed::Job, :count)

lambda do
  Delayed::Job.work_off
end.should change(Resort, :count).by(2)
end

回复收藏 0 原文

~没有更多了~