Allow dredd command customization

[gonzalo-bulnes]

Allow dredd command customization

[gonzalo-bulnes]

Oh, of course, config.dredd_command would be just fine.

The primary goal of Dredd::Rack is allowing Dredd to be used with the usual Ruby testing tools (Factory Girl in the first place). We're not there yet, but integrating the Dredd hooks support is the first concrete step towards that goal. As I see it, once that done, integrating with Factory Girl & Co should be relatively straightforward. (We can discuss about that in an independent issue.)

Back to the topic: I'll try to implement this feature as soon as I can - I'll stick to the API we defined - meanwhile, if you want to give ot a try, feel welcome to PR (no pressure) : )

[gonzalo-bulnes]

Hi @gottfrois,

The v0.9.0 release ships the new dredd_command option. : )

[gonzalo-bulnes]

Hi @gottfrois,

It makes a lot of sense. I'm thinking aloud, but I believe that could be a configuration option, something like:

Dredd::Rack.configure do |config|
  config.app = Example::Application
  config.dredd_executable = 'dredd' # or whatever String makes sense in your context
end

What do you think? Any better idea for the dredd_executable option name?
The Dredd::Rack::RakeTask#dredd_available method could be adapted to use the same configuration option.

I'm currently focused on adding support for hooks (using DreddHooks), but if you help me defining a reasonable API for this feature, I think the change is useful and small enough to be worth sneaking it in.

[gottfrois]

Looks great or simply config.dredd_command.

+1 for dredd hooks. I tried to figure out how to use them but no luck :( Ideally I would like to be able to use my factories (factory girl) inside dredd hooks, not sure "how" dredd can load the hooks + the rails env though :-/