RSpec and Cucumber are both testing frameworks. RSpec includes traditional Unit Testing (which means testing a class or part of the application in isolation from the rest of the application. So your model does what your model is supposed to do, the controller does what it is supposed to do, etc). RSpec and Cucumber both … Read more
I’m not sure if it is the best solution, but I have successfully achieved this using: FactoryGirl.define do factory :user do first_name “Luiz” last_name “Branco” #… after(:build) { |user| user.class.skip_callback(:create, :after, :run_something) } factory :user_with_run_something do after(:create) { |user| user.send(:run_something) } end end end Running without callback: FactoryGirl.create(:user) Running with callback: FactoryGirl.create(:user_with_run_something)
In RSpec 2 and 3, you can use the –profile flag or add –profile to your .rspec file. This will track the top 10 slowest examples. For RSpec 1, you can use –format o with spec command. It shows a text-based progress bar with profiling of 10 slowest examples. For more details see this. rspec … Read more
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
Use #instance_eval @controller = AccountController.new @controller.instance_eval{ current_account } # invoke the private method @controller.instance_eval{ @current_account }.should eql … # check the value of the instance variable
I found the following worked for me: # Check find(:css, “#cityID[value=”62″]”).set(true) # Uncheck find(:css, “#cityID[value=”62″]”).set(false)
This question has been answered on Twitter by @MatthewClosson @jeffehh You need to create a spec/support/devise.rb file as specified here https://github.com/plataformatec/devise#test-helpers to include the devise test helpers #ruby Thanks once again.
If you haven’t already, you might want to check out Dan North’s excellent article, What’s in a Story? as a starting point. We have two main uses for Cucumber stories. First, because the story form is very specific it helps focus the product owner’s articulation of the features he wants built. This is the “token … Read more
You should be able to specify HTTP headers as the third argument to your get() method as described here: http://api.rubyonrails.org/classes/ActionDispatch/Integration/RequestHelpers.html#method-i-get and here http://api.rubyonrails.org/classes/ActionDispatch/Integration/Session.html#method-i-process So, you can try something like this: get ‘/my/path’, nil, {‘HTTP_ACCEPT’ => “application/json”}
it “should call ‘bar’ with appropriate arguments” do expect(subject).to receive(:bar).with(“an argument I want”) subject.foo end