How can I test the page title with Capybara 2.0?

by

I had the same issues when I upgraded to Capybara 2.0, and managed to solve them by creating the following custom RSpec matcher using Capybara.string:

spec/support/utilities.rb

RSpec::Matchers::define :have_title do |text|
  match do |page|
    Capybara.string(page.body).has_selector?('title', text: text)
  end
end

Now, in a spec file where subject { page }, I can use:

it { should have_title("My Title") }
it { should_not have_title("My Title") }

As an aside, the conversation on this question was extremely helpful in getting me to this answer, so thank you!

Update 1:

If you don’t want to create a custom RSpec matcher, thanks to this StackOverflow answer by user dimuch I now know that you can call have_selector directly on page.source (aliased page.body) to test for non-visible DOM elements:

it "should show the correct title" do
  page.source.should have_selector('title', text: 'My Title')
end

or where subject { page }:

its(:source) { should have_selector('title', text: 'My Title') }

Update 2:

From Capybara 2.1, there are built-in have_title/has_title? matchers, negating the need for the custom RSpec matcher in this answer. Furthermore, the its(:source) { ... } tests described in Update 1 seem to break under Capybara 2.1; I’ve confirmed the have_title/has_title? work as expected, so it’s probably best to go with the following syntax if you plan on upgrading:

When subject { page }:

it { should have_title("My Title") }
it { should_not have_title("My Title") }

When using expect syntax within an it/scenario block:

expect(page).to have_title("My Title")
expect(page).to_not have_title("My Title")

More Related Contents:

  1. How to check a checkbox in capybara?
  2. undefined method `visit’ when using RSpec and Capybara in rails
  3. Why not use shared ActiveRecord connections for Rspec + Selenium?
  4. Rspec and capybara, difference between visit and get methods, with regards to the current_path object
  5. Why does adding “sleep 1” in an after hook cause this Rspec/Capybara test to pass?
  6. Why isn’t my CORS configuration causing the server to filter incoming requests? How can I make the server only accept requests from a specific origin?
  7. Reducing n+1 queries using the Bullet and RSpec gems
  8. Rails: Missing host to link to! Please provide :host parameter or set default_url_options[:host]
  9. How do I change the default “www.example.com” domain for testing in rails?
  10. How to spec a private method
  11. undefined method `get’ for #
  12. Capybara with subdomains – default_host
  13. Visit method not found in my rspec
  14. Suppress Ruby warnings when running specs
  15. How do you POST to a URL in Capybara?
  16. Rails rspec set subdomain
  17. How to check for a JSON response using RSpec?
  18. How is spec/rails_helper.rb different from spec/spec_helper.rb? Do I need it?
  19. Unable to obtain stable firefox connection in 60 seconds (127.0.0.1:7055)
  20. Controller spec unknown keyword: id
  21. Set Rspec default GET request format to JSON
  22. How to set request headers in rspec request spec?
  23. Why is Rspec saying “Failure/Error: Unable to find matching line from backtrace”?
  24. Configuring Warden for use in RSpec controller specs
  25. Incompatible library version: nokogiri.bundle requires version 11.0.0 or later, but libxml2.2.dylib
  26. form_for with nested resources
  27. Why do routes with a dot in a parameter fail to match?
  28. Heroku/devise – Missing host to link to! Please provide :host parameter or set default_url_options[:host]
  29. Use bundle exec rake or just rake?
  30. JWT token decoding even when the last character of the signature is changed

Leave a Comment