Comments (4)
I've not done testing against 3.0.0.beta2 yet
Have you(?) and are there are current failures popping up?
from rspec-sidekiq.
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.
from rspec-sidekiq.
@philostler opened a PR - I'll fix all the issues and warnings.
from rspec-sidekiq.
Superseded by #47
from rspec-sidekiq.
Related Issues (20)
- have_enqueued_sidekiq_job Diff is Wrong HOT 4
- Testing the negative case of have_enqueued_sidekiq_job with any arguments? HOT 10
- be_retryable not using global settings HOT 2
- Checking for time has a different format expectation HOT 1
- has_enqueued_sidekiq_job is not matching even though they are identical HOT 7
- Disable all sidekiq jobs for testing HOT 1
- Block syntax `enqueue_sidekiq_job` matcher HOT 8
- Issue with yaml safe loading (psych gem) HOT 2
- `be_delayed` without expected_arguments never matches HOT 4
- RSpec::Sidekiq::NullStatus is missing pending count
- Using ActiveJob::Base with sidekiq_options raises an error HOT 5
- difference in DST handling between Sidekiq's `perform_in` and `have_enqueued_sidekiq_job`
- How to expect to have_enqueued_sidekiq_job with specific queue? - [setting queue name at runtime] HOT 1
- Does this gem need a new owner? HOT 17
- Null Object method missing for Null Batch masks NoMethod errors
- Support Sidekiq 7 and deprecate be_delayed matcher
- Potentially unintentional breaking change in 4.0 with Symbol in argument matchers? HOT 15
- Potentially unintentional breaking change in 4.0.2 with Symbol in argument matchers? (Part 2) HOT 6
- NameError: uninitialized constant RSpec::Matchers::Composable HOT 5
- Match on custom context HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rspec-sidekiq.