similar to: RSpec 0.9.3

RSpec 0.9.4 has just been released. Gems haven''t rsync''ed around the globe yet, so you might have to wait a few hours to install it. The big news this time is Spec::Ui 0.2.0, which has been released along with RSpec core. This RSpec extension gives you custom Watir matchers (custom Selenium-RC matchers are not implemented yet). Moreover, it comes with a custom KICK ASS formatter

Behind every great release is a maintenance release. Go get it while it''s hot. We''ve also reworked the website a little - trying to scare off fewer people. Aslak

Hi all, I released RSpec 0.7.4 yesterday, and by now the gems should have rsync''ed to all the mirrors. This release features a complete redesign of the reports generated with --format html. You can see some examples of it here: http://rspec.rubyforge.org/report.html http://rspec.rubyforge.org/tools/failing_examples.html As usual there are many bug fixes - mostly related to spec/rails.

I just released RSpec 0.6.2 Hopefully this fixes the couple of glitches that went into 0.6.1 - the RSpec rake task was heavily refactored in 0.6.1 and didn''t work properly when packaged as a gem. This should be fixed now. Holler if things are still broken. Cheers, Aslak

Is it OK to go ahead and generate a Rails 2.0 project with RSpec 1.0.8? Am I likely to run into problems? Would it be best advised to wait or can I go ahead now? Thanks, Yitzhak -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20071212/c6fcea0f/attachment.html

It looks like the lates NetBeans milestone can run RSpec specifications: http://wiki.netbeans.org/wiki/view/NewAndNoteWorthyMilestone9 I haven''t tried it myself, but if anyone else does please tell us about your experience. Aslak

rspec_resource_generator ======================== By Pat Maddox Use this generator to generate RESTful scaffolding with RSpec specifications. Syntax is exactly the same as the scaffold_resource generator: ./script/generate rspec_resource ModelName [field:type field:type] When you run this generator, it will create a migration, model, and model spec file. In addition, it gives you a RESTful

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: *

I''m working on porting our app. Do I need to upgrade rspec from 1.1.3? If so which version. BTW the installation doc at http://rspec.info/documentation/rails/install.html seems to be stuck in the pre-git days. -- Rick DeNatale My blog on Ruby http://talklikeaduck.denhaven2.com/

Hi Just a quick question .... what backward versions of Rails will the 1.1.0 versions of RSpec and Spec::Rails support? I think I maybe under the (incorrect) impression that I had to go to Rails 2.0 for 1.1.0 Cheers Shane Shane Mingins ELC Technologies (TM) 1921 State Street Santa Barbara, CA 93101 Phone: +64 4 568 6684 Mobile: +64 21 435 586 Email: smingins at elctech.com AIM:

It seems that some examples at http://rspec.info are broken with invalid html. For example: http://rspec.info/documentation/before_and_after.html All those spans there should not be visible, I think :) Isn''t rspec.info web tested well enough? :P Best regards, Jarmo

Hey all, I was just wondering if any one has played around with getting autotest''s rspec integration working with rspec''s HTML output. I really like how in the rspec textmate bundle the context of the failing code is inlined with the failing spec along with the exact line highlighted and a link to the exact spot in reference. However, I rarely use this nice output since

I''m using RSpec on Rails and would like to clean up the backtraces, so I went looking for an RSpec equivalent to ThoughtBot''s Quiet Backtrace gem<http://thoughtbot.com/projects/quietbacktrace>. I found Spec::Runner::QuietBacktraceTweaker in the RDOCS, but I can''t figure out how to use it. Can I add something to spec_helper.rb that will utilize

We''d like to get some feedback on RSpec 0.9 before we start pushing out releases via Rubyforge''s gem server and update the website. We have therefore made the first beta of 0.9 available - both prepackaged and tagged in subversion (see below). RSpec 0.9 introduces a new API for expectations, which essentially means that your underscores go away (there has been other discussions

Hi, Is there already a plugin for RadRails that would support RSpec ? Thx Julien -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20070411/1c9aca29/attachment.html

Using 1.0.8, I just realized that I''ve been scrolling through pages of backtraces when rspec is supposed to clean them up for me. This is a new development machine, so I''m not sure if older versions worked or not. I''m running Ruby 1.8.6, Rails edge, Mac OS X 10.4.10. I''ve verified that the QuietBacktraceTweaker is the one that''s running.

Before I chalk this up as a bug and report it, I just want to make sure I''m not doing something silly. Running ZenTest''s autotest on OS 10.4.10 with RSpec 1.0.8, drb, produces the following failed test: ActiveRecord::AssociationTypeMismatch in ''User should create an avatar with uploaded_data'' Avatar expected, got Avatar This only happens with that exact

How can I spec out a rake task? How can I use rake in my spec''s? I want to fix this rake spec:autotest bug with --drb and --color. How can I get rake output? How would I get out of autotest? My initial thought is just to run the command in the spec. Scott

http://www.infoq.com/news/2006/11/RSpecOnJRuby

@settings.should allow_publish_ip("127.0.0.1") fails with undefined method `allow_publish_ip'' for #<#<Class:0x2f8fd48>:0x2f5a968> @settings.should_allow_publish_ip("127.0.0.1") works fine This is rspec 0.8.2. http://rspec.rubyforge.org/documentation/expectations.html says that matching arbitrary predicates is deprecated and to see