Skip to content
This repository has been archived by the owner on Nov 27, 2020. It is now read-only.

Address be_true & be_false deprecation warnings. #643

Merged
merged 1 commit into from Aug 18, 2015
Merged

Address be_true & be_false deprecation warnings. #643

merged 1 commit into from Aug 18, 2015

Conversation

erictheise
Copy link

A number of deprecation warnings related to be_true and be_false are generated when running specs:

`be_false` is deprecated. Use `be_falsey` (for Ruby's conditional semantics) or `be false` (for exact `== false` equality) instead. Called from /Users/erictheise/Projects/erictheise/poltergeist/spec/integration/session_spec.rb:242:in `block (3 levels) in <top (required)>'.
`be_true` is deprecated. Use `be_truthy` (for Ruby's conditional semantics) or `be true` (for exact `== true` equality) instead. Called from /Users/erictheise/Projects/erictheise/poltergeist/spec/integration/driver_spec.rb:197:in `block (3 levels) in <module:Poltergeist>'.
Too many uses of deprecated '`be_true`'. Pass `--deprecation-out` or set `config.deprecation_stream` to a file for full output.

These were deprecated in RSpec's move from 2.14 to 2.99.

Just hoping to contribute a little cleanup as I get my own local setup to pass all tests.

yaauie added a commit that referenced this pull request Aug 18, 2015
Address be_true & be_false deprecation warnings.
@yaauie yaauie merged commit 08323d3 into teampoltergeist:master Aug 18, 2015
@erictheise erictheise deleted the be-true-be-false branch August 18, 2015 19:16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants