Testing is a build issue and a separate matter. In that case you want
to simulate the Ruby environment locally, so you would add lib/ to the
$LOAD_PATH in your *helper* script. Or on the command line of your
test runner. Eg.
$ testrb -Ilib test/**/*.rb
···
On Oct 20, 12:50 am, "Michael W. Ryder" <_mwry...@worldnet.att.net> wrote:
What would you suggest in the case of multiple versions of a module for
testing purposes? If everything is "hard coded" to go to a specific
directory than all versions would use the same code and defeat the
purpose of having the different versions.
Lol, I have no idea what to do anymore. Practical Ruby Gems decreased to $4
since I last logged onto Amazon, I think I'll push that purchase through and
defer to it's expertise.
···
On Wed, Oct 14, 2009 at 7:01 AM, Intransition <transfire@gmail.com> wrote:
* Don't mess with the $LOAD_PATH. PERIOD.
On Tue, Oct 20, 2009 at 9:01 PM, Intransition <transfire@gmail.com> wrote:
Testing is a build issue and a separate matter. In that case you want
to simulate the Ruby environment locally, so you would add lib/ to the
$LOAD_PATH in your *helper* script.