rspec

Comments and changes to this ticket

• 

  David Chelimsky May 28th, 2008 @ 06:47 AM

  The instructions at http://rspec.info/download.html say to read the wiki at github: http://github.com/dchelimsky/rsp...

  I just followed them and had no problem at all, so I'm not sure why you'd be having any trouble.

  In any case, a single download or gem are both interesting ideas.

• 

  Assaf Arkin May 28th, 2008 @ 07:22 AM

  There's a whole page dedicated to the Rails installation instructions over here:

  http://rspec.info/documentation/...

  Worth mentioning that I'm looking for a stable release, not running from edge.

  I noticed that once I removed the version check line, I go back to using the spec command, which I did before with 1.1.3.

  I use rake for running all specs, generating reports, pre-commit, etc, but never warmed up to its clunky interface when spec is just so more useful.

  So now that I'm actually running RSpec 1.1.4 (Gem not plugin) with the rspec-rails plugin, I think it should be in reverse: have rspec-rails included (or at least usable from) RSpec the Gem.

• 

  David Chelimsky May 28th, 2008 @ 07:40 AM

  • → Assigned user changed from “” to “David Chelimsky”

  D'oh - thought I removed that. I'll update soon.

  I added directions to http://github.com/dchelimsky/rsp... to get checkout a release rather than HEAD.

  If you've got the same release of the rspec gem as the installed plugin, you should be able to use the spec command. If not, grab both plugins and use script/spec as a fallback.

• 

  Assaf Arkin May 28th, 2008 @ 09:52 AM

  Second trick using checkout works, thanks.

  I'm not sure it will work cleanly if your Rails project is also under Git control, might need to follow with rm -rf .git just after checking out the plugin.

• 

  David Chelimsky May 28th, 2008 @ 02:51 PM

  • → Milestone changed from “No-Milestone-Assigned” to “1.1.5”
  • → State changed from “new” to “resolved”

  I updated the docs to suggest removing or ignoring the .git directories.

• 

  Assaf Arkin May 29th, 2008 @ 07:55 PM

  On Wed, May 28, 2008 at 5:52 AM, Lighthouse

  wrote:

  // Add your reply here

  This is still going to come back and bite us (well, me, at least) on the

  next upgrade. Upgrade the Gem, get the specs to fall with a meaningless

  error message, fish for where the upgrade (incorrectly worded as

  installation) instructions are, then remove the plugin and replace it with

  the new version.

  Which is why I listed this as feature request. The feature is to avoid the

  lengthy, error prone, process of what should be a simple upgrade.

• 

  Coda Hale August 1st, 2008 @ 04:59 AM

  • → Tag changed from “” to “featurerequest rspec_on_rails”

  I think Assaf is right. Upgrading the RSpec Rails plugin has always been a hassle, and it'd be nice to simplify things.

  As an example of what could be done, look at the HAML install process:

  gem install haml
  cd myrailsproject
  haml --rails .
  

  A skeleton plugin with a two-line init.rb file is generated in vendor/plugins, and you're off to the races. If HAML goes up a version, just gem install haml and the only thing you're responsible for is your own code.

• 

  Pat Maddox August 1st, 2008 @ 11:55 PM

  Hey Coda & Assaf,

  rspec-rails will be available as a gem as of 1.1.5. See http://rspec.lighthouseapp.com/p...

  In the mean time, you can check out the latest source tree and build rspec-rails yourself. From there, it's just

  cd myrailsproject
  ./script/generate rspec
  

  And you can let us know if the upgrade to 1.1.5 goes smoothly without any work on your part :)