minitest-rails | Minitest integration for Rails | Application Framework library

You have to fix gems version, for example:

The root of the problem seems to be bundler. What operating system and Ruby version are you using? It may be a problem with old OpenSSL library, so you can not install bundler and everything after it.

If you are using jRuby (your gem list output tells so), your problem seems to be the same as described in link. And there is a solution as well.

Maybe you forgot to set 2.1.2 version of ruby as global? (rbenv set global 2.1.2)

The header "Using Capybara with Minitest::Spec" contains a hint :) Check https://github.com/teamcapybara/capybara/blob/master/lib/capybara/minitest/spec.rb#L8 ...

Firstly there is no need to assert on the presence of an element before clicking it since click_link will wait up to Capybara.default_max_wait_time seconds for the link to appear on the page and then click it. If the link doesn't appear in that time it will raise an error, so asserting on its presence is superfluous.

The error you're getting is because minitest-capybara isn't compatible with Capybara 2.9+ - https://github.com/wojtekmach/minitest-capybara/pull/17 - and the fact that assert_select doesn't take 2 strings as parameters. It just takes the id, name, or label text of a select element. So I'm guessing that's not actually the method you mean to be calling.

You could create a template.rb file with following configuration:

I'm not sure which FF versions are supported on selenium 2.53, consider downgrading your FF version (aim for something like v46-v47) or upgrading selenium version (which would be better, but then you need additional geckodriver setup). See if that helps.

The file capybara/minitest was added to Capybara in version 2.13.0, which is the minimum version Rails requires for its system tests since Rails 5.1.0. Upgrade to the latest version of Capybara (2.14.4) and there should be no need for the minitest-capybara or minitest-rails gems. You will need to also add the 'selenium-webdriver' gem to your test group.

Additionally the assert_response :success line is't valid in Capybara tests because the HTTP response code from the browser Capybara is using isn't generally available.

You need to allow 'http://www.example.com' in your Poltergeist whitelist if you want it to allow page requests to that url.

Additionally, http://127.0.0.1:3000 is most likely your development instance, so you don't want tests hitting that because it won't be using the test data you setup.

Use of the spec DSL is purely preference. The spec DSL was popularised by RSpec, so if you are familiar with RSpec and enjoy using it you can add a similar spec DSL to minitest.

There are no advantages to using or not using the spec DSL.