wojtekmach / minitest-capybara Goto Github PK

View Code? Open in Web Editor NEW

41.0 3.0 18.0 63 KB

**Deprecated** Capybara matchers support for minitest unit & spec

Home Page: https://rubygems.org/gems/minitest-capybara

License: MIT License

Ruby 100.00%

minitest-capybara's Introduction

minitest-capybara

⚠️ This gem is no longer maintained as Capybara has added Minitest support upstream, use that instead.

Capybara matchers support for Minitest unit & spec.

Why?

Capybara has good support for RSpec.

If you want to use it with Minitest, you can of course write:

assert page.has_content?("Hello")

but:

it's kinda ugly
you don't have meaningfull error messages.

With this project Minitest gets all the good stuff.

Rails integration

minitest-capybara (and capybara) works with Rails out of the box, remember to require capybara/rails.

See example Rails app: https://github.com/wojtekmach/minitest-capybara-example.

For more features, check out: minitest-rails-capybara.

Usage

With minitest/test:

class HomeTest < Minitest::Capybara::Test
  def test_home
    visit "/"

    assert_content "Homepage"

    within ".login" do
      refute_content "Signed in as"
    end

    assert_link "Sign in"
    assert_link find(".login"), "Sign in"

    assert_selector 'li:first', text: "Item 1"
  end
end

With minitest/spec:

class HomeSpec < Minitest::Capybara::Spec
  it "works" do
    visit "/"

    page.must_have_content "Homepage"

    within ".login" do
      page.wont_have_content "Signed in as"
    end

    find(".login").must_have_link("Sign in")

    page.must_have_selector 'li:first', text: "Item 1"
  end
end

Instead of inheriting directly from Minitest::Capybara::Test (or Spec) it's usually better to create a custom test base class:

# test/acceptance_test_helper.rb
require "minitest/autorun"

class AcceptanceTest < Minitest::Capybara::Test
  # custom methods, before blocks etc.
end

If you need to inherit from a different base class (e.g. ActiveSupport::TestCase) you can do this instead:

# test/acceptance_test_helper.rb
require "test_helper"

class AcceptanceTest < ActiveSupport::TestCase
  include Minitest::Capybara::Behaviour

  # custom methods, before blocks etc.
end

Capybara drivers

Switching drivers is easy with minitest-metadata:

require 'minitest-metadata'

class AcceptanceSpec < Minitest::Capybara::Spec
  before do
    if metadata[:js]
      Capybara.current_driver = Capybara.javascript_driver
    else
      Capybara.current_driver = Capybara.default_driver
    end
  end
end

class HomeSpec < AcceptanceSpec
  it "home with ajax", js: true do
    visit "/"
    page.must_have_content "AJAX enabled..."
  end
end

License

minitest-capybara is released under the MIT License.

minitest-capybara's People

Contributors

Stargazers

Watchers

Forkers

minitest knewter patru acnalesso yoki kaspth apotonick jonatack joseramonc branquinhoaa gui vipulnsward searls

minitest-capybara's Issues

Minitest 5.0 support?

minitest-capybara (>= 0) ruby depends on
  minitest (~> 4.0) ruby

Use Capybara 3.x

Hi, thanks a lot for writing this gem! 😄
I'd like to use it with the latest Capybara (v3). I tried simply updating the dependency and it worked fine.

What are the changes that would need to be done to support Capybara 3?
I'm happy to work on it if you could point me to the right direction.
Thanks!

Integration issue with spec (`describe` blocks)

Thanks for writing this gem, it seems super useful.

I'm having trouble using this in a project that uses MiniTest::Spec. It doesn't create any Spec classes, instead opting for just plain describe blocks, via Capybara::DSL.

require "features_helper"

describe "this feature" do
 # ...
end

Inside features_helper.rb we have:

class MiniTest::Spec
  include Capybara::DSL
end

I added require "minitest/capybara" but it didn't work.
Do I need to open a class and include Minitest::Capybara::Behaviour?

Clarify what extra functionality this gem provides

In Capybara 2.x this gem provided much needed support for mintest assertions. Since Capybara added its own minitest assertions - https://github.com/teamcapybara/capybara/blob/master/lib/capybara/minitest.rb and https://github.com/teamcapybara/capybara/blob/master/lib/capybara/minitest/spec.rb - it's much less clear what added functionality this gem provides.

Please update to latest capybara

implicit dependency on capybara 2.1.0

This is more for reference than a real issue, but there is a small dependency of the master branch on capybara 2.1.0. As I am stuck with Ruby 1.9.2 I can only use capybara 2.0.3 at the moment. assert_link (and other dynamically created methods from capybara/assertions.rb) rely on Capybara::Helpers.failure_message being present (which only got defined in capybara 2.1.0). For this reason they throw an exception when they fail (but only then, thanks to the dynamic nature of Ruby). So your existing tests are all fine, but you have a pretty hard time figuring out which assertion failed if anything breaks.

As this is easily fixed using the code in the following Gist

https://gist.github.com/Patru/6623747

this is hardly worth fixing, but it is probably easier to find this way.

uninitialized constant MiniTest::Capybara::Assertions::Capybara (NameError)

I ran into this error:

uninitialized constant MiniTest::Capybara::Assertions::Capybara (NameError)

The full line looks like this:

/Users/abatko/.rvm/gems/ruby-1.9.3-p448@hello/gems/minitest-capybara-0.3.0/lib/minitest/capybara.rb:6:in `<module:Assertions>': uninitialized constant MiniTest::Capybara::Assertions::Capybara (NameError)

Downgrading to 0.1.0 resolved the issue.

I am not be able to downgrade to 0.2.0 without having to make additional dependency changes:

Bundler could not find compatible versions for gem "capybara":
  In Gemfile:
    minitest-capybara (= 0.2.0) ruby depends on
      capybara (~> 1.0) ruby

    minitest-rails-capybara (~> 0.9.0) ruby depends on
      capybara (2.1.0)

can not use with rails 4.2

My application:
rails 4.2.4
capybara 2.5.0
minitest 5.8.2