similar to: rspec-core-2.6.1 is released!

I am working on a Rails 3 application. Recently bundler got an update for rspec, which upgraded it to 22, (previously we were using beta 20). After the update we are unable to run the old using ''rake spec:rcov'', while running with ''rake spec'' is running fine. When you do rake spec it does not give any output and finishes the task. something like below : $ rake

I saw the RCov page at http://rspec.rubyforge.org/tools/rcov.html and decided to add it to my project. My rakefile looks like this: require "rake" require "spec/rake/spectask" desc "Run all specs with RCov" Spec::Rake::SpecTask.new("spec:rcov") do |t| t.spec_files = FileList["spec/**/*_spec.rb"] t.rcov = true end When I run rake spec:rcov,

At work we''ve got a rather complex app with both specs and tests. Our default rake task runs all our our tests and specs. We''ve also got separate rake tasks to run groups of tests and specs in the various subdirectories. The default task simply lists all the individual tasks as pre-reqs. We do a lot of branching and merging, so we really want to run all of the tests and specs

Hi, Running: Ruby 1.8.7 p72, RSpec 1.1.12 and rcov 0.8.1.2.0, I get the following error message with $ rake spec:rcov -- /usr/local/ruby1.8.7//lib/ruby/1.8/rexml/formatters/pretty.rb:131:in `[]'': no implicit conversion from nil to integer (TypeError) from /usr/local/ruby1.8.7//lib/ruby/1.8/rexml/formatters/pretty.rb:131:in `wrap'' from

Hi all - I''ve applied (to trunk) Bob Cotton''s patch which supports shared behaviours (link to tracker below). I''m still toying w/ names, so please be aware that until this is released w/ 0.9 it should be considered experimental and there will NOT be translation support for it. It will definitely be included in some form - just the names (specifically

rspec version 1.2.0 has been released! Behaviour Driven Development for Ruby. Changes: ### Version 1.2.0 WARNINGS: * If you use the ruby command to run specs instead of the spec command, you''ll need to require ''spec/autorun'' or they won''t run. This won''t affect you if you use the spec command or the Spec::Rake::SpecTask that ships with

I have some specs tucked away inside my vendor/plugins directory that I want to run when I run rake spec. I''ve got the rake task working just fine, but for some reason rcov seems to choke when I try to tweak the included/excluded files to ignore any files in app/ but to include files in vendor/plugins/ plugin/app/** The error I get is this: No file to analyze was found. All the

Hi all, I appreciate that this is not an RSpec question, but I wondered if anyone out there can offer some pointers. We''re using the latest versions of RSpec and RCov, and ruby --version says this (on the Ubuntu build server): ruby 1.8.6 (2008-07-17 patchlevel 279) [x86_64-linux] We''re getting intermittent (yes, intermittent!) segfaults from the build when running

I am attending a training course covering rspec. I am using a MS WinXPpro SP3 machine. I have installed the cygwin environment. I am using git 1.5.4. I am using ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32] and rails 2.0.2 (albeit rails 2.1.0 is installed as well) I had to install rspec-rails and rspec via git and as a gem. Problem 1. If one goes to the rspec.info website and links

I have a Gem on which the testing is done with RSpec. I would like to include the results of RSpec and the RCov html files in the RDoc. The problem is that when I have RDoc include the files, it winds up escaping all the html. Is there a way to get HTML into RDoc unprocessed? Or is there some other way I can distribute the RSpec/RCov results with my Gem integrated with RDoc? I can include

Hey, I updated some Gems and now rspec seems to be broken. The weird thing is it fails because of Test::Unit which doesnt make much sense to me. /Users/username/.rvm/gems/ruby-1.9.2-p290@ror_project/gems/rack-1.3.4/lib/rack/backports/uri/common_192.rb:53: warning: already initialized constant WFKV_ /Users/username/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/test/unit/testcase.rb:9:in

This is by no means official yet, but I put together a proof-of-concept svn-to-git conversion of the NUT source tree: https://github.com/clepple/nut If you are interested in experimenting with the repository, feel free to clone it, but if we identify any problems with the Git import from SVN, be forewarned that I might blow away this repository and start over. In particular, I guessed at some

Greetings, I''m using rspec with rcov for my applications and there is one issue which I cannot solve nor can find any proper information regarding it: specing what is in a rescue block in case of an exception. I''m using Ruby on Rails and I usually make use of exceptions in my controllers, like the following example: def action @foo = Foo.find(1)

This applies to anyone using rspec''s trunk from >= 3220 with ZenTest <= 3.7.2. Anyone else, feel free to move on.... The next release of ZenTest, coming soon, includes some changes that improve the relationship between Autotest, it''s subclasses (like those in rspec) and .autotest, the file that you can use to plug into autotest''s hooks to extend/modify

Hi guys, I''m having some trouble with RSpec on Rails. Specifically, whenever I run the specs separately they''re fine: spec spec/controllers/*.rb spec spec/models/*.rb Or if I run them with TextMate..., but whenever I use the RCov Rake task from the RSpec page (or if I run all the specs together) I get failures: rake rcov spec spec/*/*.rb spec spec/models/*.rb

Hello again :) I''m trying to run rcov on my specs here but i''m getting a lot of segmentation faults (and they usually happen at different places): /home/mauricio/NetBeansProjects/reeds/vendor/rails/activerecord/lib/active_record/attribute_methods.rb:211: [BUG] Segmentation fault ruby 1.8.6 (2007-09-24) [i486-linux]

Hi all, For those of you checking out the Rails 2.0 preview release: RSpec-1.0.8 does not support Rails 2.0. Unfortunately, we''re in the middle of some big changes to the internals in trunk and won''t be in a position to do a release for another week or so. Therefore, if you are using the Rails 2.0 preview, you''ll need to use the RSpec trunk. Additionally, right now

Hi all, We''ve moved the rspec website to http://rspec.info. We want http://rspec.org, of course, but someone is squatting on and has yet to respond to my email :( The 1.1.0 docs are there. The 1.0.8 docs are still at http://rspec.rubyforge.org for the time being. We''ll be archiving them at the new site soon. This new site is hosted on our shiny new sponsored slice at Engine

Howdy, I have emailed before about the inconsistencies I''m spotting when using named routes/resource, but I think I''ve narrowed down the issue. It would seem this has nothing to do with rspec per se, but more with how routing works with rails. If you have an object instance, that isn''t saved and you attempt to generate a path for that item, even though the item may

Is there an easy way to use rcov to show my code coverage with RSpec in a rails project? Scott