RSpec 3.0 beta

gistfile1.sh

master $ rake ci
rspec -v
3.0.0.beta2
rspec spec --color
.......FF......................................................................................................

Failures:

  1) XCPretty::Formatter initializes with unicode
     Failure/Error: @formatter.use_unicode?.should be_true
     NoMethodError:
       undefined method `true?' for true:TrueClass
     # ./spec/xcpretty/formatters/formatter_spec.rb:14:in `block (2 levels) in <module:XCPretty>'

  2) XCPretty::Formatter initializes with color
     Failure/Error: @formatter.colorize?.should be_true
     NoMethodError:
       undefined method `true?' for true:TrueClass
     # ./spec/xcpretty/formatters/formatter_spec.rb:18:in `block (2 levels) in <module:XCPretty>'

Finished in 0.19785 seconds
111 examples, 2 failures

Failed examples:

rspec ./spec/xcpretty/formatters/formatter_spec.rb:13 # XCPretty::Formatter initializes with unicode
rspec ./spec/xcpretty/formatters/formatter_spec.rb:17 # XCPretty::Formatter initializes with color

Deprecation Warnings:

Using `should_receive` from rspec-mocks' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /Users/supermarin/code/OSS/xcpretty/spec/xcpretty/parser_spec.rb:388:in `block (3 levels) in <module:XCPretty>'.

Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` instead. Called from /Users/supermarin/code/OSS/xcpretty/spec/xcpretty/ansi_spec.rb:14:in `block (3 levels) in <module:XCPretty>'.

`failure_message_for_should_not` is deprecated. Use `failure_message_when_negated` instead. Called from /Users/supermarin/code/OSS/xcpretty/spec/support/matchers/colors.rb:17:in `block in <top (required)>'.

`failure_message_for_should` is deprecated. Use `failure_message` instead. Called from /Users/supermarin/code/OSS/xcpretty/spec/support/matchers/colors.rb:14:in `block in <top (required)>'.


If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
`config.raise_errors_for_deprecations!`, and it will turn the
deprecation warnings into errors, giving you the full backtrace.

4 deprecation warnings total
rake aborted!




master $ bundle exec rake ci                                                                                                rspec -v
2.14.8
rspec spec --color
...............................................................................................................

Finished in 0.19728 seconds
111 examples, 0 failures