Testing Starling and Workling

Oh, I don’t care if emails go out either. I care that the erb in them is sane, and that no objects that nil that shouldn’t be nil…

I just realized in writing this that actually, you have to do something like I said, because I test if the emails go out by counting them with:


My experience was the workling calls didn’t cause any exceptions, so I

and I can easily do:

in my the daemon version of my workling. I invoke such a thing from my test case at the right time too:

in test_helper.rb I MOCK out the component that wants to talk to the DB directly:

class ActionController::IntegrationTest


Binary file ./ruby-on-rails/2009-06-09-testing_starling_and_workling.mkd matches