No such file to load - spec/test/unit

Under the older version of rspec, I’m able to run my script successfully
by running “spec randomperform.rb”

I’ve now installed the newest rspec, and it does not work for me. If I
run the command:

rspec randomperform.rb

I get the following error:


internal:lib/rubygems/custom_require:29:in require': no such file to load -- spec/test/unit (LoadError) from <internal:lib/rubygems/custom_require>:29:inrequire’
from C:/watir-tests/craftfree/randomperform.rb:3:in <top (required)>' from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rspec-core-2.1.0/lib/rspec/core /configuration.rb:334:inload’
from
C:/Ruby192/lib/ruby/gems/1.9.1/gems/rspec-core-2.1.0/lib/rspec/core
/configuration.rb:334:in block in load_spec_files' from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rspec-core-2.1.0/lib/rspec/core /configuration.rb:334:inmap’
from
C:/Ruby192/lib/ruby/gems/1.9.1/gems/rspec-core-2.1.0/lib/rspec/core
/configuration.rb:334:in load_spec_files' from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rspec-core-2.1.0/lib/rspec/core /command_line.rb:18:inrun’
from
C:/Ruby192/lib/ruby/gems/1.9.1/gems/rspec-core-2.1.0/lib/rspec/core
/runner.rb:55:in run_in_process' from C:/Ruby192/lib/ruby/gems/1.9.1/gems/rspec-core-2.1.0/lib/rspec/core /runner.rb:46:inrun’
from
C:/Ruby192/lib/ruby/gems/1.9.1/gems/rspec-core-2.1.0/lib/rspec/core
/runner.rb:10:in `block in autorun’

Anyone know what is wrong? What am I missing? Sorry if this is a
“newb” question, as I’m still fairly new at Ruby and its various gems.

Thanks,
James

On Nov 25, 2010, at 11:44 AM, James Palmer wrote:


C:/Ruby192/lib/ruby/gems/1.9.1/gems/rspec-core-2.1.0/lib/rspec/core
from
Anyone know what is wrong? What am I missing? Sorry if this is a
“newb” question, as I’m still fairly new at Ruby and its various gems.

Thanks,
James

rspec-2 does not interoperate with the test/unit runner anymore, so
spec/test/unit was removed.

What is it you’re trying to do?

Thanks David,

I actually had a “require” statement in my code for Test Unit that
shouldn’t have been there - the problem appears to not have been rspec
related at all.

Thanks!
James