Comments on: Firing Rails Controller Actions from Command line (console)

By: science

science — Sun, 06 Apr 2008 06:49:36 +0000

An interesting alternative to this technique is blogged here: http://snippets.dzone.com/posts/show/600

By: science

science — Wed, 12 Dec 2007 07:16:08 +0000

Word to the wise: you may get weird errors if you use this line when running integration tests (i.e. when RAILS_ENV != ‘production’)


require 'action_controller/integration'

So it’s better (though fugly) to use something like:


require 'action_controller/integration' unless (RAILS_ENV != 'production')

Basically, from what I can tell, Rails is re-entrantly calling development mode and then test mode, for purposes of parsing rb files. So if you prevent this require statement from being called in dev or test mode, then you don’t get the collision with action_controller/integration. If I knew enough about this part of Rails, I’d submit a patch - anyone with ideas - post them here!

By: olddog

olddog — Wed, 28 Nov 2007 19:46:30 +0000

GRREAT post , exactly what I needed.

By: science

science — Tue, 09 Oct 2007 19:25:57 +0000

Also noticed recently that if you want to get access to the html body of an action in a test environment (a functional test, that is), the code you could use is:

html_response = @response.body