Hydra should allow setting up the Ruby load path

[brynary]

When running Test::Unit tests, it is convention to have the test/ directory in the Ruby load path, and when running RSpec tests it's convention to have spec/ in the load path.

I think Hydra's TestTask should support a "libs" option that mirrors Ruby's TestTask "libs" and sets up the load path.

[ngauthier]

Sounds good.

I was also thinking about have a "preload" option where you can have it load your test/spec helper. Then in the helper you can modify your load path.

Also, we could just have hydra add the common load paths for test files by default (it already does this with cucumber).

[rodreegez]

I think it would be worth making Hydra behave like Test::Unit does in this respect (I actually tried that right off the bat).Unless this affect Hydra's interoperability with other testing frameworks?

For me, not having test/ loaded is the only niggle in an otherwise brilliant tool.

[ngauthier]

Yeah I was thinking about including test and spec in the load path. The only possible gotcha is that cucumber likes to include lots of stuff for you. Hopefully it won't get in the way.

[adamfortuna]

+1 for this one. Setting it up as an option in the task or specifically including it would both help. Trying to get a workaround for including test/ in the load path myself -- any quick workaround to include it without branching?

[ngauthier]

@adam yeah just set your load path. Maybe you could put this in the rakefile:

$: << File.join(Rails.root, 'test') if Rails.env == 'test'

[rodreegez]

That is exactly how I've been getting around it. Not exactly pretty, but it does work.

[ngauthier]

There is also an undocumented feature:

https://github.com/ngauthier/hydra/blob/master/lib/hydra/worker.rb#L32

You could put:

$: << 'test'

into the file hydra_worker_init.rb, which is loaded when each worker boots up (so this will work remotely too).

[adamfortuna]

Awesome, thanks! The hydra_worker_init.rb hack worked to get things running smoothly.