I had a similar issue recently. If you are using bundler and only specify
rspec-rails to load in the :test environment, i.e. not in the :development
environment, when you run rake rspec you will get no output. You must
specify rspec-rails in :test AND :development (it doesn' t load the whole
Resend from 10/29/2010 due to bounce back. This is in reference to an email
sent to the group on On Oct 18, 2010, at 1:24 AM.
Short version: The solution was indeed to downgrade to test-unit 1.2.3
gem 'test-unit', '1.2.3'
Longer version: I went through my github repository and found a version
Maybe you have syntax problems. can you do a ruby -c ? Anything in test.log?
On Oct 18, 2010 7:49 AM, "David Chelimsky" wrote:
On Oct 18, 2010, at 1:24 AM, Todd Sedano wrote:
>
> At one point, I had rspec working with my system...
$ spec -h
Usage: spec (FILE(:LINE)?|DIRECTORY|GLOB)+ [options]
On Oct 18, 2010, at 1:24 AM, Todd Sedano wrote:
> At one point, I had rspec working with my system and I've must have changed
> the configuration because now I don't see anything in the output using rspec
> 1.3.
>
> Just to be clear, I see nothing when I type
> spec spec
> rake spec
> bundle e
At one point, I had rspec working with my system and I've must have changed
the configuration because now I don't see anything in the output using rspec
1.3.
Just to be clear, I see nothing when I type
spec spec
rake spec
bundle exec spec spec
bundle exec rake spec
(or any of the above with a spec
