search for: should_not_be_nil

Hi, I''m trying the specs for restful_authentication I found here http://jonathan.tron.name/articles/2007/01/02/rspec-on-rails-restful- authentication It seems to use custom .should methods: should_eql, should_be_an_instance_of, should_redirect_to, should_be_success, should_not_be_nil, should_be_nil, should_not_be_nil, should_be_empty, should_be_success, should_not_change, and should_not_be_activated Is this using an old version of rspec, and/or do i need to define these methods and how? thanks linoj

...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. assigns[:member].projects.each{|p| puts "project #{p.name}"} # force association to be loaded 3. assigns[:member].projects.size.should_be 1

...hould add a record" do post :edit_or_create, :user => {:login => ''joeschmoe'', :email => ''joe at shmoe.com'', :email_confirmation => ''joe at shmoe.com'', :full_name => ''Joe Schmoe''} assigns[:user].should_not_be_nil assigns[:user].new_record?.should_not_be(true) flash[:notice].should_match(/user added/) response.should_be_redirect puts "redirecting to #{response.redirect_url}" puts "this response was #{response.redirect?}" controller.should_redirect_to '...

...end end And a bunch of controller specs, an example of which looks like this: describe ShopsController do describe "when responding to a GET" do context "#new" do it "should create a new instance of the shop class" do get :new @shop.should_not_be_nil end end end end In rake routes, as well as via a web browser, this controller/action works fine. However, RSpec throws: 1) ShopsController when responding to a GET#new should create a new instance of the shop class Failure/Error: get :new ActionController::RoutingError: No rout...

...lize doesn''t seem to be the right way of doing this, but before_create or any of the other things don''t make the first test pass. specify "should provide a default name when none is given" do @emailer.attributes = valid_emailer_attributes.except(:name) @emailer.name.should_not_be_nil @emailer.should_be_valid end specify "should not replace name if one is given" do @emailer.attributes = valid_emailer_attributes # valid name attribute is "bill" (@emailer.name=="bill").should_be_true end class Emailer < ActiveRecord::Base def after_in...

Hi! Today I needed to implement some controller code, that uses send_file() to send image data. How can this be tested / specified with RSpec? bye, Tobias

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

I''ve found these two snippets of code useful and would love some feedback. first, .should_have_valid_associations usage: context "A new Product" do specify "should have valid associations" do @product.should_have_valid_associations end end code: (thanks to Wilson/Defiler for converting to rspec) module Spec module Expectations module Should