similar to: Bugs Fixed in Trunk

There is an assert_difference helper for Test::Unit (you can read about it at http://blog.caboo.se/articles/2006/06/13/a-better- assert_difference and to some it should look familiar -- you know who you are :), so I took a shot at one for rSpec on Rails. class Object def should_be_different(method = nil, difference = nil) return self.should_not_eql(yield) if method.nil?

Hi I just did an update to lates trunk ================= context "Given a generated venue_spec.rb with fixtures loaded" do fixtures :venues specify "fixtures should load two Venues" do Venue.should have(2).records end end ================== gives me ========== 1) TypeError in ''Given a generated venue_spec.rb with fixtures loaded fixtures should load two

I''m taking my first fledgling steps driving a new ruby (non-rails) project with BDD. I''ve got a (test) story working. However, when I run the story in TextMate (via command-r), the output is plain text. See: http://skitch.com/georgeanderson/8grg/run-examples How do I get the output to look pretty (formatted)? rspec-1.1.3 OS X 10.5.2 TextMate v1.5.7 (1455) Thanks, /g --

I''m doing some housekeeping and just realised that the rdoc formatter produces gibberish: http://rspec.rubyforge.org/rdoc/files/EXAMPLES_rd.html Will anyone protest if I just go ahead and remove it? (I can''t imagine anyone using it, especially with the much better HTML formatter) Aslak

Sort of off-topic and don''t mean to complain, but many on this list use top quoting. That works ok if you don''t quote the whole previous thread. However, I''m finding that scrolling forever to locate the reply on longer threads is getting tedious. What''s the rationale for top-quoting? Thx.

@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

I occasionally get this error: 1) ''A puzzle once featured, should no longer be nominated'' FAILED expected: Sun May 04 09:10:26 -0700 2008, got: Sun May 04 09:10:26 -0700 2008 (using ==) ./spec/models/puzzle_spec.rb:180: So, the dates looks the same to me. Any ideas for how to debug? Joe

Hi all, I know I shouldn't really expect the following to work, but it provokes a crash of the GUI on my computer (Win xp professional). --- >sessionInfo() Version 2.3.1 (2006-06-01) i386-pc-mingw32 attached base packages: [1] "methods" "stats" "graphics" "grDevices" "utils" "datasets" [7] "base"

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

In the history.txt for 0.2 is an "important note" toward the bottom of the announcement. (http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt ). This is really, *really* important for Rails users, but it can be more than a bit difficult to Google out. Questions: 1. Can this be brought into a wiki page on github on cuke.info? 2. Is

I have a Rails model that has an observer. The function of the observer is to send an email when a particular state change occurs in the model. Because the template rendering code is not loaded when doing model testing, I''ve had to shut off the email functionality of the observer for testing. Is there a better way to handle this? Thanks

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

I''m new to rspec. I just installed these: rspec (0.7.4) RSpec-0.7.4 (r1201) (rspec gem) rspec_on_rails .3 plugin (on vendor/plugin) I''ve set up a simple spec - spec/library/test_spec.rb: require File.dirname(__FILE__) + ''/../spec_helper'' context "test context" do setup do #nothing end specify "nothing to specify" do

If you want to use rspec-0.9.2 with autotest (ZenTest-3.5.2), you''ll want to read this blog: http://blog.davidchelimsky.net/articles/2007/05/01/rspec-0-9-1-and-autotest-zentest-3-5-2 Enjoy! David

I''m working with a has_many :through association, where a Member has_many Projects through ProjectViewers. The problem I''m running into is that Rails doesn''t load the association so line (3) fails until I explicitly access a member of the collection (in this case, I iterated it). Is there a better way? Thanks, Steve 1. assigns[:member].should_not_be_nil 2.

Hi there, I''ve installed rspec, rails plugin & generators thusly: $ sudo gem install rspec $ sudo gem install rspec_generator $ sudo gem install zentest -v 3.4.1 $ ./script/plugin install svn://rubyforge.org/var/svn/rspec/tags/REL_0_7_2/vendor/rspec_on_rails/vendor/plugins/rspec $ ./script/generate rspec $ ./script/generate rspec_model ModelName With Rails version: $ rails

I have a Dovecot installation on a Fedora 4. With the last update from Dovecot RC10 to Dovecot RC27, the daemon kills itself every night with this error: Mar 17 05:23:11 mail dovecot: Time just moved backwards by 6 seconds. This might cause a lot of problems, so I'll just kill m yself now. The error appears just after the night maintenance script executes a ntpdate syncronization ntpdate

I see that there is an integration testing example in the plugin code. What is the thinking about integration specs? Thanks, Steve

I love the way I can throw a call to pending() in the top of an unfinished RSpec example and stop it from failing the build. Is there a similar way to do such a thing with good ole'' cucumber? cheers, Matt ---- http://blog.mattwynne.net http://songkick.com In case you wondered: The opinions expressed in this email are my own and do not necessarily reflect the views of any former,

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