Displaying 20 results from an estimated 1100 matches similar to: "Having trouble installing the Rails plugin with Rspec 0.7.5"
2006 Dec 20
8
RSpec 0.7.5
The RSpec Development Team is pleased to announce the release of RSpec 0.7.5.
This release adds support for Heckle - Seattle''rb''s code mutation tool.
There are also several bug fixes to the RSpec core and the RSpec on
Rails plugin.
Changes: http://rspec.rubyforge.org/changes.html
Download: http://rubyforge.org/frs/?group_id=797
or
gem install rspec
Happy spec''ing,
2007 May 01
7
RSpec 0.9.1 released
The RSpec team is pleased to announce RSpec 0.9.1 (we skipped 0.9.0).
RSpec is a framework that provides programmers with a Domain Specific
Language to describe the behaviour of Ruby code with readable,
executable examples that guide you in the
design process and serve well as both documentation as tests.
This release includes a complete overhaul of the API, which can be
summarised as follows:
*
2007 Jan 13
2
svn reorganized?
It appears the repository has been rearranged when compared to the
documentation. For the Rails plugin, the correct script/plugin
install now seems to be:
script/plugin install svn://rubyforge.org/var/svn/rspec/trunk/
rspec_on_rails
Is this correct?
2007 Jan 19
3
problems updating to 0.7.5.1
Hi all
I''ve upgraded the rails plugin from 0.7.5 to 0.7.5.1 (plugin/remove
rspec_on_rails followed by :
ruby script/plugin install
svn://rubyforge.org/var/svn/rspec/tags/REL_0_7_5_1/rspec_on_rails/vendor/plugins/rspec_on_rails
I''ve also updated the rspec gem and removed the older version. I''m running
rubygems 0.9.1 on a windows box
however, when I try to run a spec
2006 Dec 25
1
Issues with 0.7.5
I installed 0.7.5 and the corresponding Rails plugin. Now it seems
that the rake command is:
rake spec:autotest
I immediately ran into several problems:
1. rspec_autotest.rb line 30 has curly quotes and makes Ruby choke
2. Same line, rails_spec is spelled solid, when it should have the
underscore
But fixing these didn''t get me back going. Now I have to have a
rails_spec_server
2006 Dec 20
16
Edge RSpec on Rails...what did I forget?
Started a new Rails project, and installed RSpec and the Rails plugin
vendor/plugins/rspec (svn://rubyforge.org/var/svn/rspec/trunk/rspec) - 1332
vendor/plugins/rspec_on_rails
(svn://rubyforge.org/var/svn/rspec/trunk/rspec_on_rails/vendor/plugins/rspec_on_rails)
- 1332
Generated the rspec file, created a model...the spec runs fine if I do
ruby spec/models/foo_spec.rb. Running rake though gives
2007 Feb 26
15
drbspec - "no server running"
At times I''ve gotten the message "No Server Running" from drbspec
with my rails app. The thing is, the drb server certainly is running!
This happened a few times with my model specs. I''m not sure exactly
what the problem was there - I believe I was loading up fixtures that
didn''t exist. I was calling fixtures :singular_table_name as opposed
to
2007 May 02
13
RSpec 0.8.2 pain, missing spec/rails?
Hi. I''m upgrading a project from an 0.8.0 pre-release gem to 0.8.2.
I''ve installed the 0.8.2 gem, and the rspec_on_rails 0.8.2 plugin:
ruby script/plugin install
svn://rubyforge.org/var/svn/rspec/tags/REL_0_8_2/rspec
When I try to run my specs though, I get the below error. It''s as if the
spec_helper cannot find "spec/rails". I''ve noticed that
2007 Sep 05
4
False Positives and Autotest on New Folders
False Positives
I just discovered how easy it was to create a false positive when I, trying
my first RSpec test, did this:
ob.should eql?(''foo'')
instead of:
ob.should eql(''foo'')
or:
ob.should == ''foo''
As far as I can see, this is roughly equivalent to:
ob.should false
Neither eql?(''foo'') nor false causes the spec
2007 Oct 11
2
Incompatibility Issues after updating CURRENT
Hi,
I''m using piston to manage rspec and rspec_on_rails in vendor/plugins.
----
~/work/simplify_md $ piston st vendor/plugins/
vendor/plugins/rspec
(svn://rubyforge.org/var/svn/rspec/tags/CURRENT/rspec)
vendor/plugins/rspec_on_rails
(svn://rubyforge.org/var/svn/rspec/tags/CURRENT/rspec_on_rails)
----
After I ''piston update''d rspec and
2007 Oct 23
6
Problem Upgrading from 1.0.5 to 1.0.8
Hey Guys,
I''m getting the following error:
1)
NameError in ''ProductsController with a GET to /products NO NAME
(Because of Error raised in matcher)''
uninitialized constant Spec::Mocks::BaseExpectation::AnyArgsConstraint
/Users/mattlins/Projects/RailsProjects/SWNetworkServices/vendor/plugins/rspec_on_rails/lib/spec/rails/dsl/behaviour/render_observer.rb:86:in
2007 Sep 27
2
1.0.8 tarball problem.
When I untar 1.0.8 after having downloaded it from rubyforge, I get
these errors:
<snip>
rspec-1.0.8/spec/spec/runner/spec_parser_spec.rb
rspec-1.0.8/spec/spec/spec_classes.rb
gzip: stdin: decompression OK, trailing garbage ignored
rspec-1.0.8/spec/spec/translator_spec.rb
rspec-1.0.8/spec/spec_helper.rb
rspec-1.0.8/UPGRADE
tar: Child returned status 2
tar: Error exit delayed from
2007 May 25
4
rspec on rails update question
I''m sure this is OT but I''d appreciate the help
I''m using rspec_on_rails
I prefer to use stable release rather than live dangerously (at least
until I can tell the difference between what I might be doing wrong
vs problems in rspec). However, I would like to try the
RspecScaffoldGenerator fix.
I installed (per the docs) last week with the following commands
2007 Feb 27
8
Using a subversion repository to spec in a rails app
Is it a bad practice to use a subversion repository to the trunk of
rspec and rspec_on_rails? Or rather, is it doomed to fail, since my
gem will always be out of date?
I know I can''t use spec, installed from gem,s if I have the latest
revision of rspec and rspec_on_rails checked into my plugins
directory. But I should still be able to use it with the --drb
option, correct?
2008 Mar 19
3
svn externals and git submodules
This is a request to split up the repository into at least two repositories
rspec
rspec_core (loaded as svn_external or git submodule)
rspec_on_rails (loaded as svn_external or git submodule)
We could load the plugins the same way as before
ruby script/plugin install http://rspec.rubyforge.org/svn/trunk/rspec_core
ruby script/plugin install
2007 Jun 08
4
Still recommend the plugins over the gems?
> We strongly recommend you install RSpec and Spec::Rails as plugins
> (as opposed to relying on an RSpec gem). See special instructions
> below if you want to install the HEAD of the trunk, or an older
> version.
(from http://rspec.rubyforge.org/documentation/rails/install.html)
Is this still the case? Why?
Is the rspec_on_rails available in gem form?
Does rspec_generator
2007 Apr 13
3
rspec on rails won''t install
Hi:
This command:
svn co svn://rubyforge.org/var/svn/rspec/tags/REL_0_9_0/rspec_on_rails/vendor/plugins/rspec_on_rail
Gives me this output:
svn: URL ''svn://rubyforge.org/var/svn/rspec/tags/REL_0_9_0/rspec_on_rails/vendor/plugins/rspec_on_rails''
doesn''t exist
If I go the ''script/plugin install'' route, I get "Export complete."
Anybody know
2007 Jan 03
0
0.7.5 Doesn''t Let My Tests Run
The tests are all running on 0.7.4. In installed 0.7.5 as follows:
- sudo gem install rspec
- script/plugin install svn://rubyforge.org/var/svn/rspec/tags/
REL_0_7_5_/vendor/rspec_on_rails/vendor/plugins/rspec
- script/generate rspec
ZenTest (3.4.1) is also installed.
Here is what happens when I run the same tests that ran on 0.7.4. (By
the way, Rails is build 5065). Any help is appreciated.
2007 Dec 28
3
Converting to Rails 2.0.2
I''m moving an older project to Rails 2.0.2 and ran into a roadblock on
the version matching. Here''s script/console session:
>> Spec::VERSION::REV
=> "1785"
>> Spec::Rails::VERSION::REV
NoMethodError: undefined method `run='' for Test::Unit:Module
from /Users/sxross/rails/tastie_work/vendor/plugins/rspec_on_rails/
lib/spec/rails.rb:16
from
2008 May 09
3
rspec version to use with git
I want to start using RSpec in an existing project that uses git for
SCM, and I was planning on using git submodules to pull in known-stable
releases of the rspec and rspec_on_rails plugins. The current
repositories on github don''t seem to be set up to help with this at the
moment though, so I''m looking for some advice. Here''re the issues, I
think:
* The last