RSpec called from Rake uses Rake's ARGV
Reported by Clifford Heath | January 24th, 2008 @ 10:17 PM
I'm using RSpec with rake, with specs in the "spec" directory,
and the SpecTask is called :test.
When I run "rake test", the ARGV from rake gets picked up by
the RSpec option parser, which adds it (in option_parser.rb:123)
to the @files list. That means that later, rspec decides that
there should be a directory called "test", and an exception is
thrown from spec/runner/options.rb:216, in files_to_load.
I don't know what the expected behaviour is here, but I know that
this isn't it! It seems that RSpec shouldn't be using ARGV here,
since rake, not rspec, is the main program.
Comments and changes to this ticket
-
James Baker August 7th, 2008 @ 07:54 PM
- → Tag cleared.
I had this happen to me as well in rspec 1.1.2. Upgrading rspec and rspeconrails to 1.1.4 (noticed I was out of date) fixed this for me.
-
Pat Maddox August 11th, 2008 @ 09:21 PM
- → State changed from “new” to “resolved”
I'm going to assume this is resolved then.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Behaviour Driven Development for Ruby.
