Require rspec-rails in Gemfile to fix 'spec' task (PR #857)

The rspec-rails gem was set to require = false a few days ago in b6bf95e7, which causes the spec rake task to silently fail. Notice that the latest Travis build is no longer running the specs.

This PR fixes the spec rake task.

GitHub

You’ve signed the CLA, chrishunt. Thank you! This pull request is ready for review.

good catch :+1:

note the change was made to speed up startup time, but was a tad to ambitious … I did not pick it cause I always use rake autospec

We could instead add an explicit spec task in lib/tasks/rspec.rake if you don’t want the autoload. Has the exact same result, but no change to the Gemfile. This might even be a bit better since the task will actually show up in rake -T

require 'rspec/core/rake_task'

RSpec::Core::RakeTask.new(:spec)

nice! I support that

On Sat, May 18, 2013 at 8:58 AM, Chris Hunt notifications@github.comwrote:

We could instead add an explicit rspec task in lib/tasks/rspec.rake if you don’t want the autoload. Has the exact same result, but no change to the Gemfile. This might even be a bit better since the task will actually show up in rake -T

require ‘rspec/core/rake_task’ RSpec::Core::RakeTask.new(:spec)

— Reply to this email directly or view it on GitHubhttps://github.com/discourse/discourse/pull/857#issuecomment-18090152 .