You can just use: first(‘.item’).click_link(‘Agree’) or first(‘.item > a’).click (if your default selector is :css) Code in your question doesn’t work as: within “.item” do first(:link, “Agree”).click end is equivalent to: find(‘.item’).first(:link, “Agree”).click Capybara finds several .item‘s so it raises an exception. I consider this behavior of Capybara 2 very good.
I find using the be_within default rspec matcher more elegant: expect(@article.updated_at.utc).to be_within(1.second).of Time.now
I’ve updated this answer to reflect modern conventions in capybara. I think this is ideal since this is the accepted answer, and what many people are being referred to when looking for a solution. With that said, the correct way to check the current path is to use the has_current_path? matcher provided by Capybara, as … Read more
As you can see in the docs here, the intended use is creating ~/.rspec and in it putting your options, such as –color. To quickly create an ~/.rspec file with the –color option, just run: echo ‘–color’ >> ~/.rspec
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
You could parse the response body like this: parsed_body = JSON.parse(response.body) Then you can make your assertions against that parsed content. parsed_body[“foo”].should == “bar”
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
Another pretty solution would be: page.should have_field(‘Your name’, with: ‘John’) or expect(page).to have_field(‘Your name’, with: ‘John’) respectively. Also see the reference. Note: for disabled inputs, you’ll need to add the option disabled: true.
The rad way => let(:dummy_class) { Class.new { include ModuleToBeTested } } Alternatively you can extend the test class with your module: let(:dummy_class) { Class.new { extend ModuleToBeTested } } Using ‘let’ is better than using an instance variable to define the dummy class in the before(:each) When to use RSpec let()?
You can tag examples with :focus hash attribute. For example, # spec/foo_spec.rb RSpec.describe Foo do it ‘is never executed’ do raise “never reached” end it ‘runs this spec’, focus: true do expect(1).to eq(1) end end rspec –tag focus spec/foo_spec.rb More info on GitHub. (anyone with a better link, please advise) (update) RSpec is now superbly … Read more