You can use pending() or change it to xit or wrap assert in pending block for wait implementation: describe ‘Automation System’ do # some code here it ‘Test01’ do pending(“is implemented but waiting”) end it ‘Test02’ do # or without message pending end pending do “string”.reverse.should == “gnirts” end xit ‘Test03’ do true.should be(true) end … Read more
As has been mentioned: expect(4).to eq(4) This is specifically testing the value that you’ve sent in as the parameter to the method. When you’re trying to test for raised errors when you do the same thing: expect(raise “fail!”).to raise_error Your argument is evaluated immediately and that exception will be thrown and your test will blow … Read more
As far as I have been able to tell, sending raw POST data is no longer possible within a controller spec. However, it can be done pretty easily in a request spec: describe “Example”, :type => :request do params = { token: 0 } post “/user/reset_password”, params.to_json, { ‘CONTENT_TYPE’ => ‘application/json’, ‘ACCEPT’ => ‘application/json’ } … Read more
I understood the difference between let and let! with a very simple example. Let me read the doc sentence first, then show the output hands on. About let doc says :- … let is lazy-evaluated: it is not evaluated until the first time the method it defines is invoked. I understood the difference with the … Read more
I normally include this code to require everything under my spec/support subdirectory once the Rails stack is available: Spork.prefork do # … Dir[Rails.root.join(‘spec’, ‘support’, ‘**’, ‘*.rb’)].each { |f| require f } RSpec.configure do |config| config.include MyCustomHelper # … end end Note that this will include MyCustomHelper in all example types (controllers, models, views, helpers, etc.). … Read more
You can use an anonymous controller to test your ApplicationController, as describe in the RSpec documentation. There’s also a section on testing helpers.
Assuming your test environment is set up in the usual fashion (that is, you have config.action_mailer.delivery_method = :test), then delivered emails are inserted into the global array ActionMailer::Base.deliveries as Mail::Message instances. You can read that from your test case and ensure the email is as expected. See here.
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 … Read more
In RSpec 2, the /spec folder is always automatically on your load path. This means that all you need is: require ‘spec_helper’ at the top of your spec files. This will always load /spec/spec_helper.rb, and is the minimum you’ll be able to get away with. This means you don’t need a horrid approach such as: … Read more
So the answer is No. before is equivalent to before :each, not before :all Test example. Update: Wow, this question is popular. To save your head from cognitive overload, I suggest you explicitly state :each or :all.