When a before(:all) is defined in the RSpec.configure block it is called before each top level example group, while a before(:suite) code block is only called once. Here’s an example: RSpec.configure do |config| config.before(:all) { puts ‘Before :all’ } config.after(:all) { puts ‘After :all’ } config.before(:suite) { puts ‘Before :suite’ } config.after(:suite) { puts ‘After … Read more
The first place to go is the official Relish docs, they have gotten a significant improvement over the years and are now my first place to look. At the time of writing this answer originally, this gist was solid. It contains matchers for the following: Capybara Paperclip with Shoulda Rspec Rails Rspec Exceptions Shoulda Matchers
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[“HTTP_REFERER”] = “where_i_came_from” end describe “GET /goback” do … Read more
CONGRATULATIONS on you endeavor into TDD with ROR I promise once you get going you will not look back. The simplest quick and dirty solution will be to generate a new valid model before each of your tests like this: before(:each) do @user = User.new @user.username = “a valid username” end BUT what I suggest … Read more
There’s now a not very well documented method called expect_any_instance_of that handles the any_instance special case. You should use: expect_any_instance_of(Object).to receive(:subscribe) Google expect_any_instance_of for more info.
I would recommend dropping your test database, then re-create it and migrate: bundle exec rake db:drop RAILS_ENV=test bundle exec rake db:create RAILS_ENV=test bundle exec rake db:schema:load RAILS_ENV=test After these steps you can run your specs: bundle exec rspec spec gerry3 noted that: A simpler solution is to just run rake db:test:prepare However, if you’re using … Read more
You must run rspec with -b option to see full backtraces
The context is an alias for describe, so they are functionally equivalent. You can use them interchangeably, the only difference is how your spec file reads. There is no difference in test output for example. The RSpec book says: “We tend to use describe() for things and context() for context”. Personally I like to use … Read more
I’ve updated this answer to match current best practices: Bundler supports gem development perfectly. If you are creating a gem, the only thing you need to have in your Gemfile is the following: source “https://rubygems.org” gemspec This tells Bundler to look inside your gemspec file for the dependencies when you run bundle install. Next up, … Read more
The following should work: at command line: rails new MYAPP -T # The -T option tells rails not to include Test::Unit in Gemfile: gem ‘rspec-rails’ at command line: bundle install rails g rspec:install