Add support for 3.0.0.beta2

[yelled3]

hopefully, this will make the transition to rspec 3 smoother :-)

[philostler]

I've not done testing against 3.0.0.beta2 yet

Have you(?) and are there are current failures popping up?

[yelled3]

rspec spec 
[rspec-sidekiq] WARNING! Sidekiq will *NOT* process jobs in this environment. See https://github.com/philostler/rspec-sidekiq/wiki/FAQ-&-Troubleshooting                        
  1) RSpec::Sidekiq::Matchers::HaveEnqueuedJob#matches? when condition matches when expected are matchers returns true                                                          
     Failure/Error: expect(matcher_subject.matches? worker).to be true

       expected true
            got #<FalseClass:0> => false
     # ./spec/rspec/sidekiq/matchers/have_enqueued_job_spec.rb:46:in `block (5 levels) in <top (required)>'

 86/86 |======================================================================== 100 =========================================================================>| Time: 00:00:00 

Finished in 0.19959 seconds
86 examples, 1 failure

Failed examples:

rspec ./spec/rspec/sidekiq/matchers/have_enqueued_job_spec.rb:45 # RSpec::Sidekiq::Matchers::HaveEnqueuedJob#matches? when condition matches when expected are matchers returns true

Deprecation Warnings:

--------------------------------------------------------------------------
RSpec::Sidekiq::Matchers::BeDelayed 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/yelled/Development/rspec-sidekiq/spec/rspec/sidekiq/matchers/be_delayed_spec.rb:25:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------

--------------------------------------------------------------------------
RSpec::Sidekiq::Matchers::BeProcessedIn 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/yelled/Development/rspec-sidekiq/spec/rspec/sidekiq/matchers/be_processed_in_spec.rb:15:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------

--------------------------------------------------------------------------
RSpec::Sidekiq::Matchers::BeRetryable 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/yelled/Development/rspec-sidekiq/spec/rspec/sidekiq/matchers/be_retryable_spec.rb:18:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------

--------------------------------------------------------------------------
RSpec::Sidekiq::Matchers::BeUnique 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/yelled/Development/rspec-sidekiq/spec/rspec/sidekiq/matchers/be_unique_spec.rb:9:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------

--------------------------------------------------------------------------
RSpec::Sidekiq::Matchers::HaveEnqueuedJob 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/yelled/Development/rspec-sidekiq/spec/rspec/sidekiq/matchers/have_enqueued_job_spec.rb:14:in `block (3 levels) in <top (required)>')
--------------------------------------------------------------------------

The Fuubar formatter uses the deprecated formatter interface.
 Formatter added at: /Users/yelled/.rvm/gems/ruby-1.9.3-p362/gems/rspec-core-3.0.0.beta2/exe/rspec:4:in `<top (required)>'

Using `stub` 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/yelled/Development/rspec-sidekiq/lib/rspec/sidekiq/batch.rb:37:in `block (2 levels) 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.

7 deprecation warnings total

Randomized with seed 19180

[Coveralls] Outside the Travis environment, not sending data.
Coverage report generated for RSpec to /Users/yelled/Development/rspec-sidekiq/spec_result. 182 / 187 LOC (97.33%) covered.

[yelled3]

@philostler opened a PR - I'll fix all the issues and warnings.

[philostler]

Superseded by #47