Upgrade rspec and capybara again #170
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
April 2, 2015 14:02
refs #161 The below warning was surpressed by the newest capybara. c.f. teamcapybara/capybara#1254 Warning: -------------------------------------------------------------------------------- Capybara::RSpecMatchers::HaveText implements a legacy RSpec matcher protocol. For the current protocol you should expose the failure messages via the `failure_message` and `failure_message_when_negated` methods. (Used from /Users/yoshihara/everyleaf/fluentd-ui/spec/features/fluentd/setting/running_backup_spec.rb:85:in `block (6 levels) in <top (required)>') -------------------------------------------------------------------------------- And specs are all green :)
|
LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I created PR #169 , but I upgraded other gems unexpectedly, so i updated again RSpec and Capybara only.
I'll going to upgrade Rails4.2 (#161), so I upgraded RSpec (~> 3.0) at first.
After RSpec upgrading, warnings is caused so i suppressed them by upgrading capybara.