rspec2

I'm testing my controllers using Rspec and I can't seem to set the session variable of the current controller under test before making the request to the path. For example this works: describe "GET /controller/path" do it "if not matching CRSF should display message" do get controller_path request.session[:state] = "12334" end end This doesn't work (i get an error saying session is not a method of Nil class): describe "GET /controller/path" do it "if not matching CRSF should display message" do request.session[:state] = "12334" get controller_path end end Any ideas? With new version of RSpec

How can I specify #initialize behaviour with RSpec? For example here: generator.rb class Generator attr_accessor :seed def initialize(seed = nil) @seed = seed || pick_seed end def pick_seed Time.now.to_i end end generator_spec.rb require 'generator' describe Generator it "calls 'pick_seed' method unless seed specified" do end end I'd like to set expectation that pick_seed method called from #initialize method. Sean DeNigris For me, expectations are about designing conversations among collaborators. So, you have to decide - is #pick_seed an internal implementation detail or part of a

How do I reset a singleton object in Ruby? I know that one'd never want to do this in real code but what about unit tests? Here's what I am trying to do in an RSpec test - describe MySingleton, "#not_initialised" do it "raises an exception" do expect {MySingleton.get_something}.to raise_error(RuntimeError) end end It fails because one of my previous tests initialises the singleton object. I have tried following Ian White's advice from this link which essentially monkey patches Singleton to provide a reset_instance method but I get an undefined method 'reset_instance' exception. require

I'm trying to write a request test that asserts that the proper links appear on the application layout depending in whether a user is logged in or out. FWIW, I'm using Devise for the authentication piece. Here's my spec: require 'spec_helper' require 'devise/test_helpers' describe "Layout Links" do context "the home page" do context "session controls" do context "for an authenticated user" do before do # I know these should all operate in isolation, but I # want to make sure the user is explicitly logged out visit destroy_user_session_path @user = Factory(:user, :password => "Asd123",

So we have been setting up attr_accessible and attr_protected on many fields through out our Rails 3.2 app. For now we really don't test to ensure that these fields are protected. So I decided to google some answers and stumbled upon this solution: RSpec::Matchers.define :be_accessible do |attribute| match do |response| response.send("#{attribute}=", :foo) response.send("#{attribute}").eql? :foo end description { "be accessible :#{attribute}" } failure_message_for_should { ":#{attribute} should be accessible" } failure_message_for_should_not { ":#{attribute} should not be accessible" } end But

How do you test redirect_to :back in rspec? I get ActionController::RedirectBackError : No HTTP_REFERER was set in the request to this action, so redirect_to :back could not be called successfully. If this is a test, make sure to specify request.env["HTTP_REFERER"] . How do I go about setting the HTTP_REFERER in my test? Using RSpec, you can set the referer in a before block. When I tried to set the referer directly in the test, it didn't seem to work no matter where I put it, but the before block does the trick. describe BackController < ApplicationController do before(:each) do request.env[

I have read what the RSpec manual says about the difference, but some things are still confusing. Every other source, including "The RSpec Book" only explain about "let", and "The Rails 3 Way" is just as confusing as the manual. I understand that "let" is only evaluated when invoked, and keeps the same value within a scope. So it makes sense that in the first example in the manual the first test passes as the "let" is invoked only once, and the second test passes as it adds to the value of the first test (which was evaluated once in the first test and has the value of 1). Following that, since

I'm looking for a rather recent open source application that uses Rspec 2 as test library. I'd like to see how an experienced developer utilizes the library properly to test the full stack, since I'm constantly in doubt concerning my own knowledge (coming from testunit and partly due to the rather sparse documentation of the latest Rspec release, even though it is constantly improved). If a project would use Cucumber, Pickle and/or Capybara as well together with Rspec 2, you'd have me jumping for joy. Any pointers? Cheers! My 2 cents: Use Steak instead of Cucumber. It RSpec at its core, it is