rspec2

I have a Rails app and I am trying to test it. I use devise to log in. However, I faced a problem that occurs when I want to test: Users/ender/Projects/ratingw/spec/controllers/widgets_controller_spec.rb:4:in `block in <top (required)>': undefined local variable or method `login_user' for #<Class:0x007fe909bd5070> (NameError) First, I want to say that I read this devise formal tutorial . My spec_helper.rb is: # This file is copied to spec/ when you run 'rails generate rspec:install' ENV["RAILS_ENV"] ||= 'test' require File.expand_path("../../config/environment", __FILE__) require 'rspec/rails'

I am trying to write some routing specs for a mountable rails 3.1 engine. I have working model and controller specs, but I cannot figure out how to specify routes. For a sample engine, 'testy', every approach I try ends with the same error: ActionController::RoutingError: No route matches "/testy" I've tried both Rspec and Test::Unit syntax (spec/routing/index_routing_spec.rb): describe "test controller routing" do it "Routs the root to the test controller's index action" do { :get => '/testy/' }.should route_to(:controller => 'test', :action => 'index') end it "tries the same thing using Test

I am trying to build a spec for this statement. It is easy with 'puts' print "'#{@file}' doesn't exist: Create Empty File (y/n)?" RSpec 3.0+ RSpec 3.0 added a new output matcher for this purpose: expect { my_method }.to output("my message").to_stdout expect { my_method }.to output("my error").to_stderr Minitest Minitest also has something called capture_io : out, err = capture_io do my_method end assert_equals "my message", out assert_equals "my error", err RSpec < 3.0 (and others) For RSpec < 3.0 and other frameworks, you can use the following helper. This will allow you to capture whatever

With the new expect syntax in rspec-2.11, how is it possible to use the implicit subject ? Is there a better way than explicitly referencing subject , like below? describe User do it 'is valid' do expect(subject).to be_valid # <<< can `subject` be implicit? end end If you configure RSpec to disable the should syntax, you can still use the old one-liner syntax, since that doesn't involve should being added to every object: describe User do it { should be_valid } end We briefly discussed an alternate one-liner syntax, but decided against it since it wasn't needed and we felt like it might add

How do I turn off transactional fixtures for only one spec (or Steak scenario) with RSpec 2? I tried some things found on the web without any success. This leads to an undefined method exception. describe "MyClass without transactional fixtures" do self.use_transactional_fixtures = false ... end This simply does nothing (transactional fixture is still on): describe "MyClass without transactional fixtures" do RSpec.configure do |config| config.use_transactional_fixtures = false end ... end What else could I try? This used to be a bug (see ticket #197 ), but I seems to be okay now. I just don't

It is pretty easy with the added generator of rspec-rails to setup RSpec for testing a Rails application. But how about adding RSpec for testing a gem in development? I am not using jeweler or such tools. I just used Bundler ( bundle gem my_gem ) to setup the structure for the new gem and edit the *.gemspec manually. I also added s.add_development_dependency "rspec", ">= 2.0.0" to gemspec and did a bundle install . Is there some nice tutorial what to do next to get RSpec working? iain I've updated this answer to match current best practices: Bundler supports gem development perfectly. If you

After significant troubleshooting, I figured out that I needed to run rake spec once (I can abort with control-c) before I can run rspec directly (e.g. on a subset of our specs). We are running Rails 3.0.7 and RSpec 2.5.0. Clearly, rake is running some important database setup tasks / code (we have custom code in the root level rails Rakefile and possibly other places). How can I run the rake test database setup tasks / code without running rake spec ? In addition to being able to run rspec on a subset of files, I am using specjour to spread our specs across multiple cores (haven't had success