minitest-rails-capybara | Capybara integration for MiniTest : :Rails | Application Framework library

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.

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.

You need to put the page.must_have_content 'USER SETTING & INFO' before the DatabaseCleaner.clean line. This is because when you click a button it can return immediately while the request triggered by the button click happens asynchronously. In your case this means you click the button, then clean the database, meanwhile the request to create the new user is sent and most likely arrives after the database has already been cleared thereby creating a user that doesn't get cleared.

Usually the DatabaseCleaner methods would be called from setup/teardown with minitest (before/append_after blocks with RSpec) to ensure that database cleaning doesn't occur until the test is complete, and that they get run even if something in the test fails.

By default Capybara only finds visible elements, so if you're using one of the drivers that fully processes CSS (pretty much anything except rack_test) then just doing

1) You should update ruby

Your Ruby is: 2.3.0 (buggy). Recommendation: upgrade to 2.3.1.

2) the error was a capital C: