Merge rspec_on_rails and rspec plugins
Reported by Brian Takita | December 31st, 2007 @ 10:35 AM
There are complaints that the rspec on rails plugin install is too complicated.
The install can be simplified by requiring only one plugin, rather than two plugins, to be installed.
Comments and changes to this ticket
-
-
David Chelimsky January 2nd, 2008 @ 04:43 AM
- → State changed from “new” to “open”
Brian - how do you propose we do this without merging the separate development trees into one? I'm open to the idea of a single download, but not merging the devel trees to do so.
-
Brian Takita May 22nd, 2008 @ 09:57 AM
There are a couple of options.
One is we have a git external or piston to rspec inside of rspec-rails. Something like:
rspec-rails/
core/
lib/
We can then add core/ onto the load path when spec/rails is loaded.
-
Pat Maddox May 22nd, 2008 @ 07:06 PM
script/plugin install blahblah/rspec enter
up arrow
-rails enter
Too complicated? Really?
fwiw I think a better approach would be to use a gem, and then obv rspec-rails would depend on rspec. Not sure how easy that would be to do though.
-
Brian Takita May 23rd, 2008 @ 11:56 PM
Too complicated may be too extreme :)
Anyways, I (personally) think that having two plugins is not ideal.
It complicates management because the user needs to update two plugins instead of one.
Its one less thing for the user to think about.
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.
Jorge Pedroso