Coupling - mock,stub

gistfile1.rb

class RequestsSchedule

  def fetch_all_expired
    # fetch and return all expired definitions from MongoDB
    # e.g. use MongoClient somehow  
  end
  
end

class RequestToQueuePusher

  QUEUE_NAME = 'requests'

  def enqueue(requests)
    each.requests { |r| enqueue_single(r) }
  end

  private

  def enqueue_singe(request)
    #locate messages queue
    # push request to queue    
  end

end

class SchedulerJob

  def run
    expired_requests = RequestSchedule.new.fetch_all_expired
    RequestToQueuePusher.new.enqueue(expired_requests)
  end
  
end 

Below is a StackOverflow comment where this gist was linked from.

Take a look at this example I created gist.github.com/anonymous/5101448. If I want to test SchedulerJob I need to stub RequestSchedule and mock RequestToQueuePusher right? Also what bothers me is that SchedulerJob is tightly coupled with two remaining classes. As I come from Java world, I'd normally extract them as dependencies as there is no easy way to fake objects which are created the hard-coded way. In Ruby it seems not to be an issue. I see a lot of object like my SchedulerJob. I know there is a way to fake them easily, but for me it violates some SOLID principles – grafthez Mar 6 '13 at 18:06